MID Server Decommissioning

[rueben]

We have recently upgraded our Windows-based MID servers in all of our instances. We are now tasked with decommissioning the old MID servers so they can be removed from our environment. What is the proper way to remove these old MID servers from running these services? Any help would be appreciated, thanks.

[phsdm]

I don't know if this is the recommended practice, but what I do is:

1. Run the uninstall file in the agent directory.

2. Use the sc command to unregister the windows service.

3. Delete the MID server directory.

4. Delete the MID server record on the instance.

Don't ask me what sc command I use.   I can never remember...

[Steven Young]

When we recently changed, i made sure to keep the config file to keep the same Mid Server within ServiceNow.

If you change the mid server within ServiceNow   changes the Sys_id of the mid.     if you copied your config file over to your new physical server, and it's connected to your current SN Mid server,   it doesn't matter what you do with the old hardware.

[HugoFirst]

Here's my .02:

Step 1. Login to the server running the MIDServer service.   Stop the ServiceNow Discovery service ( or services if you have multiple services installed ). ( Logout when done )

Step 2. On your ServiceNow instance, in Discovery -> MID Servers, delete the corresponding entry, or entries, for the MIDServer.

Repeat Step 2 for any and all instances that have a mid server configured to talk to a service on the about to be decommissioned server. This means production and sub production instances.

Step 3.   Decomission your server.