Submit a ticketCall us
Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Server Role Definitions

Server Role Definitions

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

Views: 551 Votes: 0 Revisions: 3

Patch Manager consists of three server roles:

  • Application
  • Management
  • Automation

By default, all Patch Manager servers include the Automation role. When you deploy additional Patch Manager servers, you have the option of deploying just an Automation role server, or adding one or both of the other roles. The first Patch Manager server you deploy is the Primary Application Server (PAS), and it contains all three server roles.


  • SolarWinds licenses Patch Manager by the number of computers it manages. As such, there are no additional license costs associated with deploying additional Patch Manager servers.
  • All Patch Manager servers, regardless of their role, require their own instance of SQL Server.

Application Server

Interfaces with the MMC-based administration console, Orion Platform web console, and ConfigMgr integrated console. Servers in this role also manage all communication between the console and the rest of the Patch Manager environment. Configure Application role servers to work with one or more servers in the Management role to specify what systems can be managed by what Patch Manager consoles.

Management Server

Maintains all inventory and discovery data for specific systems in the Patch Manager environment. Each Management role server hosts a management group defined by a collection of managed domains, workgroups, or WSUS servers. Deploy additional Management role servers to partition managed systems into defined security or network management boundaries.

Automation Server

Manages the local Patch Manager worker processes on each Patch Manager server. The worker processes perform the inventory and configuration management tasks and interface with the Windows Management Instrumentation (WMI) providers to collect data and supervise remote management capabilities. Deploy additional Automation role servers to support load balancing scenarios, fault tolerance scenarios, or isolated/access-controlled networks, such as a perimeter (DMZ) network.

Last modified