Combined Agent Client Collector release notes for upgrades from Yokohama to Zurich

zurich Combined Product Files

Release

zurich

ft:locale

en-US

ft:publication_title

zurich Combined Product Files

ft:clusterId

delta3zy

bundleId

delta3zy

Combined Agent Client Collector release notes for upgrades from Yokohama to Zurich

Release version: Zurich

Updated July 20, 2026

9 minutes to read

Summarize

Summarized using AI

Summary of Combined Agent Client Collector Release Notes for Upgrades from Yokohama to Zurich

This consolidated release note page assists ServiceNow customers in preparing for their upgrade of Agent Client Collector (ACC) from the Yokohama release family to the Zurich release family. It compiles new features, changes, deprecations, and important upgrade information spanning multiple intermediate releases, focusing on practical enhancements and operational improvements.

Show full answer Show less

Key Features

Resource Monitoring and Efficiency Enhancements: Starting in Yokohama 3.13.0 and 3.6.5, ACC supports scanning resource directories for file attributes and offers MID-less installation to conserve MID Server resources.
Error Management: From version 4.3.0, customers can create tasks to address ACC-related errors, assigning responsible personnel for resolution.
High-Volume Upgrades: Introduced in versions 4.3.0 and expanded in 5.0 and 6.0.0, enabling efficient upgrades of large numbers of ACC agents, including macOS environments and MID-less agents.
Discovery Improvements: ACC now supports discovery of MSSQL components, Java files (including non-running files), and TLS/SSL certificates via the ACC for Visibility - Content module, aiding licensing and auditing.
Proxy and Network Configuration: Support for proxy servers during MID-less installation and proxy auto-configuration (PAC) files enhance deployment flexibility.
Enhanced Monitoring: Features include network host availability checks, Linux event monitoring, and improved metric collection with JSON configuration files.
Security and Certificate Management: ACC supports scheduled certificate rotation for secure communication and improved diagnostics for pre- and post-registration errors.
Platform Support and Usability: File-based discovery is supported on macOS, and Kubernetes Visibility Agent enhancements include storing instance credentials in Google Cloud Secret Manager and using custom certificate authorities.
CPU Protection Mode Enhancements: ACC can selectively disable only high-resource-consuming checks, maintaining overall data collection during CPU protection mode.
Debugging and Diagnostics: Enhanced debug logging sends all debug statements to a log file, improving troubleshooting capabilities.

Changes

Metric Explorer can display and monitor metric data independently of ACC Monitoring from version 4.1.0.
ACC for Visibility was renamed to Kubernetes Visibility Agent (KVA), with CNO for Visibility becoming a separate application since version 1.1.0.

Deprecations and Removals

Agent Client Collector Security Incident Response is no longer supported in Zurich. Customers should refer to the Now Support Knowledge Base for replacement guidance.
No features were removed in Yokohama or Zurich releases.

Activation and Requirements

ACC requires activation of the Agent Client Collector Framework plugin (snagent) and the Agent Client Collector Monitoring plugin (snitmon) on instances with Event Management installed.
No additional browser, localization, or accessibility requirements were introduced or changed during these releases.

Practical Impact for ServiceNow Customers

Upgrading to Zurich enhances your ability to efficiently manage ACC agents at scale, especially in MID-less environments and across multiple operating systems including macOS. New discovery capabilities improve visibility into software assets and certificates for better compliance and security management. Enhanced error handling, diagnostics, and CPU protection features enable more reliable and resource-conscious monitoring. Proxy support and Kubernetes integration improvements simplify deployment in modern cloud environments. Lastly, the deprecation of Security Incident Response means planning for alternative solutions is necessary.

Consolidated page of all release notes for Agent Client Collector from Yokohama to Zurich.

How to use this page

To help you prepare for your upgrade, we have combined the cross-family Agent Client Collector release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Zurich.

Tip:

If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

Important information for upgrading Agent Client Collector to Zurich

Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed.


Release	Release notes
Yokohama	No updates for this release.
Zurich	No updates for this release.

New features

Between your current release family and Zurich, new features were introduced for Agent Client Collector.


Release	Release notes
Yokohama	Scan your resource directories for file attributes Starting in version 3.13.0, run a check to receive information on the directory file's integrity, size, space, response time, and age. Conserve MID Server resources by using MID-less installation for Agent Client Collector Starting in version 3.6.5, conserve MID Server resources for more persistent features by using the MID-less installation when installing Agent Client Collector. With this installation, you don't need a MID Server in your system architecture. Create tasks to address Agent Client Collector errors Starting in version 4.3.0, create tasks to resolve errors relating to the Agent Client Collector. Tasks are assigned to personnel who investigate the underlying issues and work to resolve the errors. Use a proxy server with MID-less installation Starting in version 4.3.0, enable using a proxy server when installing Agent Client Collector without a MID Server. Discovery MSSQL server components Starting in version 1.3.0, enable discovery of MSSQL components by running Discovery as a local system user. Java certification Discovery through file-based discovery Starting in version 1.3.0, discover java file information using Agent Client Collector for Visibility - Content (ACC-VC) file based discovery. File based discovery locates java files that are installed on the system but not running, enabling retrieval of data used for licensing and auditing. Enable high volume upgrade of agents Starting in version 4.3.0, enhance efficiency by performing high-volume upgrade of large numbers of Agent Client Collector installations at once. Block event creation for non-existent entities Starting in version 3.13.0, block the creation of events and alerts if the process monitoring and log files don't exist in their indicated location. Control how check results are sent Starting in version 3.6.5, configure the circumstances when check results are sent. Configure and receive notifications of agent key expiration Starting in version 3.6.5, receive notifications that indicate when an agent registration key is expiring. Monitor network host availability Starting in version 4.1.0, use a new check to verify network host availability. Identify software running on Linux and Windows devices Starting in version 4.1.0, identify the software that is running on your Linux and Windows servers and devices by using file-based Discovery. File-based Discovery enables you to maintain the records of your software licenses and helps you to evaluate any threats from unwanted files. Store ServiceNow instance credentials in the Google Cloud Secret Manager when the Informer uses Google Kubernetes Engine (GKE) If your organization uses Google Kubernetes Engine (GKE) you can store the secret in Google Cloud Secret Manager. The Kubernetes Visibility Agent Informer can then pull the ServiceNow credentials for accessing your instance from the Google Cloud Secret Manager. Use a custom CA to enable the Informer to communicate with the ServiceNow instance when using a custom root CA Mount a custom certificate authority into the Kubernetes Visibility Agent Informer pod to enable the Informer to communicate with the instance when a custom root CA is used.
Zurich	Agent Client Collector Framework Upgrade MID-less agents Starting in version 6.0.0, perform selective and high-volume upgrades on ACC agents when not using a MID Server by using products such as DEX and ACC-VC. [Placeholder link text to key verify-agent-functionality] Starting in version 6.0.0, verify that an agent is functioning properly by performing a self-test on the agent. [Placeholder link text to key acc-workspace-dashboard] Starting in version 6.0.0, view a list of agents and their statuses on the ACC Workspace dashboard. Use improved debug logging Starting in version 6.0.0, benefit from enhanced debug logging by sending all debug statements to a log file Manage Agent Client Collector certificates Starting in version 5.0, configure a schedule by which to rotate Agent Client Collector certificates which enable communication between agents and ITOM Cloud Services. Rotating certificates ensures that when a certificate expires, a new certificate is in place. Perform high-volume Agent Client Collector upgrade in a macOS environment Starting in version 5.0, upgrade large numbers of Agent Client Collector agents at a time that are running on macOS. This extends the existing high-volume upgrade capabilities available for Windows and Linux in the 4.3.0 release. Use an IMDSv2 endpoint for metadata discovery Starting in version 5.0, the IMDSv2 endpoint for metadata discovery is invoked when using Agent Client Collector in an AWS EC2 environment. Use enhanced errors and diagnostics to troubleshoot issues with servers and endpoints Starting in version 5.0, view errors that occur before or after the registration process when Agent Client Collector connects to the instance. This provides enhanced debugging capabilities by enabling you to view issues in the instance, without requiring direct access to the agent logs. Disable checks using heavy system resources while in CPU protection mode Starting in version 5.0, disable only those checks that are causing high CPU usage while in CPU protection mode. It is still possible to disable all checks and completely stop data collection while in CPU protection mode. In a Windows environment, Agent Client Collector has improved the accuracy of how check CPU usage is monitored. Configuration data files size limit Starting in version 5.0, configuration data files have a maximum size of 10MB. Configure Agent Client Collector with proxy auto-configuration (PAC) files Starting in version 5.0, enable easier connection of Agent Client Collector to a proxy server by using a proxy auto-configuration (PAC) file. Agent Client Collector Monitoring [Placeholder link text to key gcp-config-file] Starting in version 3.15.0, GCP checks provide added support to configure metrics through a configuration file in JSON format. Monitor Linux events Starting in version 3.15.0, monitor Linux events using Linux event checks. Agent Client Collector for Visibility - Content Discover MSSQL components using ACC-VC Starting in version 1.5.0, use ACC-VC to discover MSSQL components in your environment. Discover software information with ACC-VC using SWID tags Starting in version 1.5.0, gather software information with ACC-VC using software identification (SWID) tags on an agent and a ServiceNow® instance. Run certificate Discovery using Agent Client Collector for Visibility - Content Starting in version 1.3.0, use the Agent Client Collector for Visibility - Content to discover TLS/SSL certificates used by the ports running on the server's configuration items (CIs). Certificate Inventory and Management uses the certificate data to manage the TLS/SSL certificate life cycle. File-based Discovery is supported in a macOS environment Starting in version 1.3.0, use File-based Discovery in a macOS environment. Collect metrics using non-osqueryd data collection Starting in version 1.3.0, collect data more efficiently by invoking non-osqueryd data collection.

Changes

Between your current release family and Zurich, some changes were made to existing Agent Client Collector features.


Release	Release notes
Yokohama	Explore metrics with Metric Explorer independent of Agent Client Collector Monitoring Starting in version 4.1.0, view and monitor metric data with Metric Explorer, even if you have not installed Agent Client Collector Monitoring. [Placeholder link text to key acc-visibility-landing-page] Starting in version 1.1.0, ACC for Visibility has been renamed as Kubernetes Visibility Agent and consists only of what is currently CNO for Visibility. The term CNO for Visibility has been deprecated and replaced with Kubernetes Visibility Agent. All other ACC for Visibility functions are now part of Agent Client Collector for Visibility - Content.
Zurich	No updates for this release.

Removed

Between your current release family and Zurich, some Agent Client Collector features or functionality were removed.


Release	Release notes
Yokohama	No updates for this release.
Zurich	No updates for this release.

Deprecations

Between your current release family and Zurich, some Agent Client Collector features or functionality were deprecated.


Release	Release notes
Yokohama	No updates for this release.
Zurich	Agent Client Collector Security Incident Response is no longer supported. For details on replacement options, see the Deprecation guidance for Agent Client Collector Security Incident Response [KB2249776] article in the Now Support Knowledge Base.

Activation information

Review information on how to activate Agent Client Collector.


Release	Release notes
Yokohama	Agent Client Collector is available with activation of the Agent Client Collector Framework plugin (sn_agent) and the Agent Client Collector Monitoring plugin (sn_itmon) in an instance on which Event Management is installed.
Zurich	Agent Client Collector is available with activation of the Agent Client Collector Framework plugin (sn_agent) and the Agent Client Collector Monitoring plugin (sn_itmon) in an instance on which Event Management is installed.

Additional requirements

If any additional requirements were introduced or changed for Agent Client Collector we have noted them here.


Release	Release notes
Yokohama	No updates for this release.
Zurich	No updates for this release.

Browser requirements

If any specific browser requirements were introduced or changed for Agent Client Collector we have noted them here.


Release	Release notes
Yokohama	No updates for this release.
Zurich	No updates for this release.

Accessibility information

Review details on accessibility information for Agent Client Collector, such as specific requirements or compliance levels.


Release	Release notes
Yokohama	No updates for this release.
Zurich	No updates for this release.

Localization information

If there are specific localization considerations for Agent Client Collector we have noted them here.


Release	Release notes
Yokohama	No updates for this release.
Zurich	No updates for this release.

Highlight information

If there are specific highlight considerations for Agent Client Collector we have noted them here.


Release	Release notes
Yokohama	Agent Client Collector for Visibility: Starting in version 1.1.0, ACC for Visibility has been renamed Agent Client Collector for Visibility - Content. CNO for Visibility has been extracted from Agent Client Collector for Visibility - Content and is now a separate application. Store instance credentials in the Google Cloud Secret Manager when the Kubernetes Visibility Agent Informer uses Google Kubernetes Engine (GKE). Use a custom CA to enable Kubernetes Visibility Agent Informer to communicate with the instance when using a custom root Certificate Authority (CA). Configure Agent Client Collector without a MID Server by ßusing MID-less configuration. See Agent Client Collector for more information.
Zurich	Discover TLS/SSL certificates using Agent Client Collector for Visibility - Content certificate Discovery. Enhance data collection by disabling only those checks with high resource usage, allowing data collection to continue for other checks. Improve troubleshooting capabilities by viewing errors that occur before and after the registration process in the ServiceNow instance. Use file-based Discovery in a macOS environment. See Agent Client Collector for more information.