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
  • RE: "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."

    and I have the local clients are not 'tracking' the scheduled scans and reporting them to the console.

    All of my problems started after my conversion from console v3 to v4 and setup new policies for the clients

    to get/upgrade from the v7.6 to v9 clients...

    The clients appeared to have 'upgraded', but something is corrupt and they are not tracking/reporting anymore...

    but they do checkin and get updates.

    When I've tried to manually uninstall- usually a component (autoupdate/RMS/AV) will error out and fail.

    So follow instructs from support and run into DLL's that cannot be deleted from the disk

    and/or incorrect permissions in the registry.

    So, suspect some pieces really did not get upgraded - and was trying to run with incompatable 'mixed' component versions.

    I'm slowly get them all fixed, but a real pain to manually do each.

    :2126
Reply
  • RE: "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."

    and I have the local clients are not 'tracking' the scheduled scans and reporting them to the console.

    All of my problems started after my conversion from console v3 to v4 and setup new policies for the clients

    to get/upgrade from the v7.6 to v9 clients...

    The clients appeared to have 'upgraded', but something is corrupt and they are not tracking/reporting anymore...

    but they do checkin and get updates.

    When I've tried to manually uninstall- usually a component (autoupdate/RMS/AV) will error out and fail.

    So follow instructs from support and run into DLL's that cannot be deleted from the disk

    and/or incorrect permissions in the registry.

    So, suspect some pieces really did not get upgraded - and was trying to run with incompatable 'mixed' component versions.

    I'm slowly get them all fixed, but a real pain to manually do each.

    :2126
Children
No Data