topic Updating ArcGIS Pro in a Different Way? in ArcGIS Pro Questions

Updating ArcGIS Pro in a Different Way?

JoeFlannery — Tue, 11 Feb 2020 21:37:40 GMT

Over the past two calendar years (2018 & 2019), ArcGIS Pro has been updated five and eight times per year, respectively. Our company has disabled automatic updates (“Checking for updates is blocked”). We must go through an arduous process of having the IT department build a “deployment package” that is pushed out to GIS computers via Microsoft SCCM. Since this process takes so much effort, we update Pro only twice per year.

ArcGIS Pro’s Automatic Updates mechanism is likely disabled due to our corporate policy allowing software installs only from either the local C:\Temp folder, from a network drive or from an SCCM push. Of course, Admin creds are required for any stand-alone install of software.

Does anyone have any experiences or suggestions regarding how a large organization updates ArcGIS Pro on a regular basis more elegantly or easily? For instance, is it possible to have “Check for Updates” enabled, but have the software bits download and unpack in a prescribed place like a C:\Temp folder?

Thank you.

Re: Updating ArcGIS Pro in a Different Way?

BenTurrell — Tue, 11 Feb 2020 22:02:57 GMT

Hey Joe Flannery‌,

I used to work for a medium sized government agency who had approx 300 ArcGIS Pro installs. We used to do an upgrade once a year using a very similar system that you do. WE found our IT would take b about 3-6 months to package the software and deploy it. We investigated doing multiple packages a year but we decided that it was safer to just do major releases especially with how slow the packaging and deployment system worked.

Thanks,

Ben

If this answer has helpful please mark it as helpful. If this answer solved your question please mark it as the answer to help others who have the same question.

Re: Updating ArcGIS Pro in a Different Way?

JoeFlannery — Wed, 12 Feb 2020 13:26:27 GMT

Ben:

Thank you for your Reply. It sounds as though you had a tougher time doing updates then, than I am, currently. I guess I can live with the 4-6 week deployment workflow that we currently have. Staff get really excited about the new functionality that arrive with a full release, but we tend to wait the extra 4-6 weeks for Esri to put out the 2.x.1 version.

Thank you for your time and input.

Joe