0
7.0.4
Australia, Zurich, Yokohama
Integration
The ServiceNow® Agent Client Collector (ACC) can be installed on infrastructure components, such as servers and endpoints. It executes commands on the host machines and sends output data to the ServiceNow instance. The ACC is a single software agent for ServiceNow and enables the following use cases:
- Visibility and Monitoring
- Hardware and Software Asset Management
- IT Service Management
Managing the Agent Client Collector with a ServiceNow instance is part of the Agent Client Collector Framework application.
The ACC application provides centralized agent management. ACC Framework is the foundation for applications that run on it. It is suitable for on-premises servers, VMs, and cloud instances (AWS, Azure, GCP), as well as end-user desktops and laptops.
Supported Operating Systems on x86_64 architecture for this version:
- Linux
- Red Hat Enterprise Linux - 10, Rocky Linux - 10, Oracle Linux - OL 7, 8, 9, 10
- CentOS 7, CentOS Stream 8 and 9
- SLES 12, 15
- Ubuntu 18.04, 20.04, 22.04 LTS and 24.04 LTS
- Debian 9, 10, 11, 12 and 13
- Amazon Linux 2, Amazon Linux 2023
- Microsoft Windows
- Windows Server 2012, 2012r2, 2016, 2019, 2022, 2025
- Windows 10 Enterprise Edition
- Windows 11 Professional and Enterprise
- MacOS (x86_64 only)
- 10.15 - Catalina
- 11 - Big Sur
- 12 - Monterey
- 13 - Ventura
- 14 - Sonoma
- 15 - Sequoia
- 26 - Tahoe
Supported Operating Systems on ARM64 architecture for this version:
- MacOS
- 12 - Monterey
- 13 - Ventura
- 14 - Sonoma
- 15 - Sequoia
- 26 - Tahoe
- Linux
- Ubuntu 22.04 LTS
Note: ACC-M and ACC-L are supported only on server operating systems. ACC-F does not support Virtual Desktop Infrastructure (VDI) environments.
New:
Maintenance Token Protection for Windows Uninstalls
- Implement a maintenance token system that protects ACC (Agent Client Collector) agents from unauthorized or accidental uninstallation on Windows.
- Administrators must now generate and provide a unique, agent-specific token before allowing agent uninstallation, adding a critical security layer to large-scale deployments while maintaining offline functionality and audit trails.
ACC-F now provides official support for non-persistent Virtual Desktop Infrastructure (VDI) environments.
- Customers deploying agents to VDI gold images can now achieve full operational capability in under 2 minutes instead of 15–20 minutes with traditional instance push workflows.
- Prevented duplicate agent registrations on gold-image VM re-creation.
- Eliminated per-desktop TLS certificate generation for VDIs.
- Enabled immediate check execution upon instance connection
Changes:
- Randomized temporary directory creation during agent upgrade to prevent symlink attacks
- Restricted command allow-list defaults to prevent privilege escalation
- Optimized policy refresh to prevent memory exhaustion by processing agents in batches (2× max_agents_per_mid, 20,000 default) with automatic rotation
- Added post-upgrade sync hook to re-publish asset metadata to all active MIDs after ACC-F plugin upgrades
- Reordered Windows host IP selection to prioritize default-gateway interface query over generic routing
- Added explicit "check skipped" log entries to distinguish disabled checks from normal execution
- Extended policy publishing logic to support custom CI table inheritance (u_cmdb_ci_*)
- Implemented scheduled cleanup job for stale checks to auto-resolve associated error records
- Modified policy publish logic to update-in-place instead of delete/recreate
- Added detection and fix for corrupted agent_now_id files on ICS agent startup
- Added JSON5 support for allowlist parsing on ACC
- Updated WMI Permissions test to work on Windows 11 where wmic.exe was removed
Fixed:
- Fixed config file sync for checks with no assets by resolving "no agent record on context" error
- Fixed re-registration save file format for ICS agents
- Out-of-memory crashes on policy push when 80K+ agents accumulated on single MID.
- installed_software module hang on RHEL 10 when RPM output exceeds 64KB pipe buffer limit
- Asset metadata not re-synced after ACC-F plugin upgrade, breaking asset collection on MIDs
- Successful agent upgrade showing misleading "failed to fully fetch log" error message
- Windows multi-homed hosts registering with incorrect IP due to wrong interface selection
- ARM64 Linux CPU discovery failure when osquery CPU data unavailable
- Disabled checks logged as "running successfully," masking data collection outages with false health indicators
- Test Check UI crash/hang when agent table exceeds 28,000 records
- Agent crash on YAML parsing failures during initialization
- Policy deactivation success notification wiped by page auto-refresh
- Policy republish losing change history by deleting/recreating records instead of updating
- All agents for a particular ICS instance moving to "Unknown" state unable to transition to "down"
- "Clean up duplicate agent ID errors" job running indefinitely on large error volumes, consuming database resources
Not applicable for this application version.
- MID Server or ITOM Cloud Services (ICS) for sending data to the ServiceNow instance
- Configuration Management for Scoped Apps (CMDB)
3.1.0+ Plugin Signing:
- Currently, all Agent plugins are signed using the new ServiceNow certificate.
- For the agent plugins to be validated and synced to the agent host, the following requirements need to be met:
- Instance and MID Server: SanDiego+
- Agent installed on host: 2.7.0+
IPv6 Support:
- The agent can run on dual-stack (IPv4 + IPv6) or on IPv6-only systems.
- Use sn_agent.ci_prefers_ip_version to force IPv4 or IPv6 address for single attributes on dual-stack environments.
Other:
- CI Name coming from computername versus DNS hostname on Windows, using the following properties:
- glide.discovery.hostname.wmi_trusted
- glide.discovery.hostname.case
- If you manually added a custom Discovery Source, you may need to add the Agent Client Collector (and ACC-Visibility Content) sources manually.
- Ability to choose the type of required serial number [BIOS, Baseboard and others] to the computer CI serial_number attribute via the sys property sn_agent.ci_serial_number.pref_order.
- Selective Self-Upgrade: Not supported yet for CentOS Stream and macOS.
Agent Configuration File options: https://www.servicenow.com/docs/bundle/zurich-it-operations-management/page/product/agent-client-collector/reference/acc-yml-options.html
For reference, msiexec parameters:
- ACC_MID=string
- ACC_API_KEY=string
- ACC_ALLOW_LIST=True|False
- START_SERVICE=True|False
- LOCALUSERNAME=SYSTEM|LOCALSERVICE|domain\gMSA$|string
- LOCALUSERPASSWORD=string
- ISDOMAIN=0|1
- DOMAIN=string
- PASSWORD_NEVER_EXPIRES=True|False
See https://www.servicenow.com/docs/bundle/zurich-it-operations-management/page/product/agent-client-collector/task/acc-windows-install-silent.html for more details.