--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-xanadu-zurich Release : - zurich ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zx bundleId : - delta3zx --- # Combined MID Server release notes for upgrades from Xanadu to Zurich # Combined MID Server release notes for upgrades from Xanadu 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 MID Server Release Notes for Upgrades from Xanadu to Zurich This consolidated release notes document provides ServiceNow customers with key information about MID Server upgrades from the Xanadu release through to the Zurich release. It covers system requirements, new features, changes, deprecations, and important operational considerations to help ensure smooth upgrades and optimal MID Server performance. Show full answer Show less ## Key Upgrade Requirements * **Java Runtime Environment (JRE):** * **Xanadu:** Minimum JRE 11.0.9 (recommended 11.0.16.1). * **Yokohama and Zurich:** Minimum JRE 17.0.10 (recommended 17.0.12). MID Server is compiled with Java 17 and requires this version or higher. * **Auto-Upgrade and Host Connectivity:** All MID Server hosts must have access to *install.service-now.com* to enable auto-upgrades. * **Windows Service Restrictions:** Only one Windows MID Server service per executable path is supported. Multiple services pointing to the same installation folder will prevent startup after upgrade. ## New Features Introduced Between Xanadu and Zurich * **Azure Key Vault Integration (Xanadu):** Enables orchestration, discovery, and service mapping without storing credentials on the instance, enhancing security. * **Certificate-Based Authentication for Azure Key Vault (Yokohama):** Adds support for certificate-based authentication, providing a more secure and flexible credential method. * **ITOM Infra Services Workspace (Zurich):** Offers a centralized dashboard for real-time MID Server activity monitoring, proactive alerting, automation, and diagnostics to reduce downtime. * **MID Guardian Agent (Zurich):** An AI-powered assistant within the workspace that analyzes logs and runtime data to guide troubleshooting, automate fixes, and predict issues, thereby reducing Mean Time to Repair (MTTR). ## Notable Changes and Improvements * **Log Management Enhancements:** * Introduction of log file compression configurable via MID Server properties (Xanadu). * Improved MID Server logging with compressed backups stored locally and optional retrieval to the instance (Zurich). * Java Flight Recorder (JFR) logs can be enabled for periodic capture with configurable backup retention (Zurich). * **Java 17 Requirement and Packaging (Yokohama):** MID Server requires JRE 17, bundled with 17.0.12, ensuring up-to-date runtime compatibility. * **Windows Installation Improvement (Yokohama):** MID Server can now be installed on Windows as a LocalSystem or non-admin user with start/stop permissions, simplifying deployment. * **Smart Workload Manager for Clusters (Zurich):** MID Servers in clusters now dynamically assign tasks based on real-time load metrics such as queue size, CPU usage, and execution time to prevent overloads and optimize resource use. * **Performance Enhancements:** Improved MID Server performance under heavy discovery workloads by reducing script cache misses during high concurrency (Zurich). * **User Experience Update:** Coral theme introduced as the default for portals and mobile with Next Experience or Core UI enabled, offering a modern, neutral design with dark mode options (Zurich). ## Deprecations and Removals * **3DES Encryption:** Deprecated starting from Yokohama release to enhance security; 3DES is permanently removed from MID Server's SSH connections. * **No features or functionality were removed in Zurich or prior releases.** ## Activation and Additional Notes * MID Server remains an active default feature of the ServiceNow AI Platform across all releases. * No additional browser, accessibility, or localization requirements have changed from Xanadu through Zurich. * Security logs storage now requires at least 100MB of available space on host machines (Zurich). ## Practical Implications for ServiceNow Customers Before upgrading MID Servers to Zurich, ensure compliance with JRE version requirements and confirm auto-upgrade connectivity. Leverage new security enhancements such as Azure Key Vault integration and certificate-based authentication to minimize credential risks. Utilize the ITOM Infra Services Workspace and MID Guardian Agent for proactive monitoring and maintenance to reduce downtime and support tickets. Take advantage of the smart workload manager to optimize cluster performance and prevent server overloading. Update logging configurations to benefit from compressed backups and JFR monitoring for better diagnostics. Finally, prepare Windows MID Servers for changes in service handling to avoid startup issues post-upgrade. Consolidated page of all release notes for MID Server from Xanadu to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family MID Server release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu 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 MID Server to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-midserver-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=xanadu&ft:locale=en-US). The minimum JRE version supported is 11.0.9 and the recommended version is 11.0.16.1. If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE: * If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version. * If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version. All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages [MID Server upgrades](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=xanadu&ft:locale=en-US). Only one Windows MID Server service is permitted according to executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can't start. See [MID Server fails to start](https://www.servicenow.com/docs/access?context=mid-startup-fails&family=xanadu&ft:locale=en-US) for more information. For more information about MID Server upgrades, see the following topics: * [MID Server pre-upgrade check](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=xanadu&ft:locale=en-US): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade. * [Upgrade the MID Server manually](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=xanadu&ft:locale=en-US): Describes how to upgrade your MID Servers manually. | | Yokohama | Upgrade information : For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=yokohama&ft:locale=en-US). The minimum JRE version supported is 17.0.10 and the recommended version is 17.0.12. If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE: * If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version. * If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version. All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages [MID Server upgrades](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=yokohama&ft:locale=en-US). Only one Windows MID Server service is permitted according to the executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can't start. See [MID Server fails to start](https://www.servicenow.com/docs/access?context=mid-startup-fails&family=yokohama&ft:locale=en-US) for more information. For more information about MID Server upgrades, see the following topics: * [MID Server pre-upgrade check](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=yokohama&ft:locale=en-US): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade. * [Upgrade the MID Server manually](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=yokohama&ft:locale=en-US): Describes how to upgrade your MID Servers manually. | | Zurich | Upgrade information : For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=zurich&ft:locale=en-US). The minimum JRE version supported is 17.0.10 and the recommended version is 17.0.12. If you have installed your own JRE, the upgrade process takes the following actions to verify that the MID Server uses a supported JRE: * If a MID Server is using an unsupported version of the JRE when it upgrades, the upgrade process displays a warning message with the minimum and recommended JRE version. * If a supported JRE is running on the MID Server host, the upgraded MID Server uses that version. All MID Server host machines require access to the download site at install.service-now.com to enable auto-upgrades. For additional details, read how the system manages [MID Server upgrades](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=zurich&ft:locale=en-US). Only one Windows MID Server service is permitted according to the executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder can't start. See [MID Server fails to start](https://www.servicenow.com/docs/access?context=mid-startup-fails&family=zurich&ft:locale=en-US) for more information. For more information about MID Server upgrades, see the following topics: * [MID Server pre-upgrade check](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=zurich&ft:locale=en-US): Describes how the AutoUpgrade monitor tests the ability of the MID Server to upgrade on your system before the actual upgrade. * [Upgrade the MID Server manually](https://www.servicenow.com/docs/access?context=c_UpgradeAndTestMIDServer&family=zurich&ft:locale=en-US): Describes how to upgrade your MID Servers manually. | [ ] ## New features Between your current release family and Zurich, new features were introduced for MID Server. {#dfrn3-midserver-summary__entry__10} | Release | Release notes | |-|-| | Xanadu | [MID Server support for Azure Key vault](https://www.servicenow.com/docs/access?context=mid-azure-key-vault-integration&family=xanadu&ft:locale=en-US) : The MID Server integration with the Azure Key vault enables Orchestration, Discovery, and Service Mapping to run without storing any credentials on the instance. | | Yokohama | [External Credential Storage and Management supports certificate-based authentication for Azure Key Vault](https://www.servicenow.com/docs/access?context=mid-azure-key-vault-integration&family=yokohama&ft:locale=en-US) : The External Credential Storage and Management added support for certificate-based authentication when connecting to Azure Key Vault. This provides a more secure and flexible way to authenticate, especially for enterprise environments that prefer certificate credentials over client secrets. | | Zurich | [ITOM Infra Services Workspace](https://www.servicenow.com/docs/access?context=itom-infra-srv-wrksp-mid&family=zurich&ft:locale=en-US) : The ITOM Infra Services Workspace provides a concise overview of MID Server activity. The dashboard integrates several previously disparate tables so that issues can be monitored and resolved. The workspace provides real-time monitoring, proactive alerts, automation of common tasks, and centralized diagnostics to reduce downtime and support tickets. [MID Guardian Agent](https://www.servicenow.com/docs/access?context=mid-guardian&family=zurich&ft:locale=en-US) : The MID Guardian Agent is an advanced AI feature within the MID Server ecosystem/ITOM Infra Services workspace, designed to proactively assist users in diagnosing and resolving issues related to configuration, connectivity, upgrades, and operations. By intelligently analyzing logs, signals, and runtime behaviors, it offers guided troubleshooting steps, automated fixes, and predictive insights. This significantly reduces Mean Time to Repair (MTTR) and enhances the reliability and operational efficiency of the MID server. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing MID Server features. {#dfrn3-midserver-summary__entry__18} | Release | Release notes | |-|-| | Xanadu | [MID Server log enhancement](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1637658) : MID Server supports log file compression. The new log file handler settings are available as MID Server properties on the instance. The compression mode is not enabled in the base system. | | Yokohama | [MID Server supports and requires a minimum JRE version 17](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=yokohama&ft:locale=en-US) : The MID Server is compiled using Java 17 and is incompatible with any Java version below 17 for runtime execution. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10. See the [MID Server JRE Minimum Version Requirement Update to JRE 17 Starting from Yokohama Release \[KB1704368\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704368) article in the Now Support Knowledge Base for information about required procedures before upgrading the instance. [Improvements when manually installing a MID Server on Windows](https://www.servicenow.com/docs/access?context=mid-server-install-prereqs&family=yokohama&ft:locale=en-US) : The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions. | | Zurich | [MID Server security logs require 100MB of storage](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=zurich&ft:locale=en-US) : To store the security logs, MID Servers must be installed on a host with at least 100MB of storage capacity. [Smart Workload Manager in clusters](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&family=zurich&ft:locale=en-US) : MID Servers in a cluster now assign jobs based on the true load, using a variety of criteria. The smart workload manager continuously evaluates the queue size, execution time, CPU usage, and buffer size. The manager then assigns tasks to ensure that no server is overloaded. [Enhancements to MID Server logging and JFR](https://www.servicenow.com/docs/access?context=r_MIDServerTroubleshooting&family=zurich&ft:locale=en-US) : MID Server logging has been improved with log backups that are preserved in a compressed format on local host with option to fetch to the instance. You can enable JFR logs every four hours and backup JFR files for a set time. [MID Server has improved performance during heavy discovery load](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=zurich&ft:locale=en-US) : MID Servers no longer have performance degradation due to script include cache misses when using large amounts of worker threads. Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. | [ ] ## Removed Between your current release family and Zurich, some MID Server features or functionality were removed. {#dfrn3-midserver-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Deprecations Between your current release family and Zurich, some MID Server features or functionality were deprecated. {#dfrn3-midserver-summary__entry__34} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | * When upgrading to the Yokohama release, 3DES will be permanently removed from MID Server to improve security. See [++3DES deprecation in SSH from Xanadu \[KB1644950\]++](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644950) for more information. | | Zurich | No updates for this release. | [ ] ## Activation information Review information on how to activate MID Server. {#dfrn3-midserver-summary__entry__42} | Release | Release notes | |-|-| | Xanadu | MID Server is a ServiceNow AI Platform feature that is active by default. | | Yokohama | Activation information : MID Server is a ServiceNow AI Platform feature that is active by default. | | Zurich | Activation information : MID Server is a ServiceNow AI Platform feature that is active by default. | [ ] ## Additional requirements If any additional requirements were introduced or changed for MID Server we have noted them here. {#dfrn3-midserver-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for MID Server we have noted them here. {#dfrn3-midserver-summary__entry__58} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for MID Server, such as specific requirements or compliance levels. {#dfrn3-midserver-summary__entry__66} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for MID Server we have noted them here. {#dfrn3-midserver-summary__entry__74} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for MID Server we have noted them here. {#dfrn3-midserver-summary__entry__82} | Release | Release notes | |-|-| | Xanadu | * Run other applications without storing any credentials on the instance with the Azure Key vault. * MID Server supports log file compression. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | * MID Server supports and requires a minimum JRE version 17. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10. * The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * MID Server smart workload manager continuously evaluates load and assigns jobs in a cluster to ensure that no server is overloaded. * MID Server logging has been improved with log backups that are preserved in a compressed format on a local host with an option to fetch to the instance. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=zurich&ft:locale=en-US) for more information. | [ ]