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

---
title: Configure the automatic MID Server selection based on the Agent Client Collector capabilities
description: 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.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/agent-client-collector/configure-auto-mid-eligibility-by-capability.html
release: australia
product: Agent Client Collector
classification: agent-client-collector
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Automatic MID Server selection, Configuring ACC with a MID Server, ACC deployment - servers, Configuring Agent Client Collector, Agent Client Collector, IT Operations Management]
---

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

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. To block a MID Server from automatic selection, assign it different ACC capabilities from all other MID Servers in your environment. Do not assign different capabilities from the primary MID Server.

## Procedure

1.  Configure the Agent Client Collector capabilities for MID Servers, as described in [Configure the Agent Client Collector capabilities for MID Servers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/agent-client-collector/configure-acc-capability.md).

2.  Navigate to **All** > **Agent Client Collector** > **MID Servers**.

3.  Select the MID Server that you want to be ineligible for automatic MID Server selection.

4.  Select the additional actions icon \[Omitted image "additional-actions-icon.png"\] Alt text: Additional Actions icon. and select **View** > **Default 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

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.
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.


**Parent Topic:**[Automatic MID Server selection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/agent-client-collector/acc-auto-mid-selection.md)