Combined MID Server release notes for upgrades from Vancouver to Xanadu

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 Vancouver to Xanadu.

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 Xanadu

Before you upgrade to Xanadu, review these pre- and post-upgrade tasks and complete the tasks as needed.


Release	Release notes
Vancouver	For the latest MID Server system requirements, see MID Server system requirements. 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 ensure 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. Only one Windows MID Server service is permitted per executable path. Upgraded Windows MID Servers that have multiple services pointing to the same installation folder cannot start. See MID Server fails to start for more information. For more information about MID Server upgrades, see the following topics: MID Server pre-upgrade check: Describes how the AutoUpgrade monitor tests the ability of the MID Server ability to upgrade on your system before the actual upgrade. Upgrade the MID Server manually: Describes how to upgrade your MID Servers manually.
Washington DC	For the latest MID Server system requirements, see MID Server system requirements. 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 ensure 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. Only one Windows MID Server service is permitted per 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 for more information. For more information about MID Server upgrades, see the following topics: MID Server pre-upgrade check: 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: Describes how to upgrade your MID Servers manually.
Xanadu	For the latest MID Server system requirements, see MID Server system requirements. 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. 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 for more information. For more information about MID Server upgrades, see the following topics: MID Server pre-upgrade check: 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: Describes how to upgrade your MID Servers manually.

New features

Between your current release family and Xanadu, new features were introduced for MID Server.


Release	Release notes
Vancouver	Cloud Discovery using Azure service principals You can set up an Azure service principal on the Discovery credentials [discovery_credentials] table. The discovery schedule can run with a MID Server in Azure to discover Linux and Windows virtual machines using that Azure service principal.
Washington DC	Containerized MID Server support for OpenShift Use OpenShift on Linux for containerized MID Servers. The corresponding Linux docker recipe has been updated. The containerized MID Server can run rootless by using existing auto-scaling capabilities with persistent storage.
Xanadu	MID Server support for Azure Key vault The MID Server integration with the Azure Key vault enables Orchestration, Discovery, and Service Mapping to run without storing any credentials on the instance.

Changes

Between your current release family and Xanadu, some changes were made to existing MID Server features.


Release	Release notes
Vancouver	Code Signing Certificate Validation on MID Server MID Server can insert Root CA Certification in the trust store and validate the code signing certificate before that certification can be used to validate signatures. Improved Caching of Credentials with External Credentials Vaults The MID Server caches credentials from external vault solutions and implements a thread-pool, which sets a maximum number of threads used when communicating with a CyberArk server. The MID Server resolves this asynchronously to avoid other concurrency issues.
Washington DC	MID Server Password2 global policy change Use the new "Reject" default behavior of the module access policies (MAPs) to help prevent any unauthorized access, unless explicitly declared in MAP records. All required MAPs for internal access are provided. Auto-generated MAPs are provided for external access. MID Server unique logged-in users Use unique logged in users for each MID Server. See (KB1552863) MID Server Unique Logged In User for more information. Improved wrapper configuration override Enable the debug logs at the dist-upgrade wrapper level and test the changes by modifying the configuration with upgrade-wrapper-override.conf. For example, the default timeout may not be long enough for certain JVM level commands. You can increase the timeout with upgrade-wrapper-override.conf for the dist-upgrade wrapper configuration.
Xanadu	MID Server log enhancement 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.

Removed

Between your current release family and Xanadu, some MID Server features or functionality were removed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.

Deprecations

Between your current release family and Xanadu, some MID Server features or functionality were deprecated.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	Containerized Windows MID Servers are no longer supported. The download link for the Windows MID Server docker recipe is removed. You can still use the old Windows MID Server docker recipe, but there’s no official support. See (KB1559617) Deprecated Containerized MID Server Features in Washington DC for more information. Auto-deployment and auto-deletion through a dedicated deployment MID Server are no longer supported. Deployment templates are no longer supported and new deployment templates can’t be used or created. However, existing deployment requests with existing templates still work. See (KB1559617) Deprecated Containerized MID Server Features in Washington DC for more information.
Xanadu	No updates for this release.

Activation information

Review information on how to activate MID Server.


Release	Release notes
Vancouver	MID Server is a ServiceNow AI Platform feature that is active by default.
Washington DC	MID Server is a ServiceNow AI Platform feature that is active by default.
Xanadu	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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.

Browser requirements

If any specific browser requirements were introduced or changed for MID Server we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.

Accessibility information

Review details on accessibility information for MID Server, such as specific requirements or compliance levels.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.

Localization information

If there are specific localization considerations for MID Server we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.

Highlight information

If there are specific highlight considerations for MID Server we have noted them here.


Release	Release notes
Vancouver	The MID Server pages and dashboard have been updated with the Next Experience. The MID Server caches credentials from external vault solutions and implements a thread-pool. The MID Server can insert Root CA Certification in the trust store and validate the code signing certificate before that certification can be used to validate signatures. See MID Server for more information.
Washington DC	Use OpenShift on Linux for containerized MID Servers. Prevent unauthorized access with the new "Reject" default behavior of the module access policies (MAPs). Enable the debug logs at the dist-upgrade wrapper level and test the changes by modifying the configuration with upgrade-wrapper-override.conf. See MID Server for more information.
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 for more information.