I just went through this last week. Going through the cleanup here <http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/> is what fixed it for us. I had to manually cleanup the database for the powershell script to work at the end. The script is now scheduled for a weekly basis so we don't have to deal with it again.
*Tyler Humbard* | Server Systems Administrator II O: 402-444-4654 | M: 816-267-2232 408 S 18th St. Omaha, NE 68102 [email protected] How Can We Get Better? <http://www.dotcomm.org/survey> www.dotcomm.org <http://www.dotcomm.org/> <http://www.dotcomm.org/> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. On Wed, Apr 12, 2017 at 1:00 PM, Darin Nelson <[email protected]> wrote: > > > Hello. > > > > We have recently been having very high CPU utilization on our Site server > (also our SUP). The offending process seems to be the *IIS Worker > Process* servicing the *WsusPool *Application Pool. I am wondering if > anyone has seen this and what I should look for. This has just recently > started with really no changes other than the standard MS security updates, > but those were applied earlier in Marchand this has just showed up in the > past week or so. > > > > > > > > *Environment:* > > > > ConfigMgr 1606 Site > > Windows 2012R2 Server > > 3000 devices > > > > Thank you for any insight you can give. > > > > Darin > > > >
