--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-xanadu-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ax bundleId : - delta3ax --- # Combined MID Server release notes for upgrades from Xanadu to Australia # Combined MID Server release notes for upgrades from Xanadu to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 12 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 Australia This consolidated guide provides ServiceNow customers with essential information about MID Server upgrades from the Xanadu release through to Australia. It summarizes system requirements, new features, changes, deprecated functionality, and upgrade considerations to help you effectively plan and execute MID Server upgrades across these versions. Show full answer Show less ## Important Upgrade Information * **JRE Requirements:** Each release sets a minimum Java Runtime Environment (JRE) version requirement increasing from 11.0.9 in Xanadu to 17.0.10 in Australia, with Australia recommending JRE 21.0.7. The upgrade process verifies JRE compatibility and issues warnings if unsupported versions are detected. MID Server installers automatically configure the bundled JRE where applicable. * **Service Restrictions:** Only one Windows MID Server service is permitted per executable path. Windows MID Servers with multiple services pointing to the same installation folder will fail to start after upgrade. * **Auto-Upgrade Access:** MID Server hosts must have access to install.service-now.com to enable auto-upgrades. * **Manual Upgrade Support:** Documentation is available for pre-upgrade checks and manual upgrade procedures to assist customers in controlled upgrade scenarios. ## New Features Across Releases * **Xanadu:** Integration with Azure Key Vault enables Orchestration, Discovery, and Service Mapping to operate without storing credentials on the instance, enhancing security. * **Yokohama:** Support for certificate-based authentication with Azure Key Vault via External Credential Storage and Management improves secure authentication methods. * **Zurich:** Introduction of the ITOM Infra Services Workspace consolidates MID Server activity monitoring with real-time dashboards, proactive alerts, and centralized diagnostics. * **Zurich:** The MID Guardian Agent uses AI to assist in diagnosing and resolving MID Server operational issues, improving reliability and reducing mean time to repair. * **Australia:** CyberArk integration now supports a REST-based Central Credential Provider (CCP) option alongside the existing AIM SDK, offering flexible credential management choices. * **Australia:** MID Server adds support for PowerShell 7 while maintaining backward compatibility with PowerShell 5.1, enhancing security and deployment efficiency. * **Australia:** Enhanced Smart Workload Manager in MID Server clusters assigns tasks based on multiple load metrics, ensuring balanced workload distribution and preventing server overload. ## Key Changes and Improvements * **Log Management:** MID Server supports log file compression and improved log backup capabilities. Logs are stored in compressed formats locally with options to fetch them to the instance, aiding in diagnostics and storage optimization. * **Java Version Enforcement:** Starting Yokohama, MID Server requires Java 17 or higher for execution, bundled with version 17.0.12 in Yokohama and upgraded to 21.0.7 in Australia. * **Installation Enhancements:** Installations on Windows now support running MID Server as LocalSystem or non-admin users with start/stop permissions, simplifying deployment and security management. * **Resource Requirements:** MID Server hosts must have at least 100MB of storage available to accommodate security logs. * **UI Theme:** Coral theme introduced as default for new portals and experiences, providing a modern look with brand-neutral illustrations and an available dark mode. ## Deprecations and Removals * **3DES Encryption:** Deprecated starting with Yokohama to improve security, removing support for 3DES in SSH connections for MID Server. * **No features were removed directly between Xanadu and Australia releases.** ## Activation and Additional Considerations * MID Server remains an active ServiceNow AI Platform feature by default across all releases. * No additional browser, localization, or accessibility requirements have been introduced or changed through these upgrades. ## Practical Impact for ServiceNow Customers Upgrading MID Server from Xanadu to Australia enhances security, performance, and manageability. Customers should ensure their MID Server hosts meet updated JRE and storage requirements, configure access to the ServiceNow download site for auto-upgrades, and verify that only one Windows MID Server service exists per installation to avoid startup failures. New integrations with Azure Key Vault and CyberArk improve credential security by minimizing stored secrets. PowerShell 7 support and smart workload management optimize discovery and job execution efficiency. The AI-driven MID Guardian Agent and ITOM Infra Services Workspace offer advanced monitoring and troubleshooting capabilities, reducing downtime and support effort. Overall, these upgrades provide a more secure, scalable, and resilient MID Server environment aligned with best practices for enterprise IT operations. Consolidated page of all release notes for MID Server from Xanadu to Australia. ## 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 Australia. 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 Australia Before you upgrade to Australia, 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. | | Australia | Upgrade information : For the latest MID Server system requirements, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=australia&ft:locale=en-US). The minimum JRE version supported is 17.0.10 and the recommended version is 21.0.7. 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=australia&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=australia&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=australia&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=australia&ft:locale=en-US): Describes how to upgrade your MID Servers manually. | [ ] ## New features Between your current release family and Australia, new features were introduced for MID Server. {#dfrn3-midserver-summary__entry__12} | 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. | | Australia | No updates for this release. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing MID Server features. {#dfrn3-midserver-summary__entry__22} | 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. | | Australia | [MID Server security logs require 100MB of storage](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=australia&ft:locale=en-US) : To store the security logs, MID Servers must be installed on a host with at least 100MB of storage capacity. [MID Server supports PowerShell 7 for Discovery](https://www.servicenow.com/docs/access?context=powershell-remoting&family=australia&ft:locale=en-US) : MID Server now supports PowerShell 7, while maintaining backward compatibility with PowerShell 5.1. This update enhances security, accelerates onboarding, and reduces deployment blockers through improved runtime detection and comprehensive test coverage. [Configure the MID Server for CyberArk CCP](https://www.servicenow.com/docs/access?context=t_ConfigureTheMIDServerForCyberArkCCP&family=australia&ft:locale=en-US) : MID Server's CyberArk integration adds a REST-based CCP option alongside the existing AIM SDK method, providing flexible, interchangeable integration choices. This additional option can reduce dependency overhead and enables you to choose between the AIM SDK and REST-based approaches according to your requirements. [Smart Workload Manager in clusters](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&family=australia&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. [MID Server is bundled with Java Runtime Environment 21](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&family=australia&ft:locale=en-US) : MID Server comes bundled with Java Runtime Environment version 21.0.7 and requires a minimum JRE version 17.0.10. The installer automatically configures Java 21.0.7 to run in your environment. If you have installed your own JRE, see the Important information for upgrading MID Server to Australia section to ensure your JRE is compatible. | [ ] ## Removed Between your current release family and Australia, some MID Server features or functionality were removed. {#dfrn3-midserver-summary__entry__32} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some MID Server features or functionality were deprecated. {#dfrn3-midserver-summary__entry__42} | 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. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate MID Server. {#dfrn3-midserver-summary__entry__52} | 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. | | Australia | 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__62} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__72} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__82} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__92} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__102} | 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. | | Australia | * MID Server comes bundled with Java Runtime Environment version 21.0.7 and requires a minimum JRE version 17.0.10. * MID Server's CyberArk integration adds a REST-based CCP option alongside the existing AIM SDK method, providing flexible, interchangeable integration choices. * MID Server smart workload manager continuously evaluates load and assigns jobs in a cluster to ensure that no server is overloaded. See [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&family=australia&ft:locale=en-US) for more information. | [ ]