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 > 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: 397 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)


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