In this post, we will look at the steps to install WSUS for SCCM. You can install WSUS for Configuration Manager before you configure the Software Update Point role.
One of the prerequisites while installing SCCM is WSUS role installation. ConfigMgr admins can install and configure WSUS role after installing SCCM and that’s completely supported.
If you are looking to set up Software Update Point role in SCCM, the following step by step will guide you with installing Software Update Role (SUP).
If you are installing Configuration Manager on a new setup, you install WSUS for SCCM after SQL server is installed. During the WSUS role installation, you must specify the SQL server name to create the SUSDB.
If you are installing WSUS to manage updates deployment without SCCM, here is a guide to Install and Configure WSUS on Windows Server 2019.
By definition, WSUS is Microsoft’s separate, stand-alone server-based product for distributing updates to Windows systems. Windows Update service downloads and installs recommended and important updates automatically.
The software update point (SUP) site system role must be installed on a server that has WSUS role installed. For SCCM SUP role, you must use the 64-bit version of WSUS on one of the supported 64-bit editions of Windows Server. For example, Windows Server 2019 or Windows Server 2022.
Install WSUS for SCCM | Configuration Manager
Let’s install WSUS for SCCM on Windows Server.
- Log on to the server on which you plan to install the WSUS server role. Use an account that is a member of the Local Administrators group.
- In Server Manager, click Manage, and then click Add Roles and Features.
- On Server Roles page, select Windows Server Update Services and click Next.
WSUS only requires the default Web Server role configuration. On the Features page, retain the default selections, and then click Next.
On the Windows Server Update Services page, click Next.
WSUS Role Services
Under Role Services, you must select a database type for WSUS. There are three options for selecting database type for Windows Server Update Services.
- WID Database
- WSUS Services
Note: You must select one Database type for WSUS. If none of the database options are selected, the WSUS post installation tasks will fail.
When you install WSUS for SCCM, you must always select WSUS Services and Database options. These are the ones that are actually required. Do not select WID Database here. Click Next.
WSUS Content Location Selection
On the Content location selection page, type a valid location to store the WSUS updates. In this content folder the WSUS downloads and stores license terms for specific software updates in the update content folder.
During the Software Update synchronization process, Configuration Manager looks for applicable license terms in the content folder. If it cannot find the license terms, it will not synchronize the update. Provide a folder path and click Next.
Database Instance for WSUS | SCCM
On the Database Instance Selection page, specify the database server where you want to store the WSUS database. If this WSUS is for a single SCCM primary site, the same SQL server will hold the Configuration Manager Database as well.
Specify the SQL Server FQDN and click on Check connection, and you must see the message Successfully connected to server. Click Next.
On the Confirmation page, click Install.
The WSUS role is now installed and configured for SCCM. In some cases, after installing WSUS for Configuration Manager, you may see a notification that a restart is required. This can vary according to the installed server role. If it requires a restart make sure to restart the server to complete the installation.
Configure WSUS Post Installation Tasks
When you install WSUS for SCCM, you will notice that SUSDB isn’t created on your SQL Server. That’s because you haven’t performed the WSUS post installation tasks.
The WSUS post installation tasks is mandatory. This task creates the database (SUSDB), directories, pool in IIS, imports the publisher info such as Windows, Office, SQL etc.
When you configure the post installation tasks for WSUS, you are preparing the WSUS to be ready for synchronization with Microsoft.
Click on Launch Post-Installation tasks.
The message Windows Server Update Service Configuration successfully completed confirms the WSUS post installation tasks have been completed successfully. Close the Add Roles and Features Wizard.
Check SUSDB in SQL Server
After completing the WSUS post installation tasks, let’s check if the SUSDB is now visible in SQL Server. Launch the SQL Server Management Studio, enter the SQL Server name and connect to Database Engine. Expand Database and here you will find SUSDB.
Do not Configure WSUS Configuration Wizard
This is important, after you install WSUS for SCCM, you should not configure the WSUS configuration wizard. That’s because going forward Configuration Manager should be used to synchronize updates, download updates and deploy updates.
I have seen many IT guys use WSUS console even though most of the updates management can be from Configuration Manager console. It is ok to use WSUS console to review updates or the synchronization status, but you should not perform tasks such as approving or declining updates because it can adversely affect Configuration Manager’s software update management capabilities.
This completes the steps to install WSUS for Configuration Manager.