Example: I have a managed install of Adobe reader 10.1.0 which is told to go to a group of computers and works fine but there is an update to it of 10.1.2. If the update is run and the systems stay in that same group then the managed install thinks it needs to deploy 10.1.0 again.
I'm looking for the best way to handle versions so that this wouldn't happen without having to create a new managed install for the 10.1.2.

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

3
We are having the same issue. We haven't had time to go back and change it yet, but here is what I think will work.
You would probably need to make a Smart label for machines in that group that do not have Adobe Reader , any version, and add deploy the software to that label. Once the machine has that software and checks in, it should drop out of that Smart Label. That way, once it upgrades, it will not go back and install the older version.
Answered 04/04/2012 by: WGM_Jeff
Fourth Degree Black Belt

  • Utilizing a smart label would be the best way to handle this. You can try to craft smart labels that also include the version number, but that gets tricky. Just checking for the presence of Adobe Reader would be a good way to handle it.
    • The "proper" way to do this is with a regex and check for all versions lower than the current version. Kind of a pain to setup but its worth it.
  • Great ideas, thanks a bunch. I'm hoping down the way they will add some features to take care of this. Maybe will request a feature upgrade.
Please log in to comment

Answers

1
This might be a red herring for your issue, however you can't upgrade 10.1.0 to 10.1.2 - a quarterly update can't go on top of previous quarterly update.


Section 6.1 of below linked Adobe document:

"Know when you can reuse AIPs and when you have to create a new one. For example, Acrobat 10.x
quarterlies are cumulative and cannot be installed on top of each other. For Reader, reuse is ok until
an MSI appears or when you need to apply a quarterly over a security update. This means that for
Acrobat you can always reuse the AIP of the base release, and for Reader you can always reuse that
AIP of the base release or the last MSI (whichever is the most recent)."

http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Enterprise_Administration.pdf

Hope that helps,

Dunnpy
Answered 04/05/2012 by: dunnpy
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share