How to Rename a MID Server on the ServiceNow Instance - Support and Troubleshooting

How to Rename a MID Server on the ServiceNow Instance Issue .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article explains how to rename an existing MID Server so the new name is reflected on the ServiceNow instance. A common scenario is when a MID Server has been migrated to a new host and the administrator wants the MID Server name on the instance to match the new hostname.

Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } No release specific

Cause .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When a MID Server starts, it connects to the ServiceNow instance and synchronizes its configuration with the existing MID Server record. The instance-side record is the source of truth. If only the local config.xml is updated with a new name but the instance record still contains the old name, the instance will overwrite the config.xml value on startup, reverting the name change.

This behavior is by design — it is the MID Server's self-healing mechanism to ensure consistency between the local installation and the instance record.

Resolution .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Steps:

Stop the MID Server service. On the MID Server host, open Windows Services (services.msc) or the equivalent service manager, locate the ServiceNow MID Server service, and stop it. Update the MID Server record on the instance. Log into the ServiceNow instance and navigate to MID Server > Servers . Open the MID Server record that currently has the old name. Change the Name field to the desired new name and click Update. Note the Sys ID of this record (visible in the URL bar or by adding sys_id to the form). Edit the config.xml on the MID Server host. Open the config.xml file in the MID Server agent directory and update the following parameters: Parameter Action Example name Set to the new MID Server name (must match the Name field updated in Step 2) mid_sys_id Verify it matches the Sys ID from Step 2. Only change if it does not match. Important: Do not change the mid_sys_id unless it does not match the Sys ID on the instance record. If it already matches, leave it as-is.

Save the config.xml file and close the editor. Start the MID Server service. Return to Windows Services (or the equivalent) and start the ServiceNow MID Server service. Validate the MID Server. On the instance, open the MID Server record and click Invalidate. Once invalidated, a Validate button will appear — click it to complete re-validation. Resolve any MID Server issues. If a "home directory changed" issue appears in the MID Server Issues list, manually set its State to Resolved. This alert is expected when the installation path reflects the new hostname and is safe to clear (see KB0743043). Verification After completing the steps above, confirm all of the following:

The MID Server record on the instance displays the new name The MID Server status shows "Up" and "Validated" The config.xml name parameter retains the new value after a service restart (no revert) No active MID Server issues remain Existing scheduled jobs, discovery schedules, and integrations continue to execute on the renamed MID Server