Agent Client Collector installation
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 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.
| 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, a second agent record registers on the instance. Delete the original agent on the Agent Client Collectors page ().
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.
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.