Submit a ticketCall us
Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Additional Automation Server Scenarios

Additional Automation Server Scenarios

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

Views: 673 Votes: 0 Revisions: 4

Scenarios that warrant deploying additional Automation role servers are the most common when implementing Patch Manager in large or distributed networks. Patch Manager uses Automation role servers to initiate RPC/WMI connections to remote systems. When you deploy additional Automation role servers, Patch Manager can target more systems simultaneously. Furthermore, when you deploy Automation role servers closer to the remote systems they manage, the RPC/WMI connection has to travel a lesser distance.

Automation Server Routing Rules

Patch Manager uses Automation Server routing rules to manage what tasks go to what Automation role server. Furthermore, Automation Server routing rules define whether or not to assign a task to the default round-robin pool if the assigned server(s) is/are unavailable. In this way, Automation Server routing rules result in one of four general rule definitions:

  • An absolute rule for a specific Automation role server
  • A rule with a preferred Automation role server that relies on the default pool when needed
  • An absolute rule for a specific pool of Automation role servers
  • A rule with a pool of preferred Automation role servers that relies on the default pool when needed

In any case, you can define specific Worker Process Settings to limit the capacity of each Automation role server. For additional information, see "Automation Server Settings".

To define Automation server routing rules:

  1. In the left pane of the Patch Manager console, expand Patch Manager System Configuration > Management Groups.
  2. Select the management group for which you want to configure the rule.
  3. In the center pane, click the Automation Server Routing Rules tab.
  4. In the Actions pane (right), select the action for the type of rule you want to create.
  5. In the dialog that opens, specify the system(s) you want to target.
  6. Complete the Select Automation Server(s) for routing rule and rule type dialog:
    1. Select one or more Automation role servers to assign to the rule.
    2. If you want to restrict the rule to only the server(s) you selected, select Absolute Rule.
    3. Click OK.

The following two scenarios illustrate a use case for additional Automation role servers, and then describe how to create the appropriate Automation server routing rules to address them.

Last modified