when utah version will no longer be supported

[yrozo]

when is the deadline to upgrade servicenow from the utah version?

[Dr Atul G- LNG]

Hi @yrozo 

SN support N-1 version as per the latest update, but you can support it ( it can be more expensive) and for the same best to reach out to your SN Account team.

[Mark Roethof]

"SN support N-1 version"

Not for every customer, depends on the contract 🙂

[Mark Roethof]

Hi there,

I don't know the exact date, though from previous experiences when you where 2 releases behind and the new release already out (like now with Tokyo versus Washington), ServiceNow would automatically created changes for your (forced) upgrade (you could still request to have that changed).

If that is applicable to you, I don't know, I don't know your contract also.

The N-1 or N-2 like Atul mentions: that can differ per customer contract!!! So its not a generic rule that ServiceNow only support N-1. That's NOT true. ServiceNow even covered that in a recent live webinar.

I don't know if that is still how it works with the forced upgrade when 2 releases behind and a new release out, though last time I experienced this was about 1,5 year ago.

[Paige Duffey]

These two KB articles should give you all the information you need for End-of-Life Upgrades and the Version policy. I won't rehash anything else that's already been mentioned, but I will add that the instance Admins (as listed in the Support site) will receive notification that their instances are being upgraded at X date and a change request will be submitted for the upgrade(s). You can also reschedule the upgrades if the set date/time does not work for your company.

KB0610454 - End-of-Life unsupported release family upgrades FAQ

KB0783520 - ServiceNow Upgrade and Update Policy Explained