This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Awaiting Policy Transfer & SavService.exe 99% CPU

Hi all,

We are experiencing a strange issue wiith the clients (Version 9) and EC (Version 4) where they do not seem to be reporting correctly and getting hammered with 99% of the CPU.

One of the issues was the number of messages that were still waiting to be processed in the Envelopes folder, there was roughly 1GB's worth of files sat waiting to be processed.  This was rectified by following supports instrcutions, but unfortunatley there is still an issue with clients reporting to the console.  A lot of machines are showing awaiting policy transfer or differs from policy, although they dont seem to be different from the policy if you check locally.

The second issue is based around the policies being applied from the console.  If we modify the policy in the console and apply it to the clients a number of machines sit get hit by the savservice running at 99%.  The only way I have found of stopping this from happening is to remove the messages from the envelopes folder and then end the process on the clients.  If the policy is then reapplied the same happens again.

This has been logged with support but I was hoping some of you guys might have some idea's.

Thanks

:2091


This thread was automatically locked due to age.
Parents
  • I used to have this problem with Enterprise 2 and Sophos 5 when it was released; I've not seen it at all with Enterprise 3 or 4. I would routinely end up with 2GB of envelopes and the Sophos chaps had to remote desktop to my server in the end to run diagnostics and fiddle with the registry. It was never fully resolved until Enterprise 3 was released and now I have about 1MB of envelopes.

    Your endpoints aren't using virtual network adapters are they, or aren't using DHCP to be assigned fresh hostnames and IP addresses every time they're turned on? A good way of confusing ES3/4 is to install a virtual network adapter after managing a client - it'll keep trying to talk to the wrong interface and never get through.

    :2108
Reply
  • I used to have this problem with Enterprise 2 and Sophos 5 when it was released; I've not seen it at all with Enterprise 3 or 4. I would routinely end up with 2GB of envelopes and the Sophos chaps had to remote desktop to my server in the end to run diagnostics and fiddle with the registry. It was never fully resolved until Enterprise 3 was released and now I have about 1MB of envelopes.

    Your endpoints aren't using virtual network adapters are they, or aren't using DHCP to be assigned fresh hostnames and IP addresses every time they're turned on? A good way of confusing ES3/4 is to install a virtual network adapter after managing a client - it'll keep trying to talk to the wrong interface and never get through.

    :2108
Children
No Data