Software Deployment

I cannot apply the new Adobe Acrobat Patch. Version 10.1.2. To my packaged version 10.1.1.

what packaging / packaging strategy are you using?
Are you patching an installation directly on the client or patching an AIP?

Kr,
PJ

I have created an AIP of 10.0.0 + 10.1.1 and now I'm trying to patch it.

I would suggest trying to patch the AIP and rolling out from there... Also, I don't know the exact rules, but I seem to remember there being odd behaviour when patching adobe products and mixing odd and even numbered patches. Could be I'm mistaken there though, maybe someone else can confirm or deny this.

PJ

I've done it a few weeks back and it worked for me.
Patch the AIP and update your clients from that.

Pieter, I haven't heard or experienced anything like that. Might be I've just been lucky though.

I thought I remember reading somewhere, maybe in Adobe's own Enterprise Administration guide, that the 10.x products wouldn't have the same nonsense with patching AIPs, yet here we are. According to Adobe's own knowledge base there is no supported path for applying a quarterly patch (10.1.2) to an AIP which has already been patched with a quarterly update (10.1.1).

So 10.1.0 > 10.1.1 > 10.1.2 is not possible. You have to build a new AIP from 10.1.0 and go straight to 10.1.2.

Adobe really is the worst when it comes to patch management. Clients that were installed from the 10.1.1 AIP cannot even auto-update to 10.1.2. They'll be prompted for a pending update, and can even apply it and all appears to work (no error of any kind), but when you check the version after patching it is still 10.1.1 and they'll be prompted again the next time they login. I had to download and manually execute the .MSP to even get a clue (an error message of some kind) what was happening.

Has anyone tried building a new AIP from BASE+LATEST_QUARTERLY, then putting the new version back in the same network share path as the old version, and finally forcing a client update? Wonder if that will work or completely trash the install on the client machines.

I have to agree that patching Acrobat AIP's is a source of frustration. When I think of creating an AIP you take the base and continue to apply any .msps required to bring it up to the latest version. It appears now that I have to take the base media and create a new AIP each time a new patch comes out for acrobat and reader.

I now just have a copy of the base AIP with no patches applied and just apply the latest to it and copy it over the existing AIP and run the install using the REINSTALL and REINSTALLMODE for existing installs. If I had the power to ban all adobe products in my organization including flash I would do it.

I mean that i created an AIP, deployed it to the clients and now trying to patch the clients with the 10.1.2 msp