Mine started getting hammered yesterday at 5:00pm EST. I've had my private memory limit bumped for quite a while now and my app pool isn't crashing. I had enabled WSUS clean up on my SUP here:
[cid:image002.jpg@01D2B448.2D2EC310] Doesn't look like it's doing anything though... exec spGetObsoleteUpdatesToCleanup came back with 21k rows... this is gonna be a long day. De From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jimmy Martin Sent: Thursday, April 13, 2017 8:26 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: IIS Worker Process causing High CPU issues on Site Server http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/ Jimmy Martin (901) 227-8209 From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Darin Nelson Sent: Wednesday, April 12, 2017 1:00 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] IIS Worker Process causing High CPU issues on Site Server 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 This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
