Patching Acrobat X

[anon60913384]

Hi All –

We are unable to apply 10.1.13 to patch Acrobat X version 10.1.3 using the supplied fixlet. As I read Adobe’s page http://helpx.adobe.com/acrobat/kb/update-patch-acrobat-reader-10.html , it looks like you can’t apply any quarterly update over a previous quarterly update. It looks like maybe you have to uninstall 10.1.3 and re-install to get to 10.1.13 (current). This seems insane. How are you handling patches to Acrobat X through IEM?

Thanks!

[amelgares]

If you installed Acrobat X via an Administrative Installation Point (AIP), then I don’t think you can use the .MSP upgrade files. You’ll need to continue to update and use AIP installers. This hit us a couple years ago and so we stopped using AIP installs. I don’t recall the details, but check out Adobe’s AIP page for more info.

We’ve been applying all the Acrobat 10.0.X .MSP updates on top of the previous with no issues.

• Aaron

[jgstew]

I’m pretty sure @amelgares has the cause of the issue.

When patching Acrobat, you often have to patch with multiple MSPs to go from an older version that doesn’t have the intermediate ones installed all the way to the newest version… but then Adobe has some updates that contain all of the previous updates plus the most current update. Those do not require using multiple MSPs for patching.

This is an older one, but this is still relevant: http://bigfix.me/fixlet/details/3703

Similar, but for reader: http://bigfix.me/fixlet/details/3700

This shows reader being installed using multiple MSPs during setup: http://bigfix.me/fixlet/details/3658

[anon60913384]

Thank you both, AIP was exactly it. We’re now working on a fixlet to uninstall the AIP version, install 10.0.0, and then patch to 10.1.13. It’s all working except that some open applications can cause the uninstall to hang. What’s the easiest way to either force a log off or a reboot at the beginning of a fixlet? We tried adding the code from the stock Restart Endpoint and Wait for Restart to Complete task, which is:

// !#plan-engine/override::pending-restart=wait
// Restart the endpoint
Restart 0

However, it seemed to just bypass that code somehow.

Thanks for your help!

[anon60913384]

The solution is to use a baseline with a separate restart task, as described here:

Restart not Restarting

(imported topic written by SystemAdmin) I have created a baseline that includes 5 steps. Step 3 is the default Restart Computer task. When I execute the baseline, the targeted system does not restart. Instead, steps 4 and 5 attempt to execute - failing, or not being relevant because the restart did not occur. Once all steps are complete, the action says the target is pending restart. I was able to force restarts by including “restart 180” at the end of step 2, but in some cases the second ta…

Thanks again!

[jgstew]

There are ways to achieve this without affecting the user. You can target the uninstall/install/update using a baseline, but only when no user is logged on or if the applications are causing it to hang are closed.

This will cause it to happen without forcing a reboot on the majority of your users. A select few will require a more forceful hand.