Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Patch Manager > Patch Manager Documentation > Patch Manager 2.1.5 Administrator Guide > Wake on LAN > Use additional Automation Servers to manage geographically distributed networks

Use additional Automation Servers to manage geographically distributed networks

Created by Caroline Juszczak, last modified by Steve.Hawkins on Jul 10, 2018

Views: 523 Votes: 0 Revisions: 6

If your managed computers are spread out across a geographically-distributed network, install an Automation Server on a duplicate WSUS server or a dedicated desktop system in each remote location.

SPM-Admin-Guide-Scenario-2-Distributed-Network.png

Additionally, you can install a separate Automation Server to offload task management 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. In this configuration, the Automation Server on the PAS provides a backup for the secondary Automation Server. 

SPM-Admin-Guide-Scenario-2-5-Distributed-Network.png

Create an Automation Server routing rule for this example

Use the Absolute Rule  option to instruct Patch Manager to abandon a task if none of the Automation Servers you explicitly define for a location are online.

  1. Log in to the Patch Manager Administrator Console as an administrator.
  2. In the navigation pane, expand Patch Manager System Configuration > Management Groups.
  3. Select the targeted management group for the configuration rule.
  4. In the center pane, click the Automation Server Routing Rules tab.
  5. In the Actions pane (right), click Add Subnet Rule.
  6. 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.
  7. Click OK.
  8. Complete the Select Automation Server(s) for routing rule and rule type dialog box.
    1. Select the additional Automation role servers.
    2. Select Absolute Rule.
    3. Click OK.
Last modified

Tags

Classifications

Public