0
5.0.0
Zurich, Yokohama, Xanadu, Washington DC, Vancouver
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 agent for ServiceNow and is the key enabler for the following use cases:
- Visibility and Monitoring
- Hardware and Software Asset Management
- Security Incident Response
- 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, 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 - RHEL and Oracle Linux - OL 7, 8, 9
- 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 and 11
- Amazon Linux 2 AMIs
- Microsoft Windows
- Windows Server 2012, 2012r2, 2016, 2019, 2022
- 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
Supported Operating Systems on ARM64 architecture for this version:
- MacOS
- 12 - Monterey
- 13 - Ventura
- 14 - Sonoma
- 15 - Sequoia
Note: ACC-M and ACC-L are supported only on Server operating systems.
- New:
- Agent Proxy and PAC File support
- Agent registration improvements - Mid-less only
- Agent logs errors on both pre and post registration failures
- Deleting an agent will delete its registration key
- Shell agent is created during a registration failure to give visibility into failures from the instance
- Agent can now move between instances using command line execution
- Now supports macOS selective/auto upgrade
- Duplicate Agent ID duplication detection and remediation [agents connected through mid server only]
- Fixed:
- Openssl upgrade to v3.4.1
- upgrade net-imap 0.4.9.1
- Issues with deterministic agent ID generation
- Check execution on Windows agent does not accurately report CPU usage
- OS domain primary source is WMI
- Agent does not respect glide.discovery.hostname.include_domain property to populate "host_name" field
- Policy hierarchy: imported parent policies do not sync down changes to child when published
- Policy Domain Separation: When policy gets copied from parent to child domain, credentials should not get copied down
- Mid-less: Agent Registration: Update the logic to get the current active ipki cert issuing rather than just the latest
- MID Server
- Configuration Management for Scoped Apps (CMDB)