MID server best practices - multiple environments

[seberly]

I have three ServiceNow environments, and I am wondering if the best practice (/what does everyone do?) is to have MID servers specific to each environment or MID servers that serve all environments - development, QA, and production.

Right now we have separate MID servers for development, QA, and production, and it seems like unnecessary bloat to manage since we have Disco schedules deactivated in sub-prods and only activate when testing is needed.

Thoughts?

Thanks in advance,

Scott

[Deepak Kumar5]

Mid-server set up for a specific instance, You can user same server for all instance but have configure mid-server for each instance.

If you are not using too much then install one to TEST(Testing your changes) and one for Prod

[bernyalvarado]

Hi Scott,

It depends on your current needs and also what you'll need on the future. These days is not that costly or hard to manage 3 o 4 virtual servers to host your MID Servers. Ideally the servers will be different per environment, but it's also true you can host all the MID Servers within 1 server. I personally do not recommend that since development changes can be very loose, versus those from a testing and/or qa instance which should be more controlled.

Just my two cents. I hope this helps.

Thanks,

Berny

[ismailkiswani]

Hi Scott,

Based on my experience with MID Server integration with SCOM, Discovery, AD Synchronization. it depends on the Scenario but the best scenario for multiple MID Servers is when you have data centers or offices in multiple regions and you wanted to avoid traffic consumption.

if you have domain separation between your environments, so the best practice is to go with multiple MID Servers.

if domain separation is not   enabled go with one MID Server to discover all environment and create schedule for each one.

this is my advice and hope it would be helpful.

Regards,

Ismail Al-Kiswani