--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # ACC installation # Agent Client Collector Installation {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Agent Client Collector Installation The Agent Client Collector (ACC) can be installed on any supported host machine to enable data collection and communication with a ServiceNow MID Server. It uses HTTP/S for persistent connections, allowing one MID Server to manage multiple agents while each agent connects to only one MID Server at a time with failover capabilities. Proper OS support verification is essential before installation. Show full answer Show less ## Key Features * **Scalability:** Default MID Server settings allow up to 4,000 agents, configurable via the `snagent.mid.maxallowedagents` property. A 1 GiB MID Server supports approximately 700 agents, while an 8 GiB server supports up to 8,000 agents. Multiple MID Servers can be deployed to scale beyond these limits. * **Agent Software:** Installed with Ruby 3.3.2 and runs under a local user account named `servicenow` with basic permissions. * **Permission Requirements:** Different OS features require specific permissions; for example, Windows uses LOCAL SYSTEM for some operations, Linux requires sudo for commands like `dmidecode` and `ss`, and macOS has its own permission needs. Some features require no special permissions. * **Agent Management:** When reinstalling agents in ITOM Cloud Services, existing agent records must be deleted to allow re-registration. Agents with Down or Disconnected status are auto-deleted after 30 days by default, configurable via the Autoflush form. * **Security:** Supports manual Transport Layer Security (mTLS) for secure authentication between MID Web Server and agents. * **Special Configurations:** Supports operation in air-gapped environments and offers a golden image mode for cloning additional instances, with specific setup instructions per OS. * **Domain Separation:** The agent and its created Configuration Items (CIs) inherit the domain from the connected MID Server. The user domain must be a leaf domain to enable Websocket endpoint extensions. ## Practical Considerations for ServiceNow Customers * Confirm your server OS and version are supported via the ServiceNow Store before installation. * Plan MID Server sizing and scaling according to the number of agents you intend to manage. * Understand and configure necessary permissions on your endpoints to enable full agent functionality. * Manage agent lifecycle carefully, especially when reinstalling, to avoid conflicts in ITOM Cloud Services. * Implement mTLS for secure communications between agents and MID Servers. * Utilize golden image mode and domain separation features to optimize deployment and segmentation in your environment. 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](https://store.servicenow.com/store/app/bc09636e1be06a50a85b16db234bcbd1) 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](https://store.servicenow.com/store/app/bc09636e1be06a50a85b16db234bcbd1) 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.{#acc-installation__table_w4y_x2d_kfc__entry__4} | 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 | [Table 1. Agent on Endpoints Deployment] {#acc-installation__table_w4y_x2d_kfc} 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 (AllAgent Client CollectorAgents). 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](https://www.servicenow.com/docs/access?context=atf-auto-flush&version=australia&pubname=australia-application-development&ft:locale=en-US)). 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](https://www.servicenow.com/docs/9W7wslXzSuhwWoh83s1ctg "Before configuring mTLS authentication on the agent, you must run a series of commands that enable configuring Transport Layer Security (TLS) authentication."). 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\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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](https://www.servicenow.com/docs/1negMV5wJ96FLqRY6XlwCg "The following table outlines the structure and modularity of the golden image mode for cloning agents, based on the operating system (OS) in use."). 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 concepts** * [Agent Client Collector installation on a Linux OS system](https://www.servicenow.com/docs/e7Zu7Jvw_~GA5aGDS46kqQ "Install Agent Client Collector on a system that uses a Linux OS. Use a single-line command script, or follow the installation procedure to embed the agent in your own package distribution mechanism. The installation procedure provides consistency when using package distribution solutions.") * [Agent Client Collector installation on a macOS system](https://www.servicenow.com/docs/f5j3bK5HEImOk_1mdTFY9A "Install Agent Client Collector on a system that uses macOS. Use a single-line command script, or follow a manual installation procedure if the agent is not connected to the instance or you want enhanced customization options.") **Related tasks** * [Install the Agent Client Collector on a Windows machine manually](https://www.servicenow.com/docs/LtZicVxUm2xclz_5tKNSEw "Install the Agent Client Collector on a Windows machine manually when you want to test the agent on a single system.") *[\>]: and then