Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager Documentation > Patch Manager 2.1.6 Administrator Guide > Advanced configuration options > Configure additional Patch Manager servers

Configure additional Patch Manager servers

Created by Caroline Juszczak, last modified by Steve.Hawkins on Dec 07, 2018

Views: 1,112 Votes: 0 Revisions: 10

Last updated December 7, 2018

Patch Manager is installed on a dedicated server running the Primary Application Server role. This role hosts the primary configuration management database and serves as the Certificate Authority for all certificates used to register and encrypt Patch Manager communications. 

All Patch Manager operations are controlled from this server. When you install Patch Manager for the first time, the host server is called the Primary Application Server (PAS).

You can add additional server roles on remote systems to add additional functionality. The following table lists the additional server roles included with Patch Manager. 

The Patch Manager installer includes an Express option that allows you to install an evaluation version of Patch Manager and SQL Server Express. Select the Advanced Install option to install the additional server roles. SolarWinds recommends installing these server roles on separate, dedicated servers to maximize application performance.

Server Role Description
Application Server Interfaces with the Patch Manager Admin Console or integrated SCCM administration consoles, and manages all communications between the console and the Patch Manager deployment.
Automation Server Manages the local Patch Manager processes on each Patch Manager server. Each Automation server performs the inventory and configuration management tasks and interfaces with the Windows Management Instrumentation (WMI) providers to collect data and supervise remote management functions.
Management Server Maintains all inventory and discovery data for specific systems in the Patch Manager environment. Each Management server includes a defined collection of managed entities specified by their corresponding domain, workgroup, or WSUS server.

Install the Patch Manager Administrator Console on a remote server

If you cannot connect to the Patch Manager Administrator Console on the Primary Application server using a remote desktop connection, you can install the console on a separate Patch Manager server. 

Use the Patch Manager installer to install the Patch Manager Administrator Console on a remote system using the Advanced option. This system can be a server or workstation.  See Advanced Deployment Scenarios for details about selecting and installing the Patch Manager server roles.

If the standard setup wizard fails, run SetupHelper.exe to provision the additional Patch Manager server.

  1. Identify a target Windows server in your deployment.
  2. Ensure that the system meets the requirements for a Patch Manager server.

    See the Patch Manager Installation Guide for additional installation requirements and procedures.

  3. Log in to the server as an administrator.
  4. Temporarily disable any antivirus software.
  5. Download the installation file from the Customer Portal.
    1. Go to
    2. Log in using your SWID and password.
    3. In the Latest Downloads table, locate Patch Manager and click Choose Download.
    4. Download the Patch Manager full package (with SQL).
    5. Follow the prompts on your screen to complete the download.
  6. Extract the contents of the downloaded installation ZIP file to the server.
  7. Run the SolarWinds-Patch-Manager-2.1.x-Full.exe installer.

    Verify if the installation file is blocked by right-clicking the file and selecting Properties. If required, click Unblock, and then click OK.

  8. If prompted, click Install to install Microsoft .NET Framework.

    Downloading and installing Microsoft .NET Framework can take several minutes. If your system reboots, run the installation again.

  9. Select Install the Patch Manager administration console and clear all remaining check boxes
  10. If prompted, enter your email address in the SolarWinds Registration window, and click Continue.

    After you complete the registration process, you will receive product information from SolarWinds. This action is required to continue the SolarWinds Patch Manager installation.

    The installer extracts the files and initiates the Patch Manager Setup Wizard.

  11. Click Next in the Welcome window.
  12. If you accept the terms in the End User License Agreement, click Next.

    The wizard installs the SolarWinds Patch Manager software in the selected location.

  13. Complete the SolarWinds Configuration Wizard. 

Assign a new Patch Manager server to a management group

  1. Log in to the Patch Manager Admin Console. 
  2. In the navigation pane, expand Patch Manager System Configuration and select Patch Manager Servers.


  3. In the Actions pane, click Patch Manager Server Wizard.
  4. In the Patch Manager Server Configuration Wizard, select Edit an existing Patch Manager Server's configuration settings, and click Next.


  5. Enter your Patch Manager server configuration settings.


    1. Click the Server Name drop-down menu and select the new server.
    2. Click Resolve to populate the fields.
    3. Complete any remaining fields, and click Next.
  6. Associate the Patch Manager server with a management group.


    1. Click the Management Group drop-down menu and select a management group.
    2. Configure the remaining settings, and click Next.

      See Requirements in the Patch Manager Installation Guide for the Patch Manager port requirements.

  7. On the Summary page, verify the settings for the new server.
  8. Click Finish.
Last modified