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 > Wake on LAN > Scenario 3: Using an Application Role Server to Manage Console Connections

Scenario 3: Using an Application Role Server to Manage Console Connections

Table of contents
No headers
Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 59 Votes: 0 Revisions: 4

A typical example of this scenario is using multiple Application role servers to manage a large number of console connections. This example also serves to address High Availability (HA) requirements. For the HA scenario, deploy at least three Application role servers:

  • The PAS, which Patch Manager does not use for console connections.
  • At least two Secondary Application Servers (SAS), which can segregate groups of console users and/or back one another up in case of a failure.

Additional Application Role Servers for High Availability (HA)

File:Success_Center/New_Articles/PatchManager_Admin_Guide_MT/0F0/0D0/0300000B_427x382.png

This HA scenario scales to as many Application role servers as you require. If necessary, each console user could have a dedicated Application role server for their console connection.

Last modified

Tags

Classifications

Public