- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2022 07:02 PM
Is there a way to stop the automatic upgrade of MID Server?
Or is there a way to keep the MID Server from stopping if the automatic upgrade fails?
Solved! Go to Solution.
- Labels:
-
Upgrades and Patches
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2022 07:01 PM
Hi,
It is possible to stop MID server from auto-updating by setting mid.version.override property in the system property table (sys_properties) or by configuration parameter mid.pinned.version.
The configuration may be set in the config.xml file of the MID server or in a property setting.
In addition to mid.version.override, the MID Server version can also be controlled with the configuration parameter mid.pinned.version which pins the MID Server to a specific version.To pin a MID Servers, set the mid.pinned.version parameter with the name of that version in the config.xml file of each MID Server. Use the format <version>-mm-dd-yyyy. This setting overrides the property setting for the pinned MID Server version. For instructions, see Add a MID Server parameter. The value set in this parameter is not affected by an upgrade.
Warning:Using mid.version.override and mid.pinned.version is not recommended. The different versions on the MID Server and instance can cause outage issues on the MID Server.
If the reason to stop auto-upgrade is because MID server do not have Internet access, it's better to re-think the system architecture. It is recommended to place a MID server in the DMZ to allow Internet access.
Some of the MID server feature may not work properly if the version of the MID server and ServiceNow instance differs too much.
If the reason to not update the MID server is to continue using older features that are depreciated in the new version, it is probably better to switch over to the new feature because support of older feature may end.
For example, TLS1.1/1.0 will end. It is better to switch over to TLS1.2 rather than keep using TLS1.1/1.0 because TLS1.1/1.0 have security risks.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0746078
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2022 04:48 PM
Forgot to mention. It is also possible to install multiple MID Servers on a single system instead of using a virtualization. This approach will require only 1 MS Windows license. I personally haven't taken this approach because I'm using Ubuntu and it is easier to maintain OS on vm's. For example, I can just upgrade on 1 vm, copy the vm, change the setting instead of upgrading 2 instances. I can also take snapshots and revert if something goes wrong during the upgrade.
There is also an image of MID Server on a docker. Docker makes it easier to deploy instances but manual MID Server version up may be require creating a docker image. If there are many MID servers, docker may be a good solution but for a small setup, it may take more time to maintain.
