Orchestration with multiple MID Servers

When determining if multiple MID Servers are necessary to execute Orchestration activities, consider the following factors:

  • WAN deployment: When determining where to deploy MID Servers in a WAN, consider the bandwidth available between your local area networks. In most cases, the best practice is to install a MID Server on each LAN to probe devices locally, rather than deploying MID Servers that must probe devices across slow WAN connections. An alternative to this type of deployment is to install MID Servers that probe other LANs via VPN connections that take advantage of fast Internet connections. If the bandwidth of the WAN connections is comparable to that of the Internet connection, then there is no performance impact in running MID Server probes across WAN connections.
  • DMZ: Network policy might require the installation of one or more MID Servers in the DMZ to probe the devices there. This is common in networks that tightly regulate the ports that are opened on the inside firewall.
  • Security: If a security policy controls access to computers with an access control list (ACL), it might be necessary to install one or more MID Servers on a machine in the network that is already on the ACL.
  • Probe types: If Orchestration launches probes for different operating systems, network policy might require a separate MID Server for each type of probe (e.g., one MID Server for Windows PowerShell and another for SSH probes on UNIX).