Agent Client Collector deployment checklist

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Successful Agent Client Collector (ACC) implementations, especially involving large numbers of endpoints or servers, require careful deployment. When proceeding with a large-scale ACC deployment, follow the steps described in the deployment checklist.

    Table 1. Agent Client Collector deployment
    Step number Action Description
    1 Update production and sub-production instances Ensure that all instances are updated to the most recent store applications, family releases, or both.
    2 Assess instance capacity Open support tickets if additional instance capacity is needed for the projected number of ACC agents.
    3 Deploy and configure MID Servers when required If connecting over 1,000 ACC agents to a single MID Server, assess performance and whether a load balancer in front of a MID Server is needed.
    4 Verify whether ITOM Cloud Services (ICS) is required and, if so, whether it is configured Some use cases (such as DEX) always require ICS.
    5 Download appropriate installer files from the instance Installer files may be in one of the following formats:
    • .rpm
    • .msi
    • .pkg
    6 Define a deployment calendar Share deployment groups and group size, assignments, start/stop, success gates, go/no-go signers, and rollback criteria with stakeholders.
    7 Package ACC in appropriate software management tools Software management tools include:
    • Intune
    • jamf
    8 Deploy pilot and test environments on sub-production instances using your preferred software management tool In test and pilot environments, you can test multiple operating systems and hardware combinations (such as server vs. laptop).
    9 Monitor the ServiceNow instance and the software management solution
    • On the instance, monitor the performance and rate limit violations.
    • On the software management solution, monitor the deployment success rate.
    10 Assess data collection, install success rate, and instance performance over the next 2-3 business days Workloads and data collection can vary significantly, depending on the time of day; therefore, monitor deployment success over several days.
    11 Update deployment calendar and continue with next install cohorts After successful deployment, continue with data collection.