The All Covered Advanced Technology Solutions team writes scripts to help our engineers speed up repetitive tasks using automation, in this case I am writing a script to install and configure a new Windows Server Update Services (WSUS) server.

Many thanks to Boe Prox over at The Scripting Guys for sharing how to install and configure WSUS using the UpdateServices PowerShell module (Installing WSUS on Windows Server 2012).  A thank you also goes out to Trevor Jones for his article on Installing and Configuring WSUS with Powershell.

I found two issues with The Scripting Guys code and did not find any answers or solutions in the community.  I continued to troubleshoot these issues and found solutions for both.

Issue # 1 – All Office and Windows Products are enabled

I wanted to only enable select Microsoft Office and Windows products, although the parent categories “Office” and “Windows” were also selected which was not desired, this was the case if you used Product Title or the Product ID.  Here’s the commands that I tried to use to enable select Office products, Silverlight, and only Windows Server 2012 R2:

Or using the Product Id:

Then review what Products are enabled and you’ll see “Office” and “Windows”:

Solution

After enabling the desired products, disable the parent categories “Office” and “Windows” using their Product IDs.

Then review what Products are enabled and you will no longer see “Office” and “Windows”.

Issue # 2 – WSUS Configuration Wizard appears when opening the WSUS Management Console

After a PowerShell script completes a successful WSUS installation and configuration when you open the Windows Server Update Services Management Console you are still presented with the Windows Server Update Services Configuration Wizard which would be best to hide.  The wizard prompts you to configure your WSUS server which was already done using the PowerShell script.

Solution

Change the WSUS Configuration property OobeInitialized in $wsus.GetConfiguration() from $false to $true.


Mike Driest