If you want to install using PowerShell instead, you can go to another one of my posts. The Post-installation tasks are mostly the same though, as the Work required for setting it up using PowerShell isn’t justified, unless you are deploying multiple WSUS servers with the same settings.
This quide is meant for Windows Server 2012.
It is not required, but a good idea: Create a new dedicated hard disk for WSUS update files.
- Installing WSUS using Server Manager
- Post installation tasks.
In order to use the Reports feature of WSUS we need to download and install Microsoft Report Viewer 2008.
Before you can install the Report Viewer though, you need to install .NET 2, or in our case .NET 3.5
Easiest way is to install it using PowerShell:
Install-WindowsFeature –name NET-Framework-Core
Do remember to update your Server, as there are (as of this writing) 16 important updates for this .NET feature.
Installing WSUS using Server Manager
- Click the Add Roles and Features in Server Manager.
- Click Next > in Before you begin, select Role-based or feature-based installation. Next >
- In Server Selection you just select the server you want to install WSUS on, and click Next >
- Scroll Down and select Windows Server Update Services.
- Click Add Features in the Add features that are required for Windows Server Update Services? Also make sure you have a mark in Include management tools (if applicable)
- Click Next > in the Server Roles window after the above roles and features has been added automatically.
- Click Next > in the Features selection screen. Necessary features has already been selected in step 5.
- You might want to follow the links on the WSUS step. Else just click Next >.
The links are all leading to:
Windows Server Update Services Help
- Select the Database you want to use for WSUS.
WID database will install Windows Internal Database while the database will install an SQL server.
Read more about the databases here: Choose the Database Used for WSUS 3.0.
I’mg going with the default selection before clicking Next >
- Choose a path. I’m choosing the drive we set up in Server 2012 – Create a new virutal HD/VHD file.
Click Next >
! Note: Select af folder instead of in the root of the drive or post installation tasks will fail.
- Review notes about Web Server Role (IIS) and click Next >
- Go with the already selected parts and click Next >
- I’m selecting Restart the destination server automatically if required, and clicking Yes to the pop-up, then Install.
- Wait for it to finish.
Post Installation tasks
- As it turns out, the server does not need a restart yet, but we do need to perform som Post-Installation tasks.
Here I/we get an error. Which turned out to be caused by choosing root path in step 10.
- We can fix the error by starting up WSUS from the start menu and enter a new path.
- Read the Before you begin and click Next > and Next >
- If this is the first WSUS server you don’t need to do anything. If you already have a WSUS server you might want to set this one up to syncrhonize from the existing server. Configure if needed, then Next >, Next >
- Press Start Connecting in order for WSUS to configure itself by applying your settings. Press Finish when done.
It might take a while depending on your setup.
Click Next once it is done.
- Select the language you need updates for. It is important you do not choose more than you need.
- Take the time needed and select only the needed applications. You can always go and add more or remove some.
- Select relevant Classifications for your environment.
- Configure how you want to Synchronize your WSUS.
You can change this later.
- I’m choosing to start initial synchronization now.
Alle the links on the What’s Next page points to: Windows Server Update Services Help
- Once you click Finish, the Main window for Windows Server Update Services opens up.
- When you click on your server Name, you can see various information about Syncrhonizing Progress and To Do.