MID server temporarirly disable

[mah1]

Vancouver Patch 5

We are planning to replace the SCCM plugin with the ServiceGraph Connector for SCCM in our sub-prod instance. We currently do not have a MID server set up for our sub-prod instance. I requested that another MID server be set up to use with the sub-prod instance but instead have been instructed to use the MID server for our production instance for this work.

Any issues with this approach?  Can I temporarily disable/deactivate the MID server on our production instance until everything has been completed/verified with the ServiceGraph Connector for SCCM on our sub-prod instance? Do I simply pause the Mid server on the production instance or is this more involved?  I read that a MID server is limited to a single instance so I suspect that the instance url used by the current MID server needs to be changed to the url of the sub-prod instance then changed back when the work has been completed.  Is this correct or is it more complicated that than?

Any guidance would be greatly appreciated.

Thank you

[The Machine]

Basically you need to "install" the MID server package again, the same way you did it the first time.  As you go through the setup when it asks for a service name, give it something other than the default like "ServiceNow TEST MID Server"  So you can tell which service is for which instance.

And thats pretty much it.

[mah1]

This is all new to me so apologies for the additional questions. I'm just trying to make sure I understand this correctly.

When you say I need to "install" the MID server package again, do you mean on the host server? so, on the host server, there will be, for example, SN Prod MID Server and SN Dev MID Server. SN Prod MID Server will be used for the production instance and SN Dev MID Server will be used for the dev (or sub-prod) instance.

if so, that really isn't what I've been asked to do.  They want me to temporarily turn off SN Prod MID Server in the production instance and switch that to the dev instance.  They don't want to set up another MID Server service on the host server to use with the dev instance.

Thank you

[The Machine]

Whats their reasoning for you to do it "this" way?  You might be pitted into what they are asking and what actually needs to be done.

It seems a bit backwards.  I'd think you'd want to leave your production services running until the cut over.  I'd say install the separate dev service as I mentioned previously.  Then you can disable the service for production and leave the dev one running if thats what you/they want.

[mah1]

The reasoning is that I do not have access to the Windows host server and therefore am not able to set up another MID server service to use with our Dev instance and the folks with access do not have any time to do so.  But they want me to work on replacing the SCCM plugin with the ServiceGraph Connector for SCCM on our Dev instance and temporarily use the only MID server service that is currently available until everything is working/verified in Dev. Then switch the MID server service back to production and continue on until the plugin is replaced in production.

Thank you

[The Machine · Accepted solution]

I had a feeling there was something non technical around this. 

In my opinion, MID Servers usually take minutes to setup.  You probably spend more time downloading the MID package than actual configuration.  So "not having time" is not something I accept personally.  Theres a difference between doing it the right way and wrong way.  This sounds wrong to me.  

Also, if you don't have access to the MID, they need to make this change.  So either way they need to do something.

So as long as the credentials match in PROD and DEV, in theory changing the instance URL and restarting the service should do it.

Good luck.