--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-zurich-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3bz bundleId : - delta3bz --- # Combined MID Server release notes for upgrades from Zurich to Brazil # Combined MID Server release notes for upgrades from Zurich to Brazil {#ariaid-title1} Release version: Brazil Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 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 Brazil This consolidated guide provides essential information for ServiceNow customers upgrading their MID Server from Zurich through to Brazil releases. It highlights important pre- and post-upgrade considerations, new features, changes, and enhancements introduced across these releases to help you plan and execute your upgrade smoothly. Show full answer Show less ## Upgrade Preparation and Requirements * **JRE Requirements:** * Zurich to Australia: Minimum supported JRE version is 17.0.10; recommended versions are 17.0.12 for Zurich and 21.0.7 for Australia. * The MID Server installer auto-configures Java 21.0.7 in Australia release; if using a custom JRE, verify compatibility during upgrade. * **Auto-Upgrade Access:** MID Server hosts must have connectivity to *install.service-now.com* to enable automatic upgrades. * **Windows MID Server Services:** Only one Windows MID Server service per executable path is allowed; multiple services pointing to the same installation folder will prevent MID Server startup post-upgrade. * **Storage:** Hosts must have at least 100MB available to store security logs. * **Upgrade Guidance:** Documentation is available for pre-upgrade checks and manual upgrade procedures to ensure readiness and successful deployment. ## Key Features and Enhancements * **Zurich Release:** * **ITOM Infra Services Workspace:** Provides a unified dashboard for real-time MID Server monitoring, proactive alerts, automation, and centralized diagnostics to reduce downtime and support tickets. * **MID Guardian Agent:** An AI-driven assistant within the workspace that analyzes logs and operational data to offer guided troubleshooting, automated fixes, and predictive insights, improving MID Server reliability and reducing Mean Time to Repair (MTTR). * **Australia Release:** * **PowerShell 7 Support:** MID Server now supports PowerShell 7 for Discovery, enhancing security and deployment flexibility while maintaining backward compatibility with PowerShell 5.1. * **CyberArk Integration:** Adds a REST-based CyberArk Credential Provider (CCP) option alongside the existing AIM SDK integration, offering flexible choices to match your security requirements. * **Smart Workload Manager:** Continuously assesses cluster load based on queue size, execution time, CPU usage, and buffer size to assign jobs intelligently and prevent server overload. * **Bundled Java Runtime Environment:** MID Server includes Java Runtime Environment version 21.0.7 by default, simplifying environment setup. * **Brazil Release:** No new updates or features introduced for MID Server in this release. ## Improvements and Changes * **Logging Enhancements:** Improved MID Server logging includes compressed log backups stored locally with options to fetch logs to the ServiceNow instance, along with configurable Java Flight Recorder (JFR) logs for advanced diagnostics. * **Performance:** Enhanced MID Server performance under heavy discovery load by optimizing script include cache handling, especially when using many worker threads. * **User Experience:** Introduction of the Coral theme as the default for portals, web, and mobile interfaces, offering a modern, brand-neutral look with an optional dark mode. ## Activation and Additional Information * **Activation:** MID Server is an AI Platform feature active by default in Zurich and Australia releases. * **No Removed or Deprecated Features:** No MID Server features were removed or deprecated from Zurich through Brazil releases. * **No Changes in Browser, Accessibility, or Localization Requirements:** These areas remained consistent across releases. ## What to Expect After Upgrade By following the outlined upgrade recommendations and requirements, ServiceNow customers can expect a more stable, secure, and intelligent MID Server environment. The smart workload management and AI-driven diagnostics improve operational efficiency and reduce downtime. Integration enhancements support modern security practices, and improved logging facilitates troubleshooting. The Brazil release does not introduce additional changes, allowing for a stable baseline post-upgrade. Consolidated page of all release notes for MID Server from Zurich to Brazil. ## 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 Brazil. 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 Brazil Before you upgrade to Brazil, 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. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for MID Server. {#dfrn3-midserver-summary__entry__10} | 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. | | Brazil | No updates for this release. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing MID Server features. {#dfrn3-midserver-summary__entry__18} | 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. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some MID Server features or functionality were removed. {#dfrn3-midserver-summary__entry__26} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some MID Server features or functionality were deprecated. {#dfrn3-midserver-summary__entry__34} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Activation information Review information on how to activate MID Server. {#dfrn3-midserver-summary__entry__42} | 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. | | Brazil | No updates for this release. | [ ] ## 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 | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | | Brazil | 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 | |-|-| | 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. | | Brazil | No updates for this release. | [ ]