Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn More.


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: 12 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
01:13, 23 Jun 2016