Cleaning up WSUS - yes Updates targeted - Usually just the monthly ones are targeted. Latest WUA - yes, and actually that was just recent and maybe be part of the problem? KB2705357 - No, will apply and test KB2775511 - Yes KB2833001 - No, will apply and test KB2697479 - No, will apply and test Clearing out SoftwareDistribution - actually already tried this per a tip on a forum
I'll check out those three hotfixes that are not applied and see what happens, thanks! Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected] [mailto:[email protected]] On Behalf Of Russ Rimmerman Sent: Saturday, February 28, 2015 1:17 PM To: [email protected] Subject: [mssms] RE: Software updates scanning question Are you running all the WSUS server clean-up wizard actions (manually or via script) on a regular basis? How many updates are in your deployments that are targeted to these clients? Running the latest WUA version on the affected clients? Already have tried Win7 SP1 WMI hotfixes KB2705357, KB2775511, KB2833001, KB2697479? If all above is in check, maybe try stopping wuau service, renaming %windir%\softwaredistribution, starting wuau on one client as a test and see if it alleviates it any? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Friday, February 27, 2015 2:31 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Software updates scanning question We are running SCCM 2012 R2 CU1, SQL 2012, on Server 2012. 99% of our clients are Windows 7 SP1. We are seeing the issue documented here: https://social.technet.microsoft.com/Forums/en-US/4a782e40-bbd8-40b7-869d-68e3dfd1a5b4/windows-update-scan-high-memory-usage?forum=w7itproperf Essentially, when update scanning kicks off, the svchost.exe process skyrockets on memory use. On machines that have only 2GB of RAM, they soon exhaust physical memory and start to page out to disk. This seriously slows down the machine. We still have hundreds of machines with 2GB of RAM, so simply popping in additional memory is out of the question. The suggestion in the link is to change the scan cycle. Now, we have SCCM looking for OS/Office updates every 3 days yet the machines have issues daily. We also use SCEP and it checks for updates 3 times a day. Correct me if I am wrong, but SCEP also uses WSUS and therefore uses the Windows update scan engine to look for virus definitions. If this is true, then it would explain why the machines are slow on a daily basis. I guess I am just looking for confirmation on my hypothesis. There doesn't seem to be any fix from MS on this that I can find. We have tried some of the suggestions in the forum post but still have the same problem like the original poster has. I can change the def update scan for 4AM when all the machines power on to check for any installs they need to perform. This should at least drastically reduce the frequency of slowdowns. Thanks. Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State
