Creating New Server to host current MID Server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2023 05:44 AM
So we are going to be building a new host server to upgrade to the latest OS and we need to migrate/move a MID Server from the current 2012 Server to the new host server.
I have been reviewing the current KB article and it seems pretty straight forward:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0623688
The only questions I have that doesn't seem to be mentioned here (except in the FAQ, but no real info given) is does the new host server need to have the same name as the old host server. So if our current host server is SERVICENOWMID001 does the new host server need to be SERVICENOWMID001 also?
I know the MID Server name itself would need to be identical to the current one, but what about the actual host server name? The reason I ask is in our instance when looking at a MID Server record there is a "Host Name" field and it's read only. Well if it's pointing to one host server and we build a new host server with a different name I wasn't sure how that MID Server would know to connect (unless the config files drive that host name).
Anybody have any insight here?
Please mark this response as correct and/or helpful if it assisted you with your question.
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2023 11:45 AM
According to the ServiceNow KB article you referenced, there is no mention of the new host server needing to have the same name as the old host server. Typically, the MID Server configuration files drive the host name that the MID Server uses to connect to the ServiceNow instance, so as long as the new host server has the same configuration settings as the old host server, the MID Server should be able to connect without issue.
However, if the "Host Name" field in your MID Server record is read-only and points to the old host server, you may need to update this field with the new host server name after the migration is complete. This can typically be done by editing the MID Server record in the ServiceNow instance.
It's also worth noting that if the new host server has a different IP address or network configuration than the old host server, you may need to update firewall rules or network settings to ensure that the MID Server can communicate with the ServiceNow instance properly.
If you have any further concerns, it may be worth reaching out to ServiceNow support for additional guidance specific to your environment.
Please mark my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2023 12:31 PM
Hi @Syedmd08 In my case this is going to be a change in IP address as communicated from the migration team
Do you have the set of firewall rules or network settings that can be listed and notified to migration team to take care?
Is there a related KB or doc to follow this approach wherein IP is gonna change?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2023 12:24 PM
Our team also came up with the same upgrade plan wherein they are planning to migrate the current server and it's apps to new host(Maybe on cloud VM) and it seems the IP configuration would change
I want to understand if there is any best way to get through this without complication?
In terms of firewall rules or network settings what exactly are these settings that we can mention to the migration team to take care in case if they can relate?
Any related details would help
Thanks a lot