If I were slipstreaming service packs into an admin install, can I put 2.1.2 on top of 2.1 and it will roll up 2.1.1, or do I need to slipstream 2.1.1 first (which would be a pain....)?
For anyone that wants to know how to disable the check for updates at startup in ArcGIS Pro.
Todd Metzler wrote: Now I'd like to know: How can I disable the check for updates at startup in pro 2.1.2 (yes I patched Pro serial fasion 2.1.1 then 2.1.2) for my remote app consumers so the end user isn't tempted to try to do something they can't on our application server.
Todd Metzler wrote:
Now I'd like to know: How can I disable the check for updates at startup in pro 2.1.2 (yes I patched Pro serial fasion 2.1.1 then 2.1.2) for my remote app consumers so the end user isn't tempted to try to do something they can't on our application server.
Here is an ESRI Technical article that I found and I have applied.
FAQ: Is it possible to block update notifications in ArcGIS Pro, so that end-users are unable to install updates from wi…
Robert, thanks for the additional information, it is helpful.
Since you seem to be on top of the documentation, at least from a Desktop side, I have a couple quick questions for you:
And finally, to quote myself from Is there a place to send comments on the ArcGIS documentation?
Here is a documentation-related suggestion I share with Esri employees whenever I get the chance. Seeing you are a Documentation Product Engineer, I figure I will share it here as well.I think it would benefit Esri customers if there was a "community addition" section for the online documentation. Microsoft's Developer Network has long had this feature, and I have come across other IT-related companies that do the same thing. The reality is, there are limits to the resources devoted to documentation, and it makes sense to create more avenues for users/customers to share their knowledge about Esri products. The best place for additional comments or examples from the user community isn't in some forum like GeoNet but directly in the documentation.
Here is a documentation-related suggestion I share with Esri employees whenever I get the chance. Seeing you are a Documentation Product Engineer, I figure I will share it here as well.
I think it would benefit Esri customers if there was a "community addition" section for the online documentation. Microsoft's Developer Network has long had this feature, and I have come across other IT-related companies that do the same thing. The reality is, there are limits to the resources devoted to documentation, and it makes sense to create more avenues for users/customers to share their knowledge about Esri products. The best place for additional comments or examples from the user community isn't in some forum like GeoNet but directly in the documentation.
Robert, kudos to the team that has worked on the 'Pro help documentation. I find it the best incarnation so far.
Do us and yourselves a favor and highlight the ArcGIS Blog a bit more... buried in the 'Community' link on the landing page is a bit modest. It is full of pertinent information directly and indirectly related to the help documentation itself.
Hi, Joshua. You're welcome! And, yes, I can elaborate a bit more.
At a minimum, we update the Pro web help with each major, minor, and patch release. Extensive content updates occur with major and minor releases to incorporate new functionality. To give you an idea of the extent, there are about 650 new topics or topic versions for ArcGIS Pro 2.2 so far. We'll probably have between 800 to 1,000 topics/topic versions by the time 2.2 releases.
The web help updates that coincide with Pro's patch (i.e., "bug-fix") releases are much lighter because there isn't new functionality to describe. However, we take that opportunity to release content enhancements that are ready at that time but not specific to the next release. At 2.1, we revamped the licensing documentation section to make it more comprehensive and clear. We identified more improvements to make to that section after the release and published them when 2.1.1 went live. We also fix severe documentation problems during patch releases, such as adding a step that was missing in a tutorial, preventing people from completing a new workflow.
Although we try to keep the focus of Software Development on the next release as much as possible, when we have a critical doc problem to fix, like the one in this thread, we redirect resources to address it. This falls under critical doc updates.
Pro has two major or minor releases per year, about two to four patches per year, and we make about 10-20 critical doc updates, so that's between 14 and 26 total doc updates per year.
The people who work on Pro also work on ArcMap, but ArcMap is usually limited to two significant releases--equivalent to Pro's major and minor releases--and has 10-15 critical doc updates per year.
Robert Garrity, thanks for chiming in and sharing some information on production documentation updates. You mentioned, "we typically follow scheduled updates," can you elaborate a bit more? Even if the dates/schedules fluctuate, do you aim for semi-annually, matching up with product releases, or something else?
Hello, everyone. I'm sorry for the delay on this. As documentation lead for ArcMap and ArcGIS Pro, my goal is to provide the information you need to use these products effectively in your work. I realize that on the surface changing web help content is a simple html edit, but underneath there is more to it, such as translating to six languages, so we typically follow scheduled updates. In this case, we need to make an exception and update the content immediately.
The ArcGIS Desktop Documentation Team has a topic that covers cumulative releases in the queue, ready to be released with the next web help update. So, for now, the team is making a critical update to the "Release notes for ArcGIS Pro 2.1"--it will be covered in the intro paragraphs of the page. There are some dependencies to posting that, but I am working to get that information on the website as soon as possible.
UPDATE: The paragraph has been added to the Release Notes topic. At 2.2, a new topic will be added, and it will cover how Pro adheres to semantic versioning and that you can expect patches to be cumulative. The Release Notes topics will link to the new one.
If the Pro documentation team had seen it by Mar 1, 2018, why have they not updated the release notes page by Apr 26? I have just spent 15 minutes finding and reading this thread. Can I send an invoice for my time?!?!
"I think ESRI is under the mistaken impression that all users are going to have the admin rights necessary to hit that update button, when the opposite is the reality." Agree! Besides, in the enterprise world users don't really get to choose application patching. The team responsible for the app sets the schedule after 1st testing the patch in a controlled environment to ensure nothing else gets broken in the enterprise as a result of patch application.
Hi, yes, Pro documentation team has seen this thread. Thanks for reporting the confusion.
Xander Bakker, where are you seeing that bullet item? I don't see it on the release notes page, and I just did a Ctrl-F search for it. In My Esri under Additional Information, this is what I see:
ArcGIS Pro 2.1 must be installed prior to installing any ArcGIS Pro 2.1 patches. This ArcGIS Pro patch download is equivalent to the software update(s) while using ArcGIS Pro. Click the Issues Addressed link for a listing of what is available in the patch.
When I click on the Issues Addressed link in My Esri, it takes me to the Release Notes page where that text isn't showing up for me.
Great xander_bakker I did not see that yesterday.
You must have ArcGIS Pro 2.1 installed prior to installing ArcGIS Pro 2.1 Patch 2 (2.1.2).ArcGIS Pro 2.1 Patch 2 (2.1.2) includes all the fixes in ArcGIS Pro 2.1 Patch 1 (2.1.1)
It is funny, in a sad way, the Pro documentation is so vague because the ArcMap documentation has always been quite clear. For example, the description for ArcGIS Data Reviewer 10.5.1 Patch 3 for (Desktop | Server) states, "This patch is cumulative of all previously released Patches and Hot Fixes for ArcGIS Data Reviewer 10.5.1."
Back to your question. Can I answer it with certainty, no. Since Esri doesn't state which files are updated to which version with any patches, and they don't state that 2.1.2 is cumulative, I can't say unequivocally that the 2.1.1 fixes are in 2.1.2. That said, I am able to enter minus signs for long and short integer fields for attribute tables, which was an issue (BUG-000111161) addressed in the first patch. So empirically, or maybe anecdotally, the 2.1.1 fixes are rolled into 2.1.2.
https://community.esri.com/ideas/14635-pro-service-packs-should-indicate-if-cumulative-they-should-be-anyway
Hmmmmm. I think ESRI is under the mistaken impression that all users are going to have the admin rights necessary to hit that update button, when the opposite is the reality. I think IT subscribes to the release updates because they mysteriously don't answer the phone around the same time. In a future world, by the time we get SP.X installed (1 year after release), SP.Y and Z have been released. I'd like to be in a scenario where I just wait for Z, and roll up X and Y in the process. If that's no longer the case, that goes against what most software producers practice. Can you imagine if you have to install every SQL CU in ordinal order? I'm also under the naïve impression that I'm going to be able to roll Pro out using one of those magic deployment tools (my fault, not ESRI's, I've never gotten that to work). So your install says 2.1.2, but can you tell if the 2.1.1 fixes got applied?
tpcolson, there you go again, being all enterprise-y and trying to slipstream packages.
I agree the documentation is incomplete. Given the size of 2.1.1 patch was 20 MB and 2.1.2 was 70 MB, my hunch was all the 2.1.1 fixes were rolled into 2.1.2. I just tested on a newly installed Pro 2.1 machine, and I was able to go straight to 2.1.2 without installing 2.1.1 first.
My read as well... the 2.1.2 patch only list the issues which will work in 2.1, 2.1.1 and 2.1.2. There is no duplication in the list with the 2.1 and 2.1.1 list.
Besides, I get the notice, and I install but I am not in a controlled environment
Based on the Release notes it looks like each patch has different fixes and would need to be installed 2.1.1 then 2.1.2.
Release notes for ArcGIS Pro 2.1—ArcGIS Pro | ArcGIS Desktop
I am not 100% but seems like it may be the case. My guess is that the intention is that updates will be performed as available so most Pro installations would already be at 2.1.1.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
