---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# ACC system requirements

# Agent Client Collector system requirements {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
System requirements are the fundamental specifications and configuration needed to install and run Agent Client Collector (ACC) effectively.

Verify that your server's OS and version is supported. For a list of supported OS's and versions [ServiceNow Store Page](https://store.servicenow.com/store/app/bc09636e1be06a50a85b16db234bcbd1)

Before installing the Agent Client Collector, you must do the following:

* When working with a MID Server:
  * Ensure that one or more MID Servers are properly registered and validated with your instance, to be available for an agent connection request. For details, see [Configuring MID Servers](https://www.servicenow.com/docs/access?context=c_MIDServerConfiguration&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). In a staging environment, you need only one MID Server. However, in a production environment, configure at least two MID Servers to support zero-touch configuration and ensure that a MID Server is always available if one fails.
  * Ensure that there's a validated connection from the designated server where you're installing the agent to the MID Server.
  * Ensure that the MID Server port on which the Agent Client Collector listener runs is accessible.
  {#acc-sys-requirements__ul_qs1_2nk_3fc}
* When working with MID-less deployment, follow the instructions described in [Configuring MID-less Agent Client Collector](https://www.servicenow.com/docs/80ZyTDnt8y3ct~KiOdbj1w "Configure MID-less Agent Client Collector to enable sending information through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.").
* Ensure that the following plugins are installed on your instance:{#acc-sys-requirements__table_fq2_nnv_hfc__entry__2}

  | Application | Plugin |
  |-|-|
  | ACC-F | * MID Server * CMDB for scoped applications * Agent Client Collector global utilities * MID Web Server * Service Error Management {#acc-sys-requirements__ul_qs5_z2b_mfc} |
  | ACC-VC | * Agent Client Collector for Visibility Content * Agent Client Collector Framework * Discovery \[com.snc.discovery\] plugin {#acc-sys-requirements__ul_ans_pnv_hfc} |
  | ACC-M | * Agent Client Collector Framework * Agent Client Collector Monitoring * Event Management and Service Mapping Core * Metric Intelligence - \[com.snc.sa.metric\] plugin {#acc-sys-requirements__ul_bp4_m4v_hfc} |
  | ACC-L | * Agent Client Collector Framework * Agent Client Collector Log Analytics * Health Log Analytics {#acc-sys-requirements__ul_svz_n4v_hfc} |
  | DEX | * Agent Client Collector Framework * ITOM Cloud Services Core \[sn_itom_cloud_svc\] {#acc-sys-requirements__ul_vsp_42b_mfc} |
  [ ]

  {#acc-sys-requirements__table_fq2_nnv_hfc}

  You can verify that these plugins are installed on the System DefinitionsPlugins page.

  All plugins that come with the base system are signed with the ServiceNow certificate. Optionally, you can use custom plugins and sign them using your own certificate, as described in [Enable OpenSSL secure signing for plugins](https://www.servicenow.com/docs/TAVtC878l9mnZJrMwap_0g "Create a self-signed certificate for an Agent Client Collector plugin. The following procedure gives an example of how to create an x509 certificate using OpenSSL. For other certificate types, consult OpenSSL documentation.").
* Ensure that your system has the minimum requirements for agent installation.{#acc-sys-requirements__table_xfj_pz4_hbc__entry__2}

  | Agent Client Collector component | Requirements |
  |-|-|
  | Agent Client Collector Framework | * 1 GB RAM * 300 MB free disk space * 1 CPU core {#acc-sys-requirements__ul_zwz_5z4_hbc} |
  | Agent Client Collector Monitoring | * 1 GB RAM * 1 GB free disk space * 1 CPU core {#acc-sys-requirements__ul_lvm_jyc_3bc} |
  | Agent Client Collector for Visibility Content | * 1 GB RAM * 1 GB free disk space * 1 CPU core {#acc-sys-requirements__ul_lq2_yz4_hbc} |
  [Table 1. Minimum installation requirements]

  {#acc-sys-requirements__table_xfj_pz4_hbc}
* Ensure that you're installing Agent Client Collector on one of the supported operating system distributions. For details on the supported operating systems, see [Agent Client Collector Framework](https://store.servicenow.com/store/app/bc09636e1be06a50a85b16db234bcbd1) in the ServiceNow® Store.{#acc-sys-requirements__os-supported}
{#acc-sys-requirements__os-supported}

{#acc-sys-requirements__ul_s25_4th_xkb}  
Important:  
All supported operating systems work only with the x86-64 CPU architecture type. ACC-F v3.1.1 also adds native support for ARM64 on Apple Silicon architectures. For the latest information, see the [Agent Client Collection on non- x86-64 computers and embedded boards \[KB1172387\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1172387) article in the Now Support Knowledge Base.

When using ACC-L: The Agent Client Collector comes with the default servicenow user. Ensure that this user has read access to enable Agent Client Collector to view all the configured log paths. For example, the Agent Client Collector servicenow user that comes installed with the base system does not have permissions to view the paths to /var/log/ in Linux and C:\\Windows\\System32 in Windows. For information about configuring permissions for the servicenow user, see the [ACC-L Permission Denied issues
\[KB1117271\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117271) article in the Now Support Knowledge Base.

When determining the number of machines and servers needed to support your agents (such as the number of machines requiring proxy agents), consider the agents' performance KPIs. For details on agent
performance KPIs, see [Agent Client Collector performance and footprint for URL monitoring](https://www.servicenow.com/docs/vnvYWZ_laDBXsk_a7D6pYg "The following tables display the agent performance KPIs and its footprint on the host during URL monitoring data collection execution on different operation systems.").

*[\>]: and then