Configuring WSUS for Software Management 2.0

In basic scenario Windows patching requires end machine to communicate directly with Windows Update service. In some circumstances it may be needed to do these operations in a restricted internet environment or even in completely offline mode.

In such cases you need to install and configure Windows Server Update Services (WSUS). Below you can find step by step manual on configuring it to work with VSA Software Management 2.0.

The whole process incorporates these steps:

  1. Install WSUS.
  2. Import and configure WSUS Agent Procedures.
  3. Deploy Agent Procedures to end machines.

Step 1. WSUS installation.

System requirements

The minimum hardware requirements for WSUS are:

  • Processor: 1.4 gigahertz (GHz) x64 processor (2 Ghz or faster is recommended).

  • Memory: WSUS requires an additional 2 GB of RAM more than what is required by the server and all other services or software.

  • Available disk space: 40 GB or greater is recommended.

  • Network adapter: 100 megabits per second (Mbps) or greater (1GB is recommended).

Supporting Operating Systems:

  • Windows Server 2022.
  • Windows Server 2019.
  • Windows Server 2016.
  • Windows Server 2012 R2.
  • Windows Server 2012.

Configure network connections

Configure your firewall to allow your first WSUS server to connect to Microsoft domains on the internet.

Your WSUS server must have outbound access to ports 80 and 443 on the following domains:

http://windowsupdate.microsoft.com
http://*.windowsupdate.microsoft.com
https://*.windowsupdate.microsoft.com
http://*.update.microsoft.com
https://*.update.microsoft.com
http://*.windowsupdate.com
http://download.windowsupdate.com
https://download.microsoft.com
http://*.download.windowsupdate.com
http://wustat.windows.com
http://ntservicepack.microsoft.com
http://go.microsoft.com
http://dl.delivery.mp.microsoft.com
https://dl.delivery.mp.microsoft.com

You must configure your firewall to allow the WSUS server to access any URL within these domains. The IP addresses associated with these domains are constantly changing, so don't try to use IP address ranges instead.

Configure your firewall to allow client computers to access a WSUS server.

Your client computers will all connect to one of your WSUS servers. The client computer must have outbound access to two ports on the WSUS server. By default, these are ports 8530 and 8531.

Installation

To install WSUS you just need to execute the powershell script provided in the attachment (installWSUS.ps1). It will do the following operations:

  1. Download and install .Net 3.5.
  2. Download and install Microsoft Report View.
  3. Download and install Sql Express.
  4. Configure WSUS.
  5. Do initial sync of WSUS.
  6. Configure Products (configurable).
  7. Configure Classifications (configurable).
  8. Configure AutoSync (once per day at midnight).
  9. Decline updates (configurable).
  10. Configure Default Approval Rules.

You can edit the powershell file to match your rules.

Step 2. Import and configure Agent Procedures.

Once WSUS is configured we need to make adjustments in registry keys on end machines to use local WSUS server for scan and patch procedures.

To simplify this we provide Agent Procedures to make these adjustments in an automated way. You can use agent procedures in the attachment (Procedure Folder WSUS Configuration.xml). 

Import agent procedures.

Use System -> Server Management -> Import Center page to import XML file with agent procedures:

mceclip1.png

Set WSUS server name

The final step here is to set the actual WSUS server name or ip address. You can do this by opening Agent Procedure editor:

  1. Open Agent Procedures -> Schedule / Create.
  2. Click on the "Set WSUS Registry" procedure in the Shared -> WSUS Configuration folder.
  3. Click "Edit Procedure" button.
  4. Edit and Save.

mceclip2.png

Step 3. Deploy Agent Procedures to end machines.

The last step is to deploy "Set WSUS Registry" procedure to end machines. 

You have two options to do that:

  1. Schedule or Run execution via Agent Procedure dialog.
    mceclip4.png

  2. Assign this procedure to a specific Policy via Policy Management module and then assign end machines to use this Policy. For assignment use Policy Management -> Assignment section.
    mceclip5.png

Further reading

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Contact us