Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Advanced configuration options > Install the administrator console on a remote system

Install the administrator console on a remote system

Table of contents
No headers
Created by Caroline Juszczak, last modified by Steve.Hawkins on Mar 12, 2018

Views: 455 Votes: 0 Revisions: 8

In a standalone configuration, the Patch Manager Administrator Console is installed on your Primary Application Server. If your deployment is spread across a wide geographical area and you cannot access the Primary Application Server, you can install an additional console on a remote server in your environment. 

When you install the remote administrator console using the Patch Manager software installer, associate the console and server with a Patch Manager Application server. This server can be the Primary Application Server or any other Patch Manager server in an Application Server role. 

If you plan to integrate SolarWinds Patch Manager with SCCM, install all SolarWinds Patch Manager Admin Consoles on systems currently running SCCM.

  1. Locate the Patch Manager installer you downloaded from the SolarWinds Customer Portal
  2. Temporarily disable the antivirus software on the targeted server.
  3. Run the Patch Manager installer on the targeted server.

    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).

  4. In the Installation Type, clear all check boxes except Install the Patch Manager Administration Console, and click Next. 
  5. In the Patch Manager Installation Wizard window, click Next. 
  6. If Patch Manager is integrated with the Orion Platform, click Yes to create a backup of your Orion database, and then click Next.
  7. If you accept the terms in the End User License Agreement, click Next.
  8. Click Next to use the default installation folder.
    Click Browse to select a different folder.
  9. Select Advanced Install, and click Next.
  10. Click Next to install the selected Patch Manager components.
  11. Click Next to begin the configuration wizard.
  12. Select Application Server, and click Next.
  13. Enter the host name of the Patch Manager Primary Application Server. Click Test to ensure that the computer can connect to the PAS.

    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.

  14. Click Next.
  15. Enter the management group and ensure that Configure the Windows Firewall for the Server is selected.
  16. Click Next.
  17. If you do not have a WSUS server, select Install the Patch Manager WSUS service (Recommended), and click Next. If you have a WSUS server, select I'll supply my own WSUS server, and click Next.
  18. Select how Patch Manager should configure IIS.
  19. Enter a location that Patch Manager can use to locally store the updates. 
  20. Select Provision the WSUS Server to the Patch Manager to manage WSUS from Patch Manager, and click Next.
  21. Enter the administrator credentials for Patch Manager, and click Next.
  22. Select your SQL instance, enter the credentials, and click Next.
  23. Select Use the default service account or enter different service account credentials for Patch Manager, and click Next. 
  24. Click Finish.
Last modified