Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Advanced Configuration Options > Configuring Additional Patch Manager Servers

Configuring Additional Patch Manager Servers

Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 507 Votes: 0 Revisions: 4

There are several reasons to configure Patch Manager servers in addition to the default PAS. For example:

  • Use additional Automation role servers to distribute the load of running Patch Manager tasks.
  • Use additional Management role servers to store inventory data from distinct groups of clients in separate databases.
  • Use additional Application role servers to distribute the load of running Patch Manager administration consoles.

For additional information about these and other use cases for additional Patch Manager servers, see "Advanced Deployment Scenarios".

If the standard setup wizards fail, use SetupHelper.exe to provision the additional Patch Manager servers. For additional information, see "Advanced Setup CLI Commands".

Installing the Patch Manager Server

Use the Patch Manager installer with the "Advanced" option to install a Patch Manager administration console on a remote system. This system can be a server or workstation.

For additional information about which Patch Manager server roles to install, see "Advanced Deployment Scenarios".

To install an additional Patch Manager server:

  1. Log on as an administrator to the system on which you want to install Patch Manager.

  2. Temporarily disable any antivirus software.

  3. Run the SolarWinds Patch Manager.exe installer program.

  4. If the server is missing C++ Runtime and/or Microsoft .NET Framework, click Install to allow the installation wizard to install the missing component(s).

  5. In the Installation Type, select only Install the Patch Manager administration console, and click Next. All other checkboxes should be clear.

  6. After the installation wizard opens, click Next.

  7. If necessary, enter YES to create a backup of your Orion database, and then click Next.

  8. Accept the terms in the End User License Agreement, and then click Next.

  9. Click Next to use the default installation folder. Click Browse to choose a different folder.

  10. Select Advanced Install, and click Next.

  11. Click Next to install the selected Patch Manager components.

  12. Click Next to begin the configuration wizard.

  13. Select a role, and click Next.

  14. If you are not installing a Primary Application Server, enter the host name of the Patch Manager Primary Application Server. Click the Test button to ensure that the computer can connect to the PAS.
    Note: The Port field is pre-populated with port 4092. This is the port Patch Manager consoles use to connect to a Patch Manager server. Do not alter this value.

  15. Click Next.

  16. Enter the management group and ensure that Configure the Windows Firewall for the Server is selected.

  17. Click Next.

  18. If you do not have a WSUS server, select Install the Patch Manager WSUS service (Recommended). If you already have your own WSUS server, select I'll supply my own WSUS server.

  19. Click Next.

  20. Select how Patch Manager should configure IIS.

  21. Enter a location that Patch Manager can use to store updates locally.

  22. Select Provision the WSUS Server to the Patch Manager to manage WSUS from Patch Manager.

  23. Click Next.

  24. Enter the administrator credentials for Patch Manager, and click Next.

  25. Select your SQL instance and supply the credentials.

  26. Click Next.

  27. Select Use the default service account or enter different service account credentials for Patch Manager.

  28. Click Next.

  29. Click Finish.

To assign a new Patch Manager server to a management group:

  1. In the left pane of the Patch Manager console, expand Patch Manager System Configuration, and then select Patch Manager Servers.

  2. In the Actions pane (right), click Patch Manager Server Wizard.

  3. In the Patch Manager Server Configuration window, select Edit and existing Patch Manager Server's configuration settings, and then click Next.

  4. In the Server Name menu, select the new server, and then click Resolve.

  5. Click Next.

  6. In the Management Group menu, select the management group.

  7. Specify any additional settings on this page, and then click Next.

  8. On the summary page, verify the settings for the new server, and then click Finish.

Last modified