WSUS Question

zimbo · Jan 30, 2007

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Trying to get my head round multiple WSUS servers... I been reading this

Chaining

A distributed network often calls for multiple WSUS servers configured in something called a server chain. If you have two or more locations with 50+ PCs and servers separated by a WAN link, you may want to think about deploying local WSUS servers at each location. Server chains enable one WSUS server to synchronize with Microsoft Update over the Internet, and then relay those updates to additional downstream WSUS servers without incurring further Internet traffic.

Benefits of Chaining

Only one server needs Internet connectivity to Microsoft Update to download updates/patches and metadata. Note: Metadata is simply information that describes the scope of the update/patch, such as which systems it applies to, etc.

Downstream servers (those not communicating with Microsoft Update) can be administered autonomously from the upstream server. For instance, they can build their own computer groups, approve their own updates, etc. This is good if you have IT administrators at each location who want/need the ability to customize their local WSUS server.

Chaining can be enabled or disabled at any time, providing flexibility for evolving networks. The option to enable chaining is a simple check box on the WSUS Synchronization Options Administration page.

Click to expand...

Replicas

Another option for advanced deployments is replica mode. Much like WSUS server chains, replica servers inherit settings and updates from their upstream master server. However, unlike server chains, replica servers are designed for environments where a central administrator controls computer groups and update approval for the entire enterprise.

The only information that isn’t synchronized between the master server and its replica servers is the content of the computer groups themselves. For instance, an administrator might create four computer groups on the master server named Branch A through Branch D. While all replica servers will receive these group names, they will not contain any members. The idea behind this design is that the WSUS administrator will create enough computer groups to cover the entire enterprise. Then, a WSUS replica server at a branch office will add the local PCs and servers to a group (say, Branch B) and the centrally approved patches for that group will be installed. It sounds complicated, but it really isn’t once you get wrap your brain around it. For more detailed information on replicas, refer to the WSUS Deployment Guide.
Click to expand...

In the Replicas section, the words i highlighted is this the key difference between Replicas and chaining - in other words am i right in thinking that the Replica server has no control on which updates are installed or approved and that they just "link" the updates to the groups provided from the main server?

Phoenix · Jan 30, 2007

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

thats the general gist of it as far as i remember mate
replicas are good for multi sites with one central it team, especially one where internal pipes are used to connect to the main DC as with some companies

personally i think most companies i've worked for would prefur a third method (i havnt actualy tried, it may already be possible) one where its all centrallay managed but uses its own net pipe, as net connections are often far cheaper than p2p wan connections these days

zimbo · Jan 30, 2007

Alright cheers ryan!

Log in or Sign up

WSUS Question

zimbo Petabyte Poster

Phoenix 53656e696f7220 4d6f64

zimbo Petabyte Poster

Share This Page

Navigation

Popular Forums

Useful Links

Log in or Sign up

WSUS Question

zimbo Petabyte Poster

Phoenix 53656e696f7220 4d6f64

zimbo Petabyte Poster

Share This Page

Useful Searches