--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined MID Server release notes for upgrades from Yokohama to Australia # Combined MID Server release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 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 Yokohama to Australia This consolidated guide covers essential release notes for upgrading ServiceNow MID Server from Yokohama through Zurich to Australia releases. It highlights key system requirements, new features, important changes, deprecations, and upgrade considerations to help you prepare and execute a smooth upgrade process. Show full answer Show less ## Key Upgrade Requirements and Considerations * **Java Runtime Environment (JRE):** The MID Server requires a minimum JRE version 17.0.10 for all releases from Yokohama onwards. Australia release bundles JRE version 21.0.7 and recommends upgrading to this version. If you use your own JRE installation, the upgrade process validates compatibility and issues warnings if unsupported versions are detected. * **Auto-Upgrade Access:** MID Server host machines must have internet access to *install.service-now.com* to enable auto-upgrades. * **Windows MID Server Services:** Only one Windows MID Server service per executable path is permitted. Multiple services pointing to the same installation folder will prevent the MID Server from starting after upgrade. * **Security Logs Storage:** Hosts must have at least 100MB of free storage to accommodate MID Server security logs starting from the Zurich release. ## New Features and Enhancements * **Yokohama:** Added certificate-based authentication support for Azure Key Vault in External Credential Storage, improving security and flexibility. * **Zurich:** Introduced the ITOM Infra Services Workspace for centralized MID Server activity monitoring and issue resolution, featuring real-time dashboards and automation. The MID Guardian Agent, an AI-powered assistant, helps diagnose and resolve MID Server issues proactively, reducing downtime. * **Australia:** * Support for PowerShell 7 alongside PowerShell 5.1 enhances security and simplifies onboarding. * CyberArk integration now includes a REST-based Credential Provider (CCP) in addition to the existing AIM SDK, offering flexible and interchangeable authentication methods. * The bundled Java Runtime Environment is updated to version 21.0.7, with continued support for minimum JRE 17.0.10. * Smart Workload Manager improvements ensure balanced job assignment in clusters by continuously evaluating load factors such as queue size, CPU usage, and execution time. ## Changes and Improvements * Mandatory use of JRE 17 or later starting from Yokohama; MID Server is compiled with Java 17 and incompatible with earlier versions. * Improved installation process on Windows allows installing MID Server as LocalSystem or non-admin user with Start/Stop permissions. * Enhanced MID Server logging includes compressed log backups stored locally with options to fetch logs to the instance, and support for Java Flight Recorder (JFR) logging with scheduled backups. * Smart Workload Manager's cluster job assignment is fine-tuned to prevent server overloads by monitoring multiple performance metrics. * Coral theme introduced as default for portals and mobile interfaces, providing a modern, brand-neutral look with a dark mode option. ## Deprecations and Removals * 3DES encryption was permanently removed starting with Yokohama release to enhance security. * No features were removed or deprecated in Zurich or Australia releases. ## Activation and Additional Information * The MID Server feature is active by default across all release families. * No additional browser requirements, localization, or accessibility changes were introduced through these releases. ## Practical Implications for ServiceNow Customers When upgrading your MID Server to Australia, ensure your host environment meets the updated JRE requirements and has adequate storage for security logs. Plan to leverage the new PowerShell 7 support and flexible CyberArk authentication methods to enhance security and operational efficiency. Utilize the ITOM Infra Services Workspace and MID Guardian Agent (from Zurich) to monitor MID Server health proactively and reduce downtime. Take advantage of the Smart Workload Manager enhancements to optimize job distribution within MID Server clusters, improving performance and reliability. Review and address the Windows MID Server service constraints to prevent startup issues after upgrade. Adopt the Coral theme for a refreshed user experience in portals and mobile applications. Consolidated page of all release notes for MID Server from Yokohama 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 Yokohama 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 | |-|-| | 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__10} | Release | Release notes | |-|-| | 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__18} | Release | Release notes | |-|-| | 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__26} | Release | Release notes | |-|-| | 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__34} | Release | Release notes | |-|-| | 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__42} | Release | Release notes | |-|-| | 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__50} | Release | Release notes | |-|-| | 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__58} | Release | Release notes | |-|-| | 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__66} | Release | Release notes | |-|-| | 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__74} | Release | Release notes | |-|-| | 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__82} | Release | Release notes | |-|-| | 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. | [ ]