Sub Production upgraded past the scheduled production version

[mrobins100]

Hello,

I have three sub-production environments: Development, Test and Test2.

Dev and Test2 were upgraded to Zurich in preparation for the end-of-support of Xanadu. Originally they were upgraded to Patch 4 Hot Fix 3; and that is the version to which my production instance is scheduled to be upgraded.

However, now both of those sub-production environments were upgraded to Zurich Patch 7.

Is there a way to prevent this in the future? I don't think I can test Patch 4 HF3 anymore because Patch 7 likely addresses at least one issue from Patch 4. This is the first upgrade on ServiceNow that I have worked on, but I have upgraded other ITSM products in the past; so any hints or help related to this would be very appreciated. 

[Tanushree Maiti]

Hi @mrobins100 

To avoid unexpected or unauthorized automatic upgrades in the future, take control of your upgrade schedules through the Now Support (HI) portal instead of depending on ServiceNow’s default timelines.

Although rolling back an instance to a previous patch after an upgrade is not straightforward, you can leverage system cloning to restore a sub-production instance so that it aligns with the current state of the production version.

If you need to reschedule, you can adjust the timing directly in the HI Portal’s change request based on your plan. It’s best to coordinate with your ServiceNow Account Executive, who can advise you on any potential impacts of the delay.

[mrobins100]

Thank you for the response Tanushree. I appreciate the help. 🙂