--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management Release : - australia ft:locale : - de-DE ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # ACC installation # Agent Client Collector installation {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer 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, while 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. 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 ACC-VC, a default 1 GiB MID Server can support 400 agents concurrently. An 8 GB configuration for a MID Server can support 2,000 agents concurrently. 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 | [Tabelle : 1. Agent on Endpoints Deployment] {#acc-installation__table_w4y_x2d_kfc} If you completely reinstall the agent on a single host server, a second agent record registers on the instance. 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://servicenow-prod.fluidtopics.net/hC34ZCuztwjNG7Ga~wLR0A "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. 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. * **[Agent Client Collector system requirements](https://servicenow-prod.fluidtopics.net/07a2Cw7M_aSz7SKiS~e06w)** System requirements are the fundamental specifications and configuration needed to install and run Agent Client Collector (ACC) effectively. * **[Incorporating the Agent Client Collector into a custom base image for mass deployment](https://servicenow-prod.fluidtopics.net/SkYeCkebwPun_XEYAxfezA)** Deploy the Agent Client Collector on a virtual machine during mass deployment using the machine's base image. Mass deployment uses silent installation, which hides installation status. * **[Enable the Agent Client Collector load balancer](https://servicenow-prod.fluidtopics.net/EeehuBlG78MPGycdIRTV2A)** Enable a load balancer to ensure that you have functional MID Servers. A load balancer distributes resources over multiple MID Servers to ensure that no single MID Server is overloaded. * **[Upgrade an agent in an instance](https://servicenow-prod.fluidtopics.net/bNhgLGeCQ2baGMqfHXlorQ)** Perform selective self-upgrade instead of bulk upgrade for enhanced efficiency when working with agents that are difficult to access, such as agents deployed in the cloud. You can perform selective upgrade on up to 20 agents at a time. * **[Upgrade multiple agents in an instance](https://servicenow-prod.fluidtopics.net/G3KmzkMIoWEiMcp3V_kZvw)** When performing selective upgrade of an agent in an instance, you can select multiple instances to upgrade at once. * **[Perform high-volume Agent Client Collector upgrade](https://servicenow-prod.fluidtopics.net/AoOLP2fWTuFjxMGw_1TXAQ)** Perform high-volume upgrade of your Agent Client Collector agents when you want to upgrade all of your agents at one time. * **[Configure proxies when performing MID-less upgrade using a Content Delivery Network (CDN)](https://servicenow-prod.fluidtopics.net/20bKOl~53WgWPT_iZkZ9lQ)** Create proxies for added security when upgrading MID-less agents via a Content Delivery Network (CDN). You add proxy servers to the sn_agent_proxy table on the ServiceNow instance. * **[Restart an agent manually](https://servicenow-prod.fluidtopics.net/Sjjp7pfMryaB2RPSDa8Tzw)** Perform manual restart of an agent when the agent configuration file has been refreshed, or if the agent is unstable. You can perform manual restart only on agents installed in a Windows environment and for Linux-based agents that use `systemd`. **Zugehörige Konzepte** * [Agent Client Collector installation on a Linux OS system](https://servicenow-prod.fluidtopics.net/b0f4XepBZFv3m0fxPcNgUA "Install Agent Client Collector on a system that uses a Linux OS, either using a single-line command script, or following the installation procedure to embed 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://servicenow-prod.fluidtopics.net/zYqOshLaddr5NfO2guLE4g "Install Agent Client Collector on a system that uses macOS. You can either 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.") **Zugehörige Tasks** * [Install the Agent Client Collector on a Windows machine manually](https://servicenow-prod.fluidtopics.net/hOmZU9UYzt_y6NNqOmm~wQ "Install the Agent Client Collector on a Windows machine manually when you want to test the agent on a single system.")