Prevent Users from Upgrading ArcGIS Pro

[MatthewStull1]

Hi Everyone, my question is:  Is there a way to prevent users from upgrading Pro on their own (like some sort of setting)?  Recently I had a few users who upgraded without telling the GIS staff and it caused some backwards compatibility issues.  Thank you for your time.

[David_McRitchie · Accepted solution]

Hey Matthew the following documentation discusses how updating can be disabled.

https://pro.arcgis.com/en/pro-app/latest/get-started/update-arcgis-pro.htm#:~:text=startup%20check%2...

Hope that helps,

David

[MarcelSt-Germain]

By the way, can we choose the update to be done.  Since Pro broke in each release some features, I had to reinstall it to the 3.0.1.  If I update it, I past to the last update available.

[D_McRitchie]

Hey Marcel,

This will only disable the ability to update. For selecting the specific update to be done a new install would be required.

On MyEsri you can select patches for the minor version number, so if you were looking to upgrade to 3.0.4 you could download ArcGIS Pro 3 patch 1. (Patch 1 as the default download for 3.0 starts at 3.0.3.

Many thanks,

David

[MarcelSt-Germain]

@D_McRitchie 

Yes but why not make it simple.  I can update directly to 3.2x but why not incremental update.  ESRI doesn't know the KISS philosophy 

[PaulLohr]

From the documentation in the link provided by @David_McRitchie :

Block all updates

You can block the ability to update ArcGIS Pro from within the application. This option is only available with administrator access.

To block all updates, browse to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Settings and set the value of CheckForUpdatesAtStartup to 0.

We can't go around and do this manually on every machine. So we have to go to our IT department and get them to push this change out to each machine that runs Pro. That's a hassle. This should be managed on the arcgis site.

[Ed_]

Go Vandals! 🙌

[RhettZufelt]

I second that.....

[MatthewStull1]

FYI, the new Date field type in 3.2 is not backwards compatible.  To put another way, if you create a feature class with the new date field type, users using 3.1 or older will not be able to use it.  I'm personally disappointed that ESRI has not emphasized this more.