MID server Script File sync issue

[chadlockwood]

I am creating MID Server script files for all of my PowerShell activities because they are supposed to automatically sync between all MID servers. I create the script file in the Dev instance, in an update set, and it is automatically synced to all my MID servers. However, when I push the update set to the test environment, the script file is not synced automatically. I thought at one time restarting the MID servers after pushing the update set caused the automatic sync, but that doesn't appear to be the case. I now have to set the script file to inactive, save, set to active, save to get the sync to happen.

Does anyone know if this sync is supposed to be automatic based on updates in an update set? If so, how often does it happen and what triggers it? If not, what would be the best way to cause this sync to happen?

Regards,

Chad

[chadlockwood]

The sync should happen automatically. On your MID server you should see your script files in the standard location: C:\ServiceNow\Development\agent\scripts

I just created a new script file and it synced to the MID server almost instantly. 

[SNowUser11]

So if i understood correctly ..

we have 4 windows midservers as standalone . So how can changes to any one of the midserver will be synced to other three? Sorry if you can explain more will be helpful.

Can we have any script (any OOB solution) in place to have this syncing.

OR is it Mid Server Script includes in instance does this. Please guide not sure.

Many Thanks

[chadlockwood]

What kind of changes are you trying to sync? Just MID server script files, MID server settings, Windows Server settings or other?

Are all 4 MID servers connected to the same instance? Or do you have Production and lower environments?

[SNowUser11]

Say for example any type: enabling shazam probe or disabling weak ciphers, orchestration etc...I mean whatever changes I make in one midserver config it should be applicable to all other so that I dont have to do it manually for each one of them

[chadlockwood]

That hasn't been our experience. We manually make changes to our MIDs. However, we only have one for our lower environments and two for our Production, so it hasn't ever been an issue of effort.

I suspect, with a little effort, you would be able to script updates like that for all of the MID servers connected to one instance, maybe using a fix script. If you want/need your lower environments to be different to your production, remember to create data preservers so that your clones don't change those settings.