---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure the automatic MID Server selection based on the Agent Client Collector capabilities

# Configure the automatic MID Server selection based on the Agent Client Collector capabilities {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure the MID Servers that are ineligible for automatic MID Server selection with the agent. For example, you may want to block a MID Server from connecting to your agent due to firewall constraints.

## Before you begin

Role required: agent_client_collector_admin

## About this task

Agents with different levels of Agent Client Collector (ACC) capability can't be considered for automatic MID Server selection. If you want to block a MID Server from automatic MID Server selection, you can assign the MID Server different ACC capabilities from all MID Servers, but not the primary MID Server, in your environment.

## Procedure

1. Configure the Agent Client Collector capabilities for MID Servers, as described in [Configure the Agent Client Collector capabilities for MID Servers](https://servicenow-prod.fluidtopics.net/YccJZNPi4l9TttBalmOGcA "Configure the MID Servers with Agent Client Collector capabilities to enable the MID Servers to work with agents. Agents that have identical MID Server capabilities are eligible for automatic MID Server selection.").
2. Navigate to AllAgent Client CollectorMID Servers.
3. Select the MID Server that you want to be ineligible for automatic MID Server selection.
4. Select the additional actions icon ![Additional Actions icon.]() and select ViewDefault View.
5. Select the Capabilities tab.
6. Ensure that the MID Server isn't assigned with the capabilities that have Is ACC Capability=true on the Capabilities tab.

## Configuring MID Servers to be ineligible for automatic MID Server selection {#configure-auto-mid-eligibility-by-capability__example_q43_3tn_qzb}

1. Assign the AgentClientCollector capability to MID Server A and MID Server C, but not to MID Server B.
2. On the MID Server Capabilities page:
   1. Assign a capability to MID Server A and MID Server C.
   2. Assign a different capability to MID Server B.
   {#configure-auto-mid-eligibility-by-capability__ol_jhf_5wn_qzb}
3. Install Agent Client Collector Framework and specify MID Server A as the MID Server during installation.

   After installation, the agent has Status=Up and its MID Server is MID Server A.
4. Execute the MID Server Selection scheduled job to determine which MID Servers are eligible for automatic MID Server selection.

   MID Server B is ineligible for automatic selection, because it doesn't have the same ACC capability as MID Server A. MID Server C is eligible, because it has the same ACC capability as MID Server A.
{#configure-auto-mid-eligibility-by-capability__ol_lyy_ntn_qzb}

*[\>]: and then