SCCM Tips, Scripts and Tools

Some of you may have had the issue where the ISS Application pool for WSUS keeps stopping. In most cases the stop is do the the Application Pool needs to use more memory then it is configured to use. 1. The way to resolve this is to open IIS expand the node and click on application pools in the list find the Application Pool called WsusPool and right click on it choosing Advanced settings. 2. In the Advanced Settings window scroll to the bottom, You are looking for "Private Memory Limit (KB)" 3. Once you find the settings change it to a larger amount be sure you do not set it higher then the memory you have installed on the server. Settings the amount to 0 will get it to unlimited. That's it once you click ok you should stop having this issue.

One issue I have came across a few times is SCCM is not syncing correctly with windows updates and the biggest issue is normally a connection issue to Microsoft. When you are having this issue you will see an error message like " WSUS Synchronization failed.  Message: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed.  Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" in your SMS_WSUS_SYNC_MANGER component. if you then go to the wsyncmgr.log file on your site server it will tell you what IP it was trying to connect to for the sync. You can then open that connection through you firewalls.

Now that you have figured out your SCCM hierarchy and server requirements for your site its time to start building your servers. If you have not done this yep please review the Preparing for SCCM page before starting any installs Below is what I will be using for my own examples. OS - Server 2016 Standard SQL - 2016 Standard   SCCM 1702 ADK 1607 SQL Server Management Studio 17.1 SCCM Settings: Site code - TST Site Name - SCCMTST Lab Servers: SCCM-Setup - Primary Site Server, Distribution point, SQL and Software Update Point Every server that is a part of your SCCM site will want to have 1 drive for the OS, 1 drive for the page file and 1 drive for the program files.  For your Distribution point you will want to add a drive for your SCCM content to sit on and a drive from the distribution point content. SCCM will story its one copy of the packages, Applications and Image files on the Distribution content drive. For Your Software Update Point server you ...