Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Patch Manager > Patch Manager Documentation > Patch Manager Getting Started Guide > Configure your environment > Add WSUS to Patch Manager

Add WSUS to Patch Manager

Table of contents
Patch Manager Getting Started Home

Last Updated: March 9, 2017

After you verify that WSUS is installed in the Windows Server® operating system, Patch Manager can distribute Windows updates, third-party updates, and custom packages to managed systems in your deployment.

If you configured WSUS on a separate server, ensure that the server is running the same Windows Server operating system as your Patch Manager server to prevent API Mismatch errors.

  1. Locate the WSUS server IP address or hostname.
  2. Log in to the Patch Manager Administrator Console as an administrator.
  3. Expand Enterprise and click Update Services.

    File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_Getting_Started_Guide/0020-Configure_your_environment/0020-Add_WSUS_to_Patch_Manager/SPM-Getting-Started-Select-Update-Services.png

  4. In the Actions menu, click Add or Configure WSUS Server.

  5. In the Add or Modify WSUS Server window, enter the IP address or hostname of the WSUS server in the Server Name field.

    File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_Getting_Started_Guide/0020-Configure_your_environment/0020-Add_WSUS_to_Patch_Manager/SPM-Getting-Started-Add-Config-WSUS2.png

  6. Click Resolve.

    Patch Manager connects with the WSUS API and populates the hostname (or fully qualified domain name), connection name, and port number fields. Port 80 is the default port. 

  7. In the Port field, click the drop-down menu and select the port based on the operating system and connection. For example, select 8530 if the server is running Windows Server 2016 with SSL disabled.

    SPM-Getting-Started-Port-Field.png

    Operating System SSL Enabled Use This Port
    Windows Server 2008 R2 Yes 443
    No 80

    Windows Server 2012

    Windows Server 2012 R2

    Windows Server 2016

    Yes 8531
    No 8530
  8. Complete the remaining fields and selections. 

  9. Click Test Connection.

    Patch Manager contacts the WSUS API to establish a connection with the WSUS server. If the connection is good, the Connection Succeeded window opens.

    If the connection fails, select a corresponding port (for example, 8531 instead of 8530) and retest.

  10. Click Save.

    The WSUS server is configured in Patch Manager and the server displays in the menu. In this example, SPM-MGOM is the WSUS server.

    File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_Getting_Started_Guide/0020-Configure_your_environment/0020-Add_WSUS_to_Patch_Manager/SPM-Getting-Started-Add-Config-WSUS5.png

View updates

After you add a WSUS server to Patch Manager, additional nodes display below the server. The Updates menu contains nodes that store the updates.

After you download the updates, the Windows updates are stored in the Critical Updates and Security Updates nodes. All non-Microsoft updates are stored in the Third Party Updates node.

File:Success_Center/Reusable_content_-_InfoDev/SPM/Patch_Manager_Getting_Started_Guide/0020-Configure_your_environment/0020-Add_WSUS_to_Patch_Manager/SPM-Getting-Started-Add-Config-WSUS10.png

Click a node to view the updates. For example, click Critical Updates to display all approved critical updates. To view declined or unapproved critical updates, click the Approval drop-down menu and select an option.

Last modified

Tags

Classifications

Public