Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Patch Manager > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Scenario 2: Using Additional Automation Role Servers for Geographically Distributed Networks

Scenario 2: Using Additional Automation Role Servers for Geographically Distributed Networks

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

Views: 26 Votes: 0 Revisions: 5

A typical example of this scenario is placing an additional Automation role server at each remote location in a geographically distributed network. Use this configuration with either a replica WSUS server at each remote location, or an always-on desktop system to host the Automation role server.

Additional Automation Role Servers for Geographically Distributed Networks

File:Success_Center/New_Articles/PatchManager_Admin_Guide_MT/0F0/0B0/03000009_480x331.png

Another example is to use a separate Automation role server to offload work from the PAS. Use the following configuration if the PAS cannot complete tasks quickly enough due to the number of managed clients in the local network.

File:Success_Center/New_Articles/PatchManager_Admin_Guide_MT/0F0/0B0/0300000A_339x271.png

Automation Server Routing Rule for Scenario 2

In this scenario, use the Absolute Rule option to instruct Patch Manager to abandon the task if none of the Automation role servers you explicitly define for a location are online.

To create the rule for this scenario:

  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), click Add Subnet Rule.
  5. Complete the Add TCP/IP Subnets dialog:
    1. In the IP Address field, enter the IP address for the subnet.
    2. In the Subnet Mask menu, select the subnet mask.
    3. Modify the Starting Address or Ending Address fields as necessary.
    4. In the Description field, enter a description for the subnet.
    5. Click Add Subnet.
    6. Repeat these steps for any additional subnets.
  6. Click OK.
  7. Complete the Select Automation Server(s) for routing rule and rule type dialog:
    1. Select the additional Automation role servers.
    2. Select Absolute Rule.
    3. Click OK.
Last modified
01:13, 23 Jun 2016

Tags

Classifications

Public