---
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 planning checklist

# Agent Client Collector planning checklist {#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 planning checklist

Implementing the Agent Client Collector (ACC) effectively, especially at scale, requires thorough planning to ensure successful data collection and integration with ServiceNow.
This checklist guides ServiceNow customers through essential preparatory steps before large-scale ACC deployment, helping align technical, organizational, and security requirements with business goals.
Show full answer Show less  

## Planning Steps

* **Define Use Cases, Target Devices, and Success Metrics:** Identify the ACC use cases such as ITOM Visibility, ITAM, ITSM, or ITOM Health. Establish measurable success criteria, for example, ensuring a high percentage of targeted devices report data consistently over a defined period.
* **Identify Key Stakeholders:** Engage relevant teams early, including network, security, and device/software management experts (e.g., Jamf, Intune) to facilitate smooth deployment and support.
* **Assess Licensing and Instance Requirements:** Confirm possession of necessary ServiceNow licenses and app entitlements. Review instance configurations and updates required to handle the anticipated device volume.
* **Assess Software Requirements:** Validate ACC compatibility with all CPU architectures and operating systems in your environment. Determine if elevated privileges are needed on endpoints or servers. Explore alternative solutions if ACC does not support certain devices.
* **Assess Network Requirements:** Check for VPN, firewall, or proxy restrictions that could interrupt ACC data transmission to your ServiceNow instance.
* **Assess Device Management Requirements:** Identify internal deployment tools available for software distribution on endpoints (e.g., Intune, Jamf) and servers (e.g., Chef, Puppet, Ansible).
* **Draft ACC Solution Architecture:** Collaborate with your ServiceNow account team to design how ACC agents will communicate data to ServiceNow, considering distinctions between servers and endpoints and deciding between ITOM Cloud Services or MID Servers deployment models.
* **Define and Segment Deployment Plan:** Plan phased rollouts including evaluation, pilot, and broad deployment stages, each with defined device counts and aligned to risk and business priorities. Limit deployment speed to no more than 5,000 agents per hour.
* **Internal Compliance and Security Review:** Coordinate with internal teams to review and approve the deployment plan and architecture ensuring compliance with organizational policies.

## Practical Benefits

Following this checklist helps ServiceNow customers mitigate risks associated with large-scale ACC deployments by ensuring readiness across technical, organizational, and security dimensions. Proper planning facilitates a controlled, phased rollout that maximizes data collection success and supports your business use cases effectively.  
Successful Agent Client Collector (ACC) implementations, especially involving large numbers of endpoints or servers, require careful planning. Before proceeding with a large-scale ACC deployment, follow the steps described in the
planning checklist.
{#acc-planning-checklist__table_rnf_xjd_dhc__entry__3}

| Step number | Action | Description |
|-|-|-|
| 1 | Define use cases, targeted devices, and success metrics | Typical ACC use cases include ITOM Visibility, ITAM (SAM/HAM), ITSM (DEX), ITOM Health (HLA/Metric Intelligence). Many customers have success metrics targeting a percentage of devices with successful data collection for a use case over a 7 to 14-day window (for example, "95% of endpoints report software usage over a 14-day period"). |
| 2 | Identify Key Stakeholders | Involve network, security, and device/software management teams (such as jamf/Intune experts) as early as possible during planning. |
| 3 | Assess ServiceNow License, Store App and Instance Requirements | Ensure that you have all license entitlements for your use cases. Determine which software updates or configuration changes to your production and sub-production instances are needed to support your targeted number of devices. For details, see [Evaluating version requirements and dependencies](https://www.servicenow.com/docs/access?context=versions-dependencies&version=australia&pubname=australia-platform-administration&ft:locale=en-US). |
| 4 | Assess Software Requirements | 1. Ensure that all CPU architectures and operating systems for your use cases are supported. If not, determine whether non-ACC solutions such as Service Graph Connector or Discovery Patterns can be used. 2. Determine whether your use cases require elevated system privileges on endpoints or servers (for example, root access on Linux for device serial number tracking). {#acc-planning-checklist__ol_wgv_rkd_dhc} For details, see [Agent Client Collector system requirements](https://www.servicenow.com/docs/tCUVOsEarkxZFRtIpw6OLQ "System requirements are the fundamental specifications and configuration needed to install and run Agent Client Collector (ACC) effectively."). |
| 5 | Assess Network Requirements | Verify whether there are VPN, firewall, or proxy restrictions that prevent ACC from sending data to your ServiceNow instance. |
| 6 | Assess Device Management Requirements | Verify which internal solutions are available for deploying software within your organization on all targeted devices. For example, Intune and Jamf for endpoints; Chef, Puppet, or Ansible for servers. |
| 7 | Draft ACC Solution Architecture | Work with your ServiceNow account team to define how ACC agents send data to the ServiceNow instance, based on your use cases and differences in server and endpoint deployment techniques. Verify whether direct connections are made using ITOM Cloud Services or MID Servers. For details, see [Agent Client Collector architecture](https://www.servicenow.com/docs/nKJQ~~zB0MeSWCAGDZdCkg "The Agent Client Collector is a ServiceNow agent installed on your Windows, Linux, and macOS devices to monitor your company’s infrastructure and installed applications."). |
| 8 | Define and Segment your ACC Deployment Plan | Define evaluation, pilot, and broad rollout stages and the number of devices targeted in each phase. Align each segment with risk tolerance and business goals. ACC must be rolled out gradually, with no more than 5,000 agents per hour. |
| 9 | Internal Compliance and Security Review | Work with internal teams and your stakeholders to review your deployment plan, solution architecture, and to obtain approvals. |
[Table 1. Agent Client Collector planning]

{#acc-planning-checklist__table_rnf_xjd_dhc}