Some content in this section was written by Marta Barillas, a SDET on the WSUS engineering team.
This blog post applies to Windows Server 2012 and Windows Server 2012 R2.
Requirements for NLB in WSUS 6.x
The requirements to run WSUS in a NLB cluster include:
* If you are not running WSUS in a NLB configuration, then the WSUS servers must not share a database or content directory.
Prior to Windows Server 2012, WSUS 3.2 requires a special set up command line as described in the Network Load Balancing topic in WSUS 3.x documentation. Please refer to that documentation (in the in-box HTML help/CHM file) if you are using WSUS 3.2.
Additionally, all requirements for NLB also apply above and beyond the requirements discussed above.
Sample test configuration
Step 1. Install WSUS
The steps to install WSUS are the same for NLB and non-NLB scenarios. You can install WSUS using PowerShell or Server Manager.
Note: When you use PowerShell to install WSUS 6.x, you must run post-installation tasks from the command line.
Option1: Install WSUS for NLB using PowerShell (recommended)
Note: updateservices-rsat is Optional; it will install the WSUS MMC console and cannot be installed when installing WSUS on a Server Core installation.
& 'C:\Program Files\Update Services\Tools\WsusUtil.exe' postinstall SQL_INSTANCE_NAME=<Name> CONTENT_DIR=<Path>
Option 2: Install WSUS for NLB using Server Manager
Alternatively, you can install WSUS using the Server Manager GUI.
Note: local server is selected by default.
Note: This step must be run in serial (not in parallel) across all WSUSs in the NLB.
Step 2. Configure Content Sharing
WSUS Content Sharing is required when using a Shared Database. Documentation for creating a shared file location can be found at: http://technet.microsoft.com/library/dd939896(v=ws.10).aspx. Relevant portions of that article are included here:
Create a shared file location
You should create a single shared file location that is available to all of the front-end WSUS servers. You can use a standard network file share and provide redundancy by storing updates on a RAID controller, or you can use a Distributed File System (DFS) share. The domain machine account of each front-end WSUS server must have Change permissions on the root folder of the file share. That is, if there is a WSUS server installed locally on the computer that has the DFS share, the Network Service account should have change permissions on the root folder. In addition, the user account of the administrator who will run WsusUtil.exe movecontent should have Change permissions.
After you install a WSUS update, check the NTFS file system permissions for the WSUSContent folder. The NTFS file system permissions for the WSUSContent folder may be reset to the default values by the installer.
It is not necessary to use a DFS share with an NLB cluster. You can use a standard network share, and you can ensure redundancy by storing updates on a RAID controller.
For Windows Server 2012 (WSUS 6.2), The Scripting Guy wrote about the command line and GUI steps to be used to install a Front-End WSUS Server: http://blogs.technet.com/b/heyscriptingguy/archive/2013/04/15/installing-wsus-on-windows-server-2012.aspx
Step 3. Install/Configure NLB
The actual configuration of NLB is detailed on TechNet here: http://technet.microsoft.com/en-us/library/cc754833(v=WS.10).aspx
In our own NLB test environment, we have the following settings set to ON:
Step 4. Check that things are working
4.1. Test that the master server can switchover in the event of downtime
Run the following command to ensure that multiple servers are listed:
Shut down the master server. Then run the command again (on a different WSUS machine) and verify that the master server has been switched.
4.2. Test the WSUS client connection
On the WSUS server, assuming that you are using the default port (8530), run the following command
Verify that clients are able to connect. On a client machine which is configured to use the WSUS NLB cluster, run the following command:
Because of sharing same DB, patching can be tricky because only WSUS machines with the same version must be sharing DBs, as the DB schema could be changing as part of the patching.
If you are running WSUS in a NLB configuration, then you must upgrade all WSUS servers together. To do this, disconnect each server from the database & upgrade, then once all servers are disconnected from the database & content directory, you can start re-connecting WS2012 servers to the database & content directory. For one NLB cluster sharing a single database, you could follow these steps:
I am attempting to add my WSUS NLB cluster to VMM 2012 R2 as an update server, and it is bombing out. Any ideas on how to add that highly available WSUS configuration to VMM 2012 R2?