![]() ![]() At this point the normal train of thought would be “I met the requirements, all should be well!”. ![]() After uninstalling/reinstalling WSUS from server roles, I downloaded and installed SP2 for WSUS 3.0 since that’s the requirement for SCCM 2012. #Change wsus pool iis updateThis week I had an issue where I needed to rebuild the WSUS server leveraged by my SCCM 2012 Software Update Point. SCCM 2012: WSUS Server version 2.0 SP2 or above is not installed or can not be contacted This entry was posted in System Center, Windows Server and tagged SCCM, SCCM 2012 SUP, SCCM SUP Crash, WSUS, WSUS App Pool Crash, WSUS Crash. I hope this makes your day at least a little bit easier. These changes should have fixed your problems, and all should be running well! If not, I recommend you contact Microsoft (especially if you have a very large infrastructure) since there are a few more tweaks you can make in IIS. Go ahead and launch your SCCM console and do the sync from there. Or, if you have an SCCM instance leveraging WSUS you DO NOT DO ANYTHING IN THE WSUS CONSOLE (if you didn’t know). #Change wsus pool iis manualIf you run a standalone WSUS instance, you can now go do a manual synchronization in the WSUS management console to test the change. If for whatever reason you are still exceeding this limit you can set this to “0” denoting an unlimited amount.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |