--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-yokohama-zurich 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 # Combined Agent Client Collector release notes for upgrades from Yokohama to Zurich {#ariaid-title1} Release version: Zurich Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 9 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 Combined Agent Client Collector Release Notes for Upgrades from Yokohama to Zurich This consolidated release notes document guides ServiceNow customers through the upgrade path for Agent Client Collector (ACC) from Yokohama to Zurich releases. It highlights new features, changes, deprecations, activation details, and important upgrade considerations. The notes ensure that customers understand what has been introduced, changed, or removed to effectively plan and execute their ACC upgrades. Show full answer Show less ## Key Features Introduced Between Yokohama and Zurich * **Task Creation for Error Resolution:** Starting in version 4.3.0, ACC can create tasks to address errors, assigning them to personnel to investigate and resolve underlying issues. * **MID-less Installation Enhancements:** From version 3.6.5 and onward, ACC supports MID-less installation, conserving MID Server resources and allowing proxy server usage without a MID Server. * **High-Volume Agent Upgrades:** Versions 4.3.0 and 6.0.0 introduce capabilities to perform bulk upgrades of ACC agents, including selective upgrades for MID-less agents and support for macOS environments. * **Visibility and Discovery Improvements:** * Discovery of MSSQL components via ACC for Visibility Content (ACC-VC) starting version 1.3.0 and enhanced in 1.5.0. * File-based discovery for Java files and software inventory using SWID tags, including support for macOS. * Certificate discovery for TLS/SSL certificates with ACC-VC to assist certificate lifecycle management. * Monitoring Linux events and network host availability checks added in later versions. * **Security and Configuration Enhancements:** * Management and scheduled rotation of ACC certificates introduced in version 5.0 to ensure secure communication. * Support for storing ServiceNow instance credentials in Google Cloud Secret Manager when using Kubernetes Visibility Agent with Google Kubernetes Engine (GKE). * Ability to mount custom Certificate Authorities in Kubernetes Visibility Agent Informer pods for custom root CA support. * Proxy connection improvements via proxy auto-configuration (PAC) file support. * Enhanced debug logging and improved error visibility for troubleshooting connectivity and registration issues with the ServiceNow instance. * **Resource Optimization:** * Checks that heavily consume CPU can be selectively disabled during CPU protection mode, maintaining overall data collection. * Blocking event creation for non-existent entities to avoid unnecessary alerts. * Directory file attribute scanning added to monitor file integrity, size, and age. ## Changes and Deprecations * **Terminology Updates:** ACC for Visibility was renamed to Kubernetes Visibility Agent starting version 1.1.0, with other ACC for Visibility functions moved to Agent Client Collector for Visibility Content. * **Metric Exploration:** Metric Explorer can be used independently of ACC Monitoring from version 4.1.0. * **Deprecated Functionality:** Agent Client Collector Security Incident Response is no longer supported as of Zurich. Replacement guidance is available via ServiceNow Knowledge Base. ## Activation and Requirements * ACC activation requires enabling the Agent Client Collector Framework (snagent) and Agent Client Collector Monitoring (snitmon) plugins within an instance that has Event Management installed. * The product is available through the ServiceNow Store for installation. * No new browser, localization, or accessibility requirements have been introduced between Yokohama and Zurich. ## Upgrade Considerations and Practical Impact * Review pre- and post-upgrade tasks to ensure a smooth transition to Zurich. * Leverage MID-less installation enhancements to simplify architecture and conserve MID Server resources. * Utilize high-volume upgrade capabilities to efficiently manage large ACC deployments across Windows, Linux, and macOS environments. * Enhance software license management and threat evaluation through improved file-based discovery and SWID tag support. * Improve security posture by managing certificates and leveraging secure credential storage on cloud platforms like Google Cloud. * Benefit from improved troubleshooting options with enhanced logging and more detailed error diagnostics accessible from the ServiceNow instance. 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. {#dfrn3-agentclientcollector-summary__entry__2} | 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. {#dfrn3-agentclientcollector-summary__entry__8} | Release | Release notes | |-|-| | Yokohama | [Create tasks to address Agent Client Collector errors](https://www.servicenow.com/docs/access?context=create-error-task&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-yml-options&family=yokohama&ft:locale=en-US) : Starting in version 4.3.0, enable using a proxy server when installing Agent Client Collector without a MID Server. [Discovery MSSQL server components](https://www.servicenow.com/docs/access?context=using-enhanced-discovery-and-sam-together&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=using-enhanced-discovery-and-sam-together&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-high-volume-upgrade&family=yokohama&ft:locale=en-US) : Starting in version 4.3.0, enhance efficiency by performing high-volume upgrade of large numbers of Agent Client Collector installations at once. [Store ServiceNow instance credentials in the Google Cloud Secret Manager when the Informer uses Google Kubernetes Engine (GKE)](https://www.servicenow.com/docs/access?context=cnov-deploy-prepare&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=cnov-deploy-prepare&family=yokohama&ft:locale=en-US) : 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. [Scan your resource directories for file attributes](https://www.servicenow.com/docs/access?context=directory-scan-checks-policies&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-itom-cloud-services&family=yokohama&ft:locale=en-US) : 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. [Block event creation for non-existent entities](https://www.servicenow.com/docs/access?context=prevent-events-nonexistent-entities&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=create-edit-policies&family=yokohama&ft:locale=en-US) : Starting in version 3.6.5, configure the circumstances when check results are sent. [Configure and receive notifications of agent key expiration](https://www.servicenow.com/docs/access?context=agent-registration-key-configuration&family=yokohama&ft:locale=en-US) : Starting in version 3.6.5, receive notifications that indicate when an agent registration key is expiring. [Monitor network host availability](https://www.servicenow.com/docs/access?context=network-host-availability-check&family=yokohama&ft:locale=en-US) : Starting in version 4.1.0, use a new check to verify network host availability. [Identify software running on Linux and Windows devices](https://www.servicenow.com/docs/access?context=acc-visibility-checks-policies&family=yokohama&ft:locale=en-US) : 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. | | Zurich | [Upgrade MID-less agents](https://www.servicenow.com/docs/access?context=upgrade-agent-from-instance&family=zurich&ft:locale=en-US) : 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\]](https://www.servicenow.com/docs/access?context=verify-agent-functionality&family=zurich&ft:locale=en-US) : 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\]](https://www.servicenow.com/docs/access?context=acc-workspace-dashboard&family=zurich&ft:locale=en-US) : Starting in version 6.0.0, view a list of agents and their statuses on the ACC Workspace dashboard. [Monitor Linux events](https://www.servicenow.com/docs/access?context=linux-checks-policies&family=zurich&ft:locale=en-US) : Starting in version 3.15.0, monitor Linux events using Linux event checks. [Discover MSSQL components using ACC-VC](https://www.servicenow.com/docs/access?context=exploring-accv&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=exploring-accv&family=zurich&ft:locale=en-US) : Starting in version 1.5.0, gather software information with ACC-VC using software identification (SWID) tags on an agent and a ServiceNow® instance. [Use improved debug logging](https://www.servicenow.com/docs/access?context=acc-configure-log-levels&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-yml-options&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-high-volume-upgrade&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-configure-websocket-endpoint&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=view-agent-errors&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=checks-policies&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=acc-config-data-files&family=zurich&ft:locale=en-US) : Starting in version 5.0, configuration data files have a maximum size of 10MB. [Configure Agent Client Collector with proxy auto-configuration (PAC) files](https://www.servicenow.com/docs/access?context=proxy-agent&family=zurich&ft:locale=en-US) : Starting in version 5.0, enable easier connection of Agent Client Collector to a proxy server by using a proxy auto-configuration (PAC) file. [\[Placeholder link text to key gcp-config-file\]](https://www.servicenow.com/docs/access?context=gcp-config-file&family=zurich&ft:locale=en-US) : Starting in version 3.15.0, GCP checks provide added support to configure metrics through a configuration file in JSON format. [Run certificate Discovery using Agent Client Collector for Visibility Content](https://www.servicenow.com/docs/access?context=run-cert-discovery-accvc&family=zurich&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=file-based-discovery&family=zurich&ft:locale=en-US) : Starting in version 1.3.0, use File-based Discovery in a macOS environment. [Collect metrics using non-osqueryd data collection](https://www.servicenow.com/docs/access?context=using-enhanced-discovery-and-sam-together&family=zurich&ft:locale=en-US) : 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. {#dfrn3-agentclientcollector-summary__entry__14} | Release | Release notes | |-|-| | Yokohama | [\[Placeholder link text to key acc-visibility-landing-page\]](https://www.servicenow.com/docs/access?context=acc-visibility-landing-page&family=yokohama&ft:locale=en-US) : 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. [Explore metrics with Metric Explorer independent of Agent Client Collector Monitoring](https://www.servicenow.com/docs/access?context=agent-workspace-ops-intelligence&family=yokohama&ft:locale=en-US) : Starting in version 4.1.0, view and monitor metric data with Metric Explorer, even if you have not installed Agent Client Collector Monitoring. | | Zurich | No updates for this release. | [ ] ## Removed Between your current release family and Zurich, some Agent Client Collector features or functionality were removed. {#dfrn3-agentclientcollector-summary__entry__20} | 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. {#dfrn3-agentclientcollector-summary__entry__26} | 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](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2249776) in the Now Support Knowledge Base. | [ ] ## Activation information Review information on how to activate Agent Client Collector. {#dfrn3-agentclientcollector-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | Activation information : 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. Important: Agent Client Collector is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : 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. Important: Agent Client Collector is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Agent Client Collector we have noted them here. {#dfrn3-agentclientcollector-summary__entry__38} | 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. {#dfrn3-agentclientcollector-summary__entry__44} | 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. {#dfrn3-agentclientcollector-summary__entry__50} | 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. {#dfrn3-agentclientcollector-summary__entry__56} | 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. {#dfrn3-agentclientcollector-summary__entry__62} | 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](https://www.servicenow.com/docs/access?context=acc-landing-page&family=yokohama&ft:locale=en-US) 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](https://www.servicenow.com/docs/access?context=acc-landing-page&family=zurich&ft:locale=en-US) for more information. | [ ]