Automatic MID Server selection

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Automatic MID Server Selection

    The Automatic MID Server selection feature enhances the efficiency of agents by ensuring they use the most suitable available MID Server. While this feature is disabled by default, it offers several advantages worth considering based on specific use cases.

    Show full answer Show less

    Key Features

    • Efficiency: Automatically narrows down the list of MID Servers based on their capabilities, optimizing connections.
    • Automatic Updates: Keeps the back-end URL configuration updated without requiring additional workflows.
    • Connectivity Testing: Agents perform tests to select the best MID Server based on latency and connection load.

    However, it is important to note that this selection acts as a fail-over mechanism rather than a true load balancer. The configuration complexity increases as the back-end URL is derived from multiple sources, potentially leading to security alerts if agents connect to MID Servers in restricted areas.

    Key Outcomes

    When enabled, agents receive periodic updates from the ServiceNow instance and select primary and secondary MID Servers for fail-over protection. Changes in network context may affect connectivity, so DNS configurations should be carefully managed. For secure communication, the MID Server's unified key store should be utilized.

    To utilize this feature, ensure that MID Servers are configured with Agent Client Collector capabilities and consider blocking specific MID Servers from agent connectivity as necessary.

    Automatic selection of MID Servers ensures that each agent uses the most efficient available MID Server.

    The Agent Client Collector automatic MID Server selection feature set is disabled by default. There are several factors to consider before determining if automatic MID Server selection is right for your use cases.

    Use case considerations

    Automatic MID Server selection provides several benefits. MID Server capabilities can narrow the list of MID Servers an agent can potential connect to. Automatic MID Server selection keeps the back-end URL configuration list up to date on the agent host without additional work flows.

    When automatic MID Server selection is enabled, the agent performs a connectivity test against the list of available MID Servers and determines the best connection based on latency and number of currently connected agents.

    However, there are several additional considerations that may make automatic MID Server selection wrong for your use case.

    The ACC automatic MID Server selection is not a true load balancer and should be considered a fail-over mechanism. There is higher complexity for choosing a back-end URL as it is derived from multiple input sources. If, instead, an application load balancer is used only one back-end URL needs to be specified. See Enable the Agent Client Collector load balancer for more information.

    By default, each agent is sent the list of all MID Servers listening for ACC connections. Since that list includes MID Servers running in restricted areas, the agents can try to connect to them which can generate security alerts.

    Your DNS configuration should be considered before using automatic MID Server selection because the resolution can lead to unexpected results. The DNS resolution is done periodically. End User Compute systems that alternate between internal corporate, Wi-Fi, VPN, or external networks may not be able to reconnect if the network context has changed.

    Automatic selection process

    When automatic selection is enabled, the ServiceNow instance sends periodic MID Server updates to existing agents. The agent selects a MID Server based on information it receives from the ServiceNow instance.

    During automatic MID Server selection, the agent selects a primary MID and a secondary MID list, and writes them to the agent’s config file. The agent uses this list for fail-over protection when the primary MID/secondary MID in the list loses connection.

    When an agent detects that its IP address has changed, it automatically connects with the most efficient MID Server available from the agent's list of MID Servers.

    To secure communication between the MID Server and the agent, use the MID Server's unified key store. For details on using the MID Server unified key store, see MID Server unified key store.