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 > Distribute the Patch Manager servers

Distribute the Patch Manager servers

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

Views: 514 Votes: 0 Revisions: 4

You can distribute multiple Patch Manager servers in your environment for load balancing and fault tolerance, and to resolve issues caused by geographic distribution or securities boundaries within your organization. When you deploy multiple Patch Manager servers, consider the following requirements:

Geographically-distributed environments

In geographically-distributed environments, deploy an additional Automation Server role to each remote site. This server role allows you to facilitate client management and configuration processes on the local LAN of the target systems rather than across the WAN

You can also deploy additional Management Server roles to each site to segregate management and data collection tasks. Management Server roles work in conjunction with the additional Application Server role to support remote system administrators.

Large environments

In large environments with multiple subnets or large inventory requirements, deploy additional Application and/or Management role servers to optimize your Patch Manager environment. Use additional Application role servers to support multiple administration consoles. Use additional Management role servers to create smaller management groups for administration and reporting.

Wake-on-LAN

In environments that implement Wake-on-LAN (WOL), deploy additional Automation role servers to facilitate WOL broadcasts for distributed systems. This helps administrators avoid the need to configure routers to support this functionality. It also increases the overall reliability by restricting WOL broadcasts to smaller, LAN-specific network domains.

Port Considerations and bandwidth restrictions

In environments with open port or bandwidth issues, you can deploy additional Automation Server or Management Server roles to minimize these issues. You can add additional Application role servers to limit WAN communication to port 4092—the port used for server-to-server communication. With an Automation Server role on each LAN, the remaining ports required in the Patch Manager environment must only be open on each LAN.

Additionally, use additional Management Server roles to limit the amount of traffic traveling across the WAN. With a Management Server role on each LAN, inventory data will cross the WAN only if a Patch Manager administrator runs a report for that LAN from a remote site.

Last modified

Tags

Classifications

Public