Install and Configure WSUS for SCCM – A 10 Minute Easy Guide
In this post I will cover how to install and configure WSUS for SCCM. Before you install WSUS let’s understand more about WSUS basics and the role of WSUS and SCCM in software updates deployment.
Most of the points covered in this post are some of the frequently asked questions on WSUS and SCCM. I will try to explain these in simple ways for better understanding.
What is WSUS
WSUS is a stand-alone product developed by Microsoft. The WSUS is a server-based product for distributing updates to Windows systems.
If you have worked on WSUS, then you might know that WSUS uses the WUA to scan for patch applicability and subsequently install updates delivered by WSUS.
If you planning to install WSUS for SCCM, you must use the 64-bit version of WSUS on one of the supported 64-bit editions of Windows Server.
Because there are a lot of updates for several products, downloading updates is performed according to some rules such as classification, languages or products.
However WSUS can’t be used alone in a big IT infrastructure requiring automation. This product doesn’t have a granular scheduler to deploy update. This is why SCCM is used with WSUS.
Do I need WSUS for SCCM
This is an interesting question asked by many, do i need WSUS for SCCM ?. WSUS is necessary for software updates synchronization and for the software updates applicability scan on clients.
When you install WSUS for SCCM and configure it, you get more control over software updates deployments. In other words SCCM and WSUS work well when installed together.
If you are planning to install WSUS you must install it before you install software update point role in SCCM.
Difference between WSUS and SCCM
A lot of people ask this question – What is the difference between WSUS and SCCM. WSUS is Microsoft product that offers enterprise OS and Microsoft application patching.
It basically connects to Microsoft’s update catalogue, has got minimal configuration options and limited reporting details on patch deployment.
When it comes to SCCM, it has a system role called Software Update Point (SUP). This role has to be installed on WSUS server.
With SUP role installed, SCCM can manage updates catalog and binaries to make updates packages. The packages can be created by selecting the classification, products, languages of the update.
Once these updates packages are ready, it can be deployed with SCCM. You must always avoid using WSUS console to manage updates when you have SUP installed.
Supported WSUS versions for SCCM Software Update Point
The following versions of WSUS are supported for a software update point.
- WSUS 10.0.14393 (role in Windows Server 2016)
- WSUS 10.0.17763 (role in Windows Server 2019) (Requires SCCM 1810 or later)
- WSUS 6.2 and 6.3 (role in Windows Server 2012 and Windows Server 2012 R2)
Install WSUS for SCCM
To install WSUS for SCCM
- Login to server where you want to install WSUS.
- If this is the same server on which you would be installing SCCM SUP role, that’s great.
- Launch Server Manager and click Add roles and features.
Select Role-based or feature based installation. Click Next.
On Server Roles page, select Windows Server Updates Services. Click Next.
Nothing to select on Features page. Click Next.
Under Roles Services select the following.
- WSUS Services
- SQL Server Connectivity
Select a folder path where you want to store the WSUS updates. You could choose a local path or a remote path. Click Next.
You must specify an existing database server to install WSUS database. Enter the name of the SQL server and click Check connection.
If it shows successfully connected to server, click Next.
On the Confirmation page, review the settings and click Install.
Configure WSUS for SCCM – Post Installation Tasks
This is the last step where you need to perform a bit of WSUS configuration – post installation tasks. If you skip this you won’t see the SUSDB in SQL server.
Notice that WSUS is installed but it says Configuration required. Click Launch Post-installation tasks.
Wait for few minutes and you should see Configuration successfully complete message. Click Close.
Now launch the SQL server management studio and login to database engine. Expand Databases and you should see SUSDB database.