Your company has a branch office that contains a Windows Server 2008 R2 server. The server runs
Windows Server Update Services (WSUS). The company opens four new satellite offices. Each
satellite office connects to the branch office by using a dedicated WAN link. You need to design a
strategy for patch management that meets the following requirements:
• WSUS updates are approved from a central location.
• WAN traffic is minimized between the branch office and the satellite offices.
What should you include in your design?
A.
In each satellite office, install a WSUS server. Configure each satellite office WSUS server as a
replica of the branch office WSUS server.
B.
In each satellite office, install a WSUS server. Configure each satellite office WSUS server as an
autonomous server that synchronizes to the branch office WSUS server.
C.
On the branch office WSUS server, create a computer group for each satellite office. Add the
client computers in each satellite office to their respective computer groups.
D.
For each satellite office, create an organizational unit (OU). Create and link a Group Policy object
(GPO) to each OU. Configure different schedules to download updates from the branch office WSUS
server to the client computers in each satellite office.
Explanation:
Replica Mode and Autonomous Mode
You have two options when configuring the administration model for your organization’s
downstream WSUS servers. The first option, shown in Figure 8-5, is to configure the downstream
WSUS server as a replica of the upstream server. When you configure a WSUS server as a replica, all
approvals, settings, computers, and groups from the upstream server are used on the downstream
server. The downstream server cannot be used to approve updates when configured in replica
mode, though you can change a replica server to the second mode—called autonomous mode—if an
update urgently needs to be deployed.
Figure 8-5Downstream replica server
