Acrobat 8.1.2 MSP will not update old MSI

Question

Has anyone been able to update the Adobe Acrobat MSI file with the 8.1.2 MSP and push it out through Active Directory? I run the
msiexec /a "MSIFILE" /p "MSPFILE"
command and it says it updated the msi.
Then when I try to run the msi file it go to install/repair/remove 8.1.1. However when I just try to run the AcrobatUpd812_all_inc.msp it will let me install 8.1.2 with no problem. Is there something wrong with the patch or the way I am trying to patch it and push it out? I need it to be included into the MSI so I can push it out to all my users.

Answer 1

Here's some info that I found on the adobe forum sites that
corrected my problem with applying patches to an admin install point.
I recently got msiexec v4.5 from MSoft (which can't install on
Win 2K) but only on the later XP and Vista, and server 2003. Thus,
msiexec v3.1 will work too.
The common mistake people are making is that based on ones
interpretation of the MSoft msiexec documentation and which
AcroPro.msi to use. The first step to patching is to copy
all the files from the Acrobat install disk to ones hard drive.
After doing this, the person wants to create an admin install point
and then patch the AIP. What people are interpreting wrongly from
the msiexec documentation (an honest mistake) since they will perform
each step one at a time instead of all at once, and also that in the
future when a patch comes out, they will run the patch on the AIP
using the same sequence is filename AcroPro.msi. If all the patches
were applied in one commandline along with creating the AIP, the
AIP will be patched all at one. However, the easy thing for humans
to do is run one command at a time which is creating the problem with
the MAGAZINE_Ad_2006_JPN.jobopti file not found in the Data1.cab since each time the apply a patch they use the original AcroPro.msi
file that came from the Acrobat install disk, instead of the new
one that is created and updated in the AIP directory. Once people
create the AIP using the original AcroPro.msi file, they must then
patch the AIP using the new AcroPro.msi that is in the AIP directory.
Here's an example that a copied from Nhiem which fixed the problem.
Adobe web and technical support along with their KB articles
couldn't help because they didn't know why/how people were making
mistakes.
1). create an AIP using the original AcroPro.msi
msiexec /a "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcroPro.msi" TARGETDIR="c:\test\acroPro812"
2), Apply the patches, but use the NEW AcroPro.msi in the AIP directory and not the one used in step (1) above.
msiexec /a "c:\test\acroProAIP\AcroPro.msi" /p "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcrobatUpd810_efgj_incr.msp" TARGETDIR="c:\test\acroProAIP"
msiexec /a "c:\test\acroProAIP\AcroPro.msi" /p "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcrobatUpd811_all_incr.msp" TARGETDIR="c:\test\acroProAIP"
msiexec /a "c:\test\acroProAIP\AcroPro.msi" /p "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcrobatUpd812_all_incr.msp" TARGETDIR="c:\test\acroProAIP"
3). I was able to apply the 6468.mst file to the new AcroPro.msi
and save it off using ORCA from Msoft. However, if I try to
use the commandline shown below, I get a 2203 Internal error and
it won't install (no filename specified when it does this). However,
if I specify the TRANSFORM file at the sametime I'm applying the
v8.1.2 patch, I get no error. But, when I view the AcroPro.msi
with ORCA and look at the entry, the port number that this transform
does which changes this number doesn't change the data. This transform
has conditions in it that check to see if the patch version is
greater than v8.1.1 and v8.1.2 since the port number was mistakenly
changed in these patches.
any ideas other than to apply it after the Acrobat software has
been installed from the install point using the /i switch which
commandline containing the transform option and filename?
Here's the command I'm running.
msiexec /a "c:\test\acroProAIP\AcroPro.msi" TRANSFORMS="c:\acrobat8pro\Adobe Acrobat 8 Professional\6468.mst" TARGETDIR="c:\test\acroProAIP"
See Adobe's kb article; however, the usage of the AcroPro.msi
is wrong since it implies to use the original one after the AIP
to patch Acrobat 7 files which is why people are mislead and
are getting all the problems they are getting. See,
http://kb.adobe.com/selfservice/viewContent.do?externalId=330817