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
  • Hi Chris, thanks for the reply.  We are using DHCP to assign new IP's but the lease is a fairly standard length of time and last for a few days, and none of the clients are using virtual network adapters.  There doesnt seem to be a pattern to them either which is annoying to say the least, there is a mixture of desktops and laptops.

    I have had the issue before when clearing the envelopes sorts the clients out but this time we seem to have about 85 connected machines that are still awaiting policy transfer.  I am going to try and uninstall a couple more of them today and see what happens after a redeployment.

    As for the 99% CPU issue, I seem to have got to the bottom of this.  It only happened when a policy modifiation was done, so applying the default policy to the clients worked OK and didnt cause the spike.  So it looked like the AV & HIPS policy that was deployed was corrupt or something.  Creating a new policy and reapplying the exceptions seems to have resolved it.  Now a new policy with the same exceptions works OK and can be modified and applied freely without causing an issues.

    :2112
Reply
  • Hi Chris, thanks for the reply.  We are using DHCP to assign new IP's but the lease is a fairly standard length of time and last for a few days, and none of the clients are using virtual network adapters.  There doesnt seem to be a pattern to them either which is annoying to say the least, there is a mixture of desktops and laptops.

    I have had the issue before when clearing the envelopes sorts the clients out but this time we seem to have about 85 connected machines that are still awaiting policy transfer.  I am going to try and uninstall a couple more of them today and see what happens after a redeployment.

    As for the 99% CPU issue, I seem to have got to the bottom of this.  It only happened when a policy modifiation was done, so applying the default policy to the clients worked OK and didnt cause the spike.  So it looked like the AV & HIPS policy that was deployed was corrupt or something.  Creating a new policy and reapplying the exceptions seems to have resolved it.  Now a new policy with the same exceptions works OK and can be modified and applied freely without causing an issues.

    :2112
Children
No Data