First published on TECHNET on Aug 01, 2016
Authored by Cameron Cox
Before we get started a huge thank you to Meghan Stewart (Support Escalation Engineer) and Mike Johnson (Senior Support Escalation Engineer) for their knowledge and assistance with this blog.
I have several customers who have been interested in Network Load Balancing for Configuration Manager Software Update Points (SUP). Reasons vary from wanting to avoid costly network catalog resyncs, to needing a more fluid resilient solution, responsible for patching their large scale environment. A few of considerations should be taken prior to deploying in production.
At a high level, a minimum configuration requires 2 WSUS servers, 1 database server and some sort of load balancing method. Below is a diagram of this configuration.
Traffic comes in through the load balancer, to the IIS servers. If content is needed, IE: Eula download, the content is directed to the share to be downloaded. The DFS role is optional but recommended, especially for HA considerations. If the content is only stored on one of the servers, that server becomes a single point of failure. I will cover this in detail, but when you install WSUS, you point both installs to the same database server and content location. This is called a shared database and shared content configuration. The WSUS servers will be identical which is what allows us to load balance between them without clients having to download the entire catalog every time it hits a different WSUS server.
Now that we have covered some of the considerations and a high-level overview of the end result, let’s get started.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.