--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined MID Server release notes for upgrades from Zurich to Australia # Combined MID Server release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 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 Zurich to Australia This consolidated release notes document helps ServiceNow customers prepare for MID Server upgrades from the Zurich release family through to Australia. It covers essential upgrade information, new features, changes, and important technical requirements across these releases to ensure smooth transitions and optimal MID Server performance. Show full answer Show less ## Important Upgrade Information * **JRE Requirements:** The minimum supported Java Runtime Environment (JRE) version is 17.0.10 for both Zurich and Australia, with Australia recommending JRE 21.0.7. The MID Server installer automatically configures Java 21.0.7 in Australia, but if you use a custom JRE, ensure it meets these requirements to avoid upgrade warnings or failures. * **Auto-Upgrade Access:** MID Server host machines must have access to the ServiceNow download site (install.service-now.com) to enable auto-upgrades. * **Windows MID Server Limitations:** Only one Windows MID Server service is permitted per executable path. Multiple services pointing to the same installation folder will prevent the MID Server from starting after the upgrade. * **Pre-Upgrade Checks and Manual Upgrades:** Use the MID Server pre-upgrade check to confirm upgrade readiness and follow documented manual upgrade procedures if needed. * **Storage Requirements:** Hosts must allocate at least 100MB of storage for MID Server security logs starting from Zurich. ## New Features * **ITOM Infra Services Workspace (Zurich):** Provides a unified dashboard for real-time MID Server activity monitoring, proactive alerts, automation, and centralized diagnostics to reduce downtime and support tickets. * **MID Guardian Agent (Zurich):** An AI-powered assistant embedded within the MID Server ecosystem that proactively diagnoses configuration, connectivity, and operational issues, offering guided troubleshooting, automated fixes, and predictive insights to reduce Mean Time to Repair (MTTR). * **PowerShell 7 Support (Australia):** Enhances MID Server Discovery by supporting PowerShell 7 alongside PowerShell 5.1, improving security, onboarding speed, and reducing deployment blockers. * **CyberArk CCP REST Integration (Australia):** Adds a REST-based CyberArk Credential Provider (CCP) option alongside the existing AIM SDK, providing flexible integration methods to fit your security requirements. * **Bundled Java Runtime (Australia):** MID Server now includes Java Runtime Environment version 21.0.7, simplifying configuration and ensuring compatibility with the latest supported Java version. ## Key Changes * **Smart Workload Manager Improvements:** Clustered MID Servers now assign jobs based on a comprehensive evaluation of queue size, execution time, CPU usage, and buffer size to avoid overloading any server. * **Enhanced Logging and JFR Support:** MID Server logging now includes compressed log backups stored locally with options to fetch logs to the instance. Java Flight Recorder (JFR) logs can be enabled every four hours with configurable backup retention. * **Improved Discovery Performance:** Performance issues related to script include cache misses under heavy discovery loads have been resolved, especially when using many worker threads. * **UI Theme Update:** The Coral theme is now the default for portals, web, and mobile experiences using Next Experience or Core UI, offering a modern, brand-neutral look with a dark theme option. ## Removals and Deprecations No MID Server features or functionalities were removed or deprecated between Zurich and Australia. ## Activation and Additional Requirements * MID Server continues to be an active ServiceNow AI Platform feature by default across releases. * There are no new additional system requirements, browser requirements, accessibility, or localization changes introduced in this upgrade path. ## What ServiceNow Customers Can Expect By following the outlined upgrade procedures and ensuring adherence to system requirements, customers will benefit from enhanced MID Server reliability, smarter workload distribution, improved diagnostics, and modernized UI experiences. The introduction of AI-driven issue resolution and expanded integration options strengthens operational efficiency and security. The bundled Java update simplifies maintenance and compatibility management. Consolidated page of all release notes for MID Server from Zurich 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 Zurich 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 | |-|-| | 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__8} | Release | Release notes | |-|-| | 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__14} | Release | Release notes | |-|-| | 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__20} | Release | Release notes | |-|-| | 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__26} | Release | Release notes | |-|-| | 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__32} | Release | Release notes | |-|-| | 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__38} | Release | Release notes | |-|-| | 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__44} | Release | Release notes | |-|-| | 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__50} | Release | Release notes | |-|-| | 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__56} | Release | Release notes | |-|-| | 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__62} | Release | Release notes | |-|-| | 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. | [ ]