Mid server renames itself?

[jeffreyluto]

I have an On-premise ServiceNow instance.

And we have not really done anything much Mid servers yet.

But is it possible that if discovery is left on, that the system renames itself and the directory on the Windows server?

I have seen some strange behavior in QA and Prod like it's doing that?

For example if I named the MID server in QA: QA_MID_SERVER

Then I come back a week later and notice it changed the name of the mid server to the FQDN of the app server

with the port I connect on.

I'll attach an image to give a bit of context.

It also renames the second directory on the Windows server to something different also

like from c:\Windows\MID_Server\ServiceNow MID <insert appserver host>\agent

But the weird thing it that is seems to run fine?

 Why these renames?

[MadhanMaddy]

Hi @jeffreyluto ,

Please go through the below ServiceNow's official knowledge article. This explains your issue on why it might be happening.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748832
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1080390

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards,

Madhan

[jeffreyluto]

maybe it's related to this setting? "glide.discovery.hostname.always_update" I see it's marked True by default and we haven't changed it. 

[jeffreyluto]

I looked at QA and the location https://servicenow-instance/discovery_schedule_list.do?

shows not discovery scans are active?