Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Patch Manager > Troubheshoot downstream WSUS server issues in Patch Manager

Troubheshoot downstream WSUS server issues in Patch Manager

Overview

This article provides steps to troubleshoot the following issues resulting from downstream WSUS server configurations:

  • Systems cannot be moved from an unassigned group.
  • Systems will not change groups.
  • Options to change groups or settings are disabled in WSUS.
  • Patch Manager reports only display upstream server information.
  • The downstream WSUS does not display added systems.

Environment

  • All Patch Manager versions
  • WSUS 

Cause

When a WSUS server is in Replica Mode, it inherits the update approvals and computer groups from the parent WSUS server. Most options and settings are disabled (including moving computers and group) because the downstream WSUS server mirrors the parent WSUS server. All upstream information. As a result, a generated report will only show the upstream WSUS server to prevent duplicate information. 

The following table lists the differences between autonomous and replica downstream WSUS server configurations.

Autonomous Downstream Replica Downstream
Uses another WSUS server as the master repository. Any updates downloaded by the master server are available to the downstream server Uses another WSUS server as it's master repository. Any updates downloaded by the master server are available to the downstream server
Not required to be in the same Active Directory forest as the master to provide full reporting. Must be in the same Active Directory forest as the master to provide full reporting
Allows individual approvals for updates different from the master. Updates must be approved on the upstream (master) server. Mirrors update approvals, settings, computers, and groups from its parent.
Downstream WSUS servers must be administered separately.  Downstream WSUS servers are administered by the upstream server. 
Allows flexibility in creating computer groups Reports on status of its clients available to the master server.
Reduces overall bandwidth off-campus as the updates are downloaded from Microsoft once and then distributed to other servers Does not upload reports to master server.

Resolution

Manually administer the downstream servers to adjust some settings. 

  1. In the WSUS Administration Console, expand the server name and click Options.

  2. In the Options pane, click Update Source and Proxy Server.

  3. On the Update Source page, select Synchronize from another Windows Server Update Service server.

  4. In the Server name field, type the name of the local upstream WSUS server.

  5. In the Port number field, type the port number that this WSUS server will use to communicate with the upstream WSUS server. The default port number is 80, or 8530 on server 2012

  6. Deselect the This is a replica of the upstream server option. and then click OK.

 

Last modified

Tags

Classifications

Public