Configure Downstream WSUS Server

  • Autonomous downstream
    • Uses another WSUS server as it's master repository. Any updates that the master server has downloaded, will be available to the downstream server.
    • Allow flexibility in creating computer groups
    • Allows individual approvals for updates different from that of the master
    • Reduces overall bandwidth off campus as the updates are downloaded from Microsoft once and the distributed to other servers
    • Does not have to be in the same Active Directory forest as the master.
  • Replica downstream
    • Uses another WSUS server as it's master repository. Any updates that the master server has downloaded, will be available to the downstream server.
    • Mirrors update approvals, settings, computers, and groups from its parent. Updates can only be approved on the upstream (master) server
    • Makes reports on status of it's clients available to the master server.
    • Does not upload reports to master server
    • Must be in the same Active Directory forest as the master to allow for full reporting.

Configuring Secondary server

  • Open MMC with Update Services Snap-in
  • Connect to server you are going to change to a secondary server
  • Click Options in the left pane
  • Click Update Source and Proxy Server
  • Click the Synchronize from another Windows Server Update Services Server radio button
  • Enter server name: WSUS.CITES.ILLINOIS.EDU (to use the CITES WSUS as the upstream master)
  • Port Number: 80 or 443 (443 if you check the Use SSL when synchronizing update information box)
  • Check This server is a replica of the upstream server. (This will turn the WSUS server into a replica server and most options will be greyed out as it inherits from the master.)
Labels: