Agent Client Collector Installation

concept australia Updated Sep 10, 2026 3 min read acc-installation.md
Raw file servicenow.com

You can install the Agent Client Collector on any supported host machine. The Agent Client Collector connects to a MID Server using the HTTP/S protocol, and the connection remains active after being established. One MID Server may handle several agents simultaneously. A single agent works with one MID Server at a time and switches to a different MID Server when necessary to provide failover protection.

When an agent's IP address changes, it selects a MID Server to connect to based on the agent's MID Server list.

Verify that your server's OS and version is supported. For a list of supported OS's and versions, see ServiceNow Store Page

The maximum number of agents that can be connected to a single MID Server is configurable in the sn_agent.mid.max_allowed_agents MID Server property. The default value is 4,000.

For the list of required OS versions, see For a list of supported OS's and versions ServiceNow Store Page

For ACC-VC, a default 1 GiB MID Server can support 700 agents concurrently. An 8 GiB configuration for a MID Server can support 8,000 agents concurrently. You can also scale out. For example, 5 MID Servers with 8 GiB of heap size can handle up to 40k agents.

Agent Client Collector is installed with ruby version 3.3.2.

The default user account is a local user called servicenow. This user has basic level permissions.

The following table describes the permissions required to work with various features associated with the agent, per OS. An asterisk (*) indicates that no special permissions are required.

Feature

Windows

Linux

macOS

Basic inventory

*

*

*

Serial number(s)

*

sudo

dmidecode

*

Running processes

Debug programs

*

*

Mapping TCP connections to running processes

*

sudo ss

*

Storage devices

LOCAL SYSTEM

*

*

Logged-in users

LOCAL SYSTEM

*

*

Package self-upgrade

LOCAL SYSTEM

sudo rpm/dpkg

Not supported

If you completely reinstall the agent on a single host server, and you're using ITOM Cloud Services, you must delete the agent record to allow for re-registration. Delete the original agent on the **Agent Client Collectors** page \(**All** > **Agent Client Collector** > **Agents**\).

Agents whose Status = Down or Disconnected which haven't been deleted are deleted automatically after 30 days. You can modify this setting on the Autoflush form page (see Autoflush form).

Use the Manual Transport Layer Security protocol (mTLS) for secure authentication between your MID Web Server and the agent (the client). For details, see Connect the agent to the MID Server using mTLS.

For details on using Agent Client Collector in an air-gapped environment, see the Agent Client Collector Framework Air Gapped Configuration Item Management Solution [KB1585753] article in the Now Support Knowledge Base.

Golden image mode enables cloning of additional instances. Setting golden image mode is described in the installation procedure prerequisites for each OS. For information on the structure and modularity of the golden image plugin by operating system, see Golden image structure and modularity.

Agent Client Collector supports domain separation. The domain of the agent and the CIs it creates is determined by the domain of the MID Server that the agent is connected to. The user's domain must be the lowest domain level (known as a leaf domain) to enable creating a Websocket endpoint extension for the MID Server.

Related topics

Agent Client Collector installation on a Linux OS system

Install the Agent Client Collector on a Windows machine manually

Agent Client Collector installation on a macOS system

Search documentation
Search document titles and file paths on the australia branch