We are facing some issues(Client computer Memory activity is high) on client pcs.

From 'https://technet.microsoft.com/en-us/library/gg682067.aspx#BKMK_SoftwareUpdatesDeviceSetting'

I came to know that 'The deployment re-evaluation schedule should be adjusted based on company policy for software update compliance, whether users have the ability to uninstall software updates, and so on, and with the consideration that every deployment re-evaluation cycle results in some network and client computer CPU activity.' In our environment we don't allow users to uninstall/install updates.

Can we change this scan schedule to initiate for every 30 days?? What is the impact?

Current scenario:
We deploy patches every month(After patch Tuesday)
Schedule deployment re-evaluation runs for every 7 days.
Software update scan schedule runs for every 7 days.

Any help would be appreciated..!!

Thanks,
Lokesh

• Edited by LokeshGoud 12 hours 36 minutes ago Typo

If you are doing this in response to high CPU activity, I would do more testing before implementing the change. While it uses some CPU, it really should not be noticeable on devices.

- If you go to a workstation where the CPU is mostly idle and manually kick off the task, what kind of behavior are you seeing?

- On machines with high CPU usage, what got you pointed at this task?

Most of the organizations I work with have the re-eval task scheduled for between 1 and 7 days, and the update scan for daily without any noticeable CPU usage on the devices.

  

I hope that helps,

 

Nash

Re-Eval does not affect the initial distribution of softwarae updates at all. That task is only used to check if all required updates are *still* present on the system.

Hi Nash,

Its 'Client computer Memory activity is high' it is taking up to 80% memory all the time.

Kr,

Lokesh

Hi Torsten Meringer,

We have more than 7000+ clients and we are deploying updates in every month. So the number of updates are also more than 10000. When re-evaluation is triggered I doubt it is checking some of the updates and causing the High memory issues on the Client PC.

Kr,Lokesh

Please re-read my answer. "Re-eval" is not needed when it comes to "patch tuesday scenar

Have you deployed the latest Windows Update Agent Update for July 2015: https://support.microsoft.com/en-us/kb/3050265?

Here is the some more background info on this issue:
- Before posting the query here, I had already spent good amount of time in troubleshooting the root cause.
- Cleared cache on Client Computer.
- Observed 'svhost.exe' is the proccess and depending services are 'BITS' and 'WUAgent'.
- Checked logs 'WUAhandler.log/UpdateDeployment.log/WindowsUpdate.log/ScanAgent.log' and confirmed that it is RE_EVALUATION CYCLE which is consuming more memory.
- After the scan is completed, client is coming back to the normal situation.
- Installed 'kb3050265' and the tests are some better, but couln't solve the issue completely...

All the inputs are welcome...!!

What client OS is being used?

Windows 7 Professional and Windows 7 Enterprise.

You should have a look at http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx if you are using x86 W7.