--- 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 deployment - servers # Agent Client Collector deployment - servers {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer When deploying the Agent Client Collector, perform deployment and management tasks on your environment's servers. Server deployment uses MID Servers to connect your agents to a ServiceNow instance. Agents deployed on data center servers open WebSocket connections to your MID Servers, which relay data to your instance. You manage the sizing, certificates, and load balancing of the MID Server. Use server deployment when your agents are in controlled environments such as data centers, where you are already running MID Servers and want to keep traffic on your network. Agent Client Collector Monitoring (ACC-M) and Agent Client Collector Log Analytics (ACC-L) require server deployment, and you can deploy Agent Client Collector for Visibility - Content (ACC-VC) with servers as well. * **[Configuring Agent Client Collector with a MID Server](https://servicenow-prod.fluidtopics.net/XcXO6WIT9qQwjVOQlyHs8w)** Configure the Agent Client Collector with a MID Server to enable communication between network servers and the ServiceNow instance. * **[Agent Client Collector installation](https://servicenow-prod.fluidtopics.net/x_3rxiHpsFUeJY7eOdJReQ)** 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. * **[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 Windows machine](https://servicenow-prod.fluidtopics.net/A5U0I0LUThaUi13mfomTcA)** When installing the Agent Client Collector on a Windows machine, either download an installation file and use a wizard to install the agent manually, or use silent installation to automate agent installation and configuration. Manual installation enables you to test the agent on a single system, while silent installation enables you to deploy the agent at scale. * **[Create and edit Agent Client Collector plugins](https://servicenow-prod.fluidtopics.net/OFg7qrGWPzEANyW_5aI_Sw)** You can edit the default plugins, or you can add new plugins, as needed. Creating and editing plugins customizes the Agent Client Collector monitoring capabilities. * **[Optimize distribution of agents to MID Servers](https://servicenow-prod.fluidtopics.net/K4itnhsXo4Geb1tGRQ0iVQ)** Optimize the distribution of agents by allowing redistribution from one MID Server to another. Agents will always be connected to the MID Server with the fastest response time. * **[View the Agent Client Collector configuration file for an agent](https://servicenow-prod.fluidtopics.net/dEOGzD7rz_VFUJTeYGmw0Q)** View the acc.yml Agent Client Collector configuration file without having to access the host server by retrieving the file from an agent. * **[Create an Agent Client Collector configuration data file](https://servicenow-prod.fluidtopics.net/Gjkqg1K0SBhpp2v2auJ1AQ)** Create an Agent Client Collector configuration data file and associate it with check definitions so that you can view the information about your instance. You can also add or delete an attachment to the configuration data files, which are used by check definitions during check executions. * **[Validate plugins on the MID Server](https://servicenow-prod.fluidtopics.net/rIDMv89hFJPRcK_uXiGjUg)** Validate plugins on your MID Server to ensure that they match the plugins on your ServiceNow instance. Validating plugins ensures that the instance provides accurate data on all of your MID Server plugins. * **[Validate plugins on agents](https://servicenow-prod.fluidtopics.net/swVgYWPY24X6kPnwAdES4w)** Validate plugins on your agents to ensure that they match the plugins on your ServiceNow instance. Validating plugins ensures that the instance provides accurate data on all of your agents' plugins. * **[Using proxy agents in Agent Client Collector](https://servicenow-prod.fluidtopics.net/DhYqZECC3q5AhFoVDMn3wQ)** You can use a proxy agent to monitor the health and performance of your configuration items (CIs) even if the agent is in the cloud or any place that is external to your host server. * **[Enable log monitoring in a Linux environment](https://servicenow-prod.fluidtopics.net/vJ7UZIysf_4nfCx5s65_yw)** To enable monitoring logs in a Linux environment, select the relevant policy and assign specific check parameters to the policy. When log monitoring is enabled and a specified string is discovered in the log being monitored, the system creates an event. * **[Enable log monitoring in a Windows environment](https://servicenow-prod.fluidtopics.net/w2Hp83vhduSX0qHADXuRwQ)** To enable monitoring logs in a Windows environment, select the relevant policy and assign specific check parameters to the policy. When log monitoring is enabled and a specified string is discovered in the log being monitored, the system creates an event. * **[Select the Azure policies to activate for metric collection](https://servicenow-prod.fluidtopics.net/TcJwx7HnzvoESjPWp74tXw)** Activate the Azure policies that come with the Agent Client Collector base system so that Azure virtual machines can collect metrics. These metrics help you monitor the configuration items (CIs) in the CMDB. * **[Use the Agent Client Collector Health Dashboard](https://servicenow-prod.fluidtopics.net/x8s35QGa8J1kHhUGwnRJnw)** The Agent Client Collector Health Dashboard enables you to monitor the status of the agents in your system. * **[Agent Client Collector Discovery](https://servicenow-prod.fluidtopics.net/CHtEnCuw8bYe90Ip8K46sQ)** Discover CIs in your environment by using Agent Client Collector for Visibility - Content (ACC-VC) Discovery. ACC-VC works with both horizontal IP-based Discovery, and you can also use push-based Discovery. * **[Agent Client Collector Log Analytics setup](https://servicenow-prod.fluidtopics.net/d2DVJemWcv_Qk~Socm6_pQ)** Configure Agent Client Collector Log Analytics on your ServiceNow instance either with or without using guided setup.