Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Advanced Configuration Options > Configuring Remote Administration Consoles

Configuring Remote Administration Consoles

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

Views: 62 Votes: 0 Revisions: 4

In addition to the Patch Manager console included on your PAS, you might want to install additional remote administration consoles throughout your environment. You must associate each console and server with a Patch Manager Application role server. This could be the PAS or any other Patch Manager server in the Application server role.

Installing the Patch Manager Console

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

Note: If you plan on integrating Patch Manager with ConfigMgr, install all Patch Manager consoles on computers that already have the ConfigMgr console installed.

To install a Patch Manager console on a remote system:

  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 Application Server, and click Next.

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

Last modified