I've been trying to sort out the correct command line to silently install the msp file adobe published for adobe reader 10.1.2, AdbeRdrUpd1012.msp.  First, I'll state my deployment method is to use SCCM.  I've been using it for some years to deploy, remove and patch software and I am pretty familliar with it.  So the previous patch file installed by using this command line "msiexec /i "\\path to 10.1.0 MSI" PATCH="\\path to 10.1.1 MSP"  This worked perfectly.  So now I come to 10.1.2 and this method doesn't work.  I get complants from my test computers stating "Another version of this product is already installed.  Installation of this version cannot continue."  I also tried using the /p switch as "msiexec /p "\\path to 10.1.0 MSI" PATCH="\\path to 10.1.1 MSP".  When i use this method I receive a message stating "The patch package could not be opened.  Contact the application vendor..."

Clearly I am missing something as installing these updates cannot be this difficult.  I see a lot of folks using GPO.  I've never used this method and am not at all familliar with it.  It just seems to me there should be a better way to get these to install more consistantly. 

Let's see, additional details:  Target clients are all windows XP SP3.  My user account has administrator rights.  All client PC's were built using the same base image.  I've tested various methods of install from the command line and each ocassion gets me the same results.  Currently all clients are running reader 10.1.1.33.

Any thoughts, tips, suggestions are most appreciated.

If you'd like additional detail, if I missed a critical piece of information, please just let me know and I'll gladly supply that.

Thank you ladies and gents.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
0

I always use the /update switch with patches
ifn' you wanna do it with the main install I think 10.x has an INI file; tack the patch name on to the end and put the msp in the folder with the other patches.

Answered 02/24/2012 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0

If think that your issue here is that you can't install a quarter update (10.1.2) on top of a previous quarterly update (10.1.1).

You will need to uninstall the previous version and install the latest patch.

This link has further information.

Section 6.1

Thanks,

Dunnpy

Answered 02/27/2012 by: dunnpy
Red Belt

Please log in to comment
0

Owen, thank you very much.  That worked like a charm.  If the user of the /update switch is what you typically use to apply a patch file, then I also have my answer as to how to consistantly get these patch fiels applied.  Thanks again.

Answered 02/27/2012 by: Stormchoir
Yellow Belt

Please log in to comment
0

Dunnpy, can you expand on that a bit?

I'm reading the section you pointed to but I guess I'm just confused.  Isn't the second digit the quarterly update with the third digit being the security update?  So you can't install 10.1.0 over 10.0.1 because it's a quarterly update but you should be able to install 10.1.2 over 10.1.1 because that's just a security update.

Answered 03/01/2012 by: bryandam
Yellow Belt

Please log in to comment
2

This link should give you more information. It's linked from within that Admin document, but you have to follow a few links to get to it.

It shows that 10.1.1 is a quarterly update, so 10.1.2 can't go over the top of it.

I've just come across this in my environment and I've had to create a new AIP of 10.1.2 and uninstall the previous AIP installation that was patched 10.1.1 to get it on.

Hope that helps,

Dunnpy

Answered 03/01/2012 by: dunnpy
Red Belt

Please log in to comment
0

Thanks for the link dunnpy, that will come in handy for future releases.

Answered 03/01/2012 by: bryandam
Yellow Belt

Please log in to comment
0

Don't forget to rate any posts you might have found useful [:D]

Answered 03/02/2012 by: dunnpy
Red Belt

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