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

[SNowUser11]

We have all 4 MidServers connected to a single ServiceNow instance production. 

So if I create fix-scripts or back ground scripts, does it pushes to all MidServers. And don't we need in that case Windows admin credential to do that remotely.

I can understand there is no OOB solution but thinking any custom approach.

Many Thanks

[chadlockwood]

Just an idea, your script would setup whatever config changes you wanted to make, then iterate through your list of MID servers and apply those changes. If you are just making changes to the MID server, you would not need Windows admin credentials. However, if you are wanting to make changes to the Windows Server that the MID server is running on, you would need admin credentials and a fix script would not be able to make those changes. 

[Mike Farmer]

Chad, how did you find the offending script.  I am experiencing a similar issue.  WHen i toggle a script active / inactive, it forces a sync but the script updates that came in a recent patch are not syncing on their own.

[chadlockwood]

Mike,

I only wish I could remember back that far, and in hindsight, I definitely could have added more details when i found the problem. But from the way you worded your question, I'm wondering if you made any changes to the script you are trying to sync? If so, you own it and upgrades/patches will skip over it. If that were the case, you might be able to look at the Upgrade Monitor and see skipped records. In Orlando, there is a widget at the top that shows the number of skipped changes, in Paris there is a whole section that shows info about skipped. You might see if your script shows up there.

[Mike Farmer]

Thank you.  I was actually having an issue with a seeded script failing to update.  I finally figured out that if I delete the Scripts Folder on the Mid server and restarted the MID server, the folder would rebuild and properly populate.

Appreciate you jumping back in to help after 5 years.