Oh and here is the documentation I read which helped http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/
From: Gannon, Todd Sent: Wednesday, 17 February 2016 10:13 AM To: 'ms...@lists.myitforum.com' <ms...@lists.myitforum.com> Subject: RE: [mssms] SUP Scan issues on clients and high cpu on site server Thanks – I did do the wsus database maintenance cleanup, however didn’t resolve the issue. But you were right it being a timeout issue. Ended up increasing the memory limit of the app pool and that seems to resolve it. From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Qadri, Syed Sent: Monday, 15 February 2016 9:36 PM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: RE: [mssms] SUP Scan issues on clients and high cpu on site server Since the error seems to be a timeout issue, you need to start working on the cleanup of the WSUS database. It requires a cleanup. Below would be the process you would like to use. http://blogs.technet.com/b/configurationmgr/archive/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance.aspx Regards, Syed. From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of CESAR.ABREG0 . Sent: Monday, February 15, 2016 11:49 AM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: Re: [mssms] SUP Scan issues on clients and high cpu on site server The error translate to firewall issue. Can you access the WSUS from the agents? http://windows.microsoft.com/en-us/windows/windows-update-error-80072ee2#1TC=windows-7. On Sun, Feb 14, 2016, 9:39 PM Eswar Koneti <eswarkon...@outlook.com<mailto:eswarkon...@outlook.com>> wrote: the error code from wuahandler.log translates to the operation timed out, seems like network issues for the client while communicating to sup server. have a look at this article on this http://www.scconfigmgr.com/2015/04/07/how-to-amend-wsus-scan-retry-error-codes-list-in-configmgr-2012-with-powershell/ Regards, Eswar Koneti www.eskonr.com<http://www.eskonr.com> sent from mobile device, please excuse any typo's as a result. From: "Gannon, Todd" <todd.gan...@cbh.com.au<mailto:todd.gan...@cbh.com.au>> Sent: Feb 15, 2016 12:07 PM To: ms...@lists.myitforum.com<mailto:ms...@lists.myitforum.com> Subject: [mssms] SUP Scan issues on clients and high cpu on site server Hi guys – Sorry for the long winded message, but have had some great advice from here in the past and was hoping someone may be able to help out here. After installing SUP and doing some initial testing which worked great, I have widened the SUP scan to about 1500 computers, removed the gpo from wsus in preparation for deployment of the software updates release in march. This was configured at the start of last week, and since doing this I have noticed considerably higher cpu usage on the config mgr server, namely being the wsuspool worker process whilst the scan is taking place. I run the scan during the night, so it is mostly ok, however for the first part of the morning the computers that were off, come back online and there is a cpu bottleneck on the site server, making any admin work horrible. Then throughout the day intermittently I get these spikes of about 5-10 mins where the same process is consuming the majority of cpu. The only thing that really pops out to me is running the scan report, there are a number of failed scans, with the error as captured below. It seems these figures are improving to Scan completed after each daily scan completes. [cid:image001.png@01D167DE.60CA3400] [cid:image002.png@01D167DE.60CA3400] The site server is a virtual server running on ibm hardware x3850 X5. The virtual server has 32gb ram, 4 x vcpu, with roughly 3000 clients all up. Majority of clients connected locally. Was wondering if anyone has come across this, or should it settle down once clients have completed the scan? Is there a way to ensure the clients complete the scan. I reviewed the local client logs wuagent.log and scanagent.log as well as the windowsupdate.log, and have run manual scans on the clients but don’t know why the scan fails and then after maybe 4th or 5th scan it completes. ScanAgent: [cid:image003.png@01D167E4.4E2FE0A0] WUAhandler [cid:image004.png@01D167E4.4E2FE0A0] WindowsUpdate.log [cid:image005.png@01D167E8.B969D750] Apart from my initial test group, I have not configured any update deployments to these computers yet, so maybe that may be where the problem lies. I will test that later. Thanks Todd This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this mail in error please notify the originator of the message. This footer also confirms that this email message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of the CBH Group. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this mail in error please notify the originator of the message. This footer also confirms that this email message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of the CBH Group.
