/build/static/layout/Breadcrumb_cap_w.png

Which MSI for Adobe Reader 8.1.3?

For Adobe Reader 8.1.3 (we cannot use version 9.x, due to backwards-compatibility issues, also, I AM aware of the Security vulnerability with 8.1.3), I can:

1. Download the EXE, then, use the technique described in, http://kb.adobe.com/selfservice/viewContent.do?externalId=kb400540&sliceId=2 , to extract the (small) MSI and (large) CAB file, use the Customization Wizard to configure, and, standard MSI install (we'd be using SCCM to deploy).

2. Download a (larger) MSI from http://download.adobe.com/pub/adobe/reader/win/8.x/8.1.3/enu/AdbeRdr813_en_US.msi , and use the Customization Wizard on it, directly.

Only difference I see (I think) is that #1 may install faster, but, is a larger package to deploy, while #2 will install slower (maybe) as it has to decompress.

Is there a more desired version to use?

Thanks!

0 Comments   [ + ] Show comments

Answers (14)

Posted by: nheim 15 years ago
10th Degree Black Belt
0
Hi Bill,
Download: ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.3/enu/AdbeRdr813_en_US.msi
And then do an admin install and apply:
ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.4/misc/AdbeRdrUpd814_all_incr.msp
to it. Then you should be on the safe side.
Regards, Nick
Posted by: gmouse 15 years ago
Orange Senior Belt
0
Yeah, I JUST stumbled upon that FTP site...not even on their website, even.

But...if I was NOT to do the Admin Install, and, just wanted to add in the MSP, would the procedure (and, maybe the setup.exe file) I describe below work (I JUST posted on the Adobe Forums)?

>>There's an article on using a newer Setup.exe (Adobe Bootstrapper) for Adobe Acrobat PRO-STD, that allows chaining MSP files, as they never released a cumulative patch. This is at: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403246&sliceId=2

Will this also work for Reader? The 8.1.4 MSP is here: ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.4/misc/ <<

Thanks!
Posted by: nheim 15 years ago
10th Degree Black Belt
0
Hi Bill,
there's an easier way. Use the technic, i have described in this post:
http://www.appdeploy.com/messageboards/fb.asp?m=45789
Regards, Nick
Posted by: sammy09 15 years ago
Yellow Belt
0
hoping someone can help.. i have a customised 8.1.3 package (I got the exe, extracted it out to having an msi, mst & ini etc)... I've now downloaded the 8.1.4 msp and used

msiexec /p %TEMP%\814\AdbeRdrUpd814_all_incr.msp /a %IPATH2% SHORTFILENAMES=TRUE /qb /log %WIN%\appslogs\AdbeRdr814.log

where ipath2 is %TEMP%\813\AcroRead.msi and %temp% is where i'm storing all the files)
I do see it try and do the 8.1.4 install but bottom line.. 8.1.4 doesn't end installed.. this is part of the log

DEBUG: Error 2746: Transform BRZToBRZ invalid for package C:\Windows\Installer\198224c1.msi. Expected product {AC76BA86-7AD7-1046-7B44-A81300000003}, found product {AC76BA86-7AD7-1033-7B44-A81300000003}.
1: 2746 2: BRZToBRZ 3: C:\Windows\Installer\198224c1.msi 4: {AC76BA86-7AD7-1046-7B44-A81300000003} 5: {AC76BA86-7AD7-1033-7B44-A81300000003}


lots of this.. so i'm thikning its saying i'm not using the right msi... which one should i be using?
Posted by: gmouse 15 years ago
Orange Senior Belt
0
We do this, using SCCM:

1. Remove the other versions, including 9.x, using a modified VBS script found on appdeploy.com:

>>Dim objShell
Set objShell = WScript.CreateObject("WScript.Shell")
On error resume next
Dim OldVersion
Dim sngVersion
'<!--- Adobe Reader --->
' Adobe Readers
sngVersion = objShell.RegRead ("HKLM\SOFTWARE\Adobe\Acrobat Reader\9.0\Installer\ENU_GUID")
if NOT sngVersion="" then
objShell.run("msiexec /x " & sngVersion & " /qn /norestart"), 0, True
end if
OldVersion = objShell.RegRead ("HKLM\SOFTWARE\Adobe\Acrobat Reader\8.0\Installer\ENU_GUID")
if NOT sngVersion="" then
objShell.run("msiexec /x " & sngVersion & " /qn /norestart"), 0, True
end if
OldVersion = objShell.RegRead ("HKLM\SOFTWARE\Adobe\Acrobat Reader\7.0\Installer\ENU_GUID")
if NOT OldVersion="" then
objShell.run("msiexec /x " & OldVersion & " /qn /norestart"), 0, True
end if
OldVersion = objShell.RegRead ("HKLM\SOFTWARE\Adobe\Acrobat Reader\6.0\Installer\ENU_GUID")
if NOT OldVersion="" then
objShell.run("msiexec /x " & OldVersion & " /qn /norestart"), 0, True
end if
WScript.sleep 60000<<

2. Like the newer setup.exe for Adobe Acrobat Pro or Std, this new one allows you to "slipstream" and "stack" MSP's in the ini, so, we use the Tuner to setup features, then, we just added in the mention of the MSP in the INI:

>>[Startup]
RequireOS=Windows 2000
RequireMSI=3.0
RequireIE=6.0.2600.0
CmdLine=/rs /sAll
[Product]
msi=Adobe813.msi
CmdLine=TRANSFORMS="Adobe813.mst"
PATCH=Adobe814.msp
[Windows 2000]
PlatformID=2
MajorVersion=5
ServicePackMajor=4
[MSI Updater]
Path=http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.0/misc/WindowsInstaller-KB893803-v2-x86.exe<<

As to the locations, poke around on their FTP site to find all files.

We had a conference call with Adobe, and, mentioned that their "where things are, and, what to use, and, how to do it" info could use severe upgrading. They agreed.
Posted by: anonymous_9363 15 years ago
Red Belt
0
We had a conference call with Adobe, and, mentioned that their "where things are, and, what to use, and, how to do it" info could use severe upgrading. They agreed...."then we all held our breath, waiting for that change to be implemented, because Adobe is such a responsive vendor." Well, I'm holding mine. Is everyone else?
Posted by: gmouse 15 years ago
Orange Senior Belt
0
Adobe, actually, does seem to be at least trying to get better. But, they are on MY "A" list:

AutoDesk
Apple
Adobe
Posted by: sammy09 15 years ago
Yellow Belt
0
is there a method to install ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.3/enu/AdbeRdr813_en_US.msi
and then install ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.4/misc/AdbeRdrUpd814_all_incr.msp .. once those two are done and we see the 8.1.4 in the help->about adobe reader dialog, can we THEN install an mst to customize the package?
Posted by: jcarri06 15 years ago
Senior Purple Belt
0
Hi Sammy,

If I understand your question right, your best best would be to create and administrative install, apply the msp to it, and then create an MST based off the new msi. To do this:

1. msiexec AdbeRdr813_en_US.msi /a TARGETDIR=c:\somefolder
2. msiexec /a c:\somefolder\AdbeRdr813_en_US.msi /p AdbeRdrUpd814_all_incr.msp
3. Create the new MST using the now patched c:\somefolder\AdbeRdr813_en_US.msi (you probably won't have to create a new MST...in the past I've been able to use the previous MST and just apply it to the new MSI...worth a try :) )

Hope this helps,
Jorge
Posted by: sammy09 15 years ago
Yellow Belt
0
ok.. I still have the update problem from 8.1.3 to 8.1.4 but i've got more specifics now on the problem.. i'll put everything there and if anyone can help... that would be awesome.

I downloaded AdbeRdr813_en_US.exe and then extracted it.. once i had the msi, cab etc..i edited the msi using adobe 8 cust wizard and customized some settings. I also downloaded AdbeRdrUpd814_all_incr.msp.. so when i ran my customized install of 8.1.3 and then ran my 8.1.4 package things seem to go well until i opened reader and looked at the help->about..which reported 8.1.3.
upon further inspection.. the install log of 8.1.4 reported;

DEBUG: Error 2746: Transform BRZToBRZ invalid for package C:\WINDOWS\Installer\b566ec.msi. Expected product {AC76BA86-7AD7-1046-7B44-A81300000003}, found product {AC76BA86-7AD7-1033-7B44-A81300000003}.
1: 2746 2: BRZToBRZ 3: C:\WINDOWS\Installer\b566ec.msi 4: {AC76BA86-7AD7-1046-7B44-A81300000003} 5: {AC76BA86-7AD7-1033-7B44-A81300000003}
it says that about 10 times.

(I think its a language thing.. 1033 rings a bell).. but why? the onrignal exe was an english package.and from what i see..the 8.1.4 is supose to support all langs)....yea 1033 is english.. 1046 is Portuguese...so what is going on?

so the expected msi and found msi GIDs are different... my question is..how do i get past this to have a successful install of my 8.1.4 on-top of my customized (via mst) of my 8.1.3? Where/what is this msi that 8.1.4 is looking for to proceed?

thanks in advance

just as a followup to my original message.. regarding the 8.1.4 install log that had all the warnings with the msi it expected and the different one it found... at the bottom of the log..this is what I got;

Property(S): SourcedirProduct = {AC76BA86-7AD7-1033-7B44-A81300000003}
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 - Update 'KB408682' installed successfully.

MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 -- Installation operation completed successfully.

when i go into adobe reader -> help -> about i stillget 8.1.3

I get the same results by the way if instead of extracting the exe (AdbeRdr813_en_US.exe) i use the msi (AdbeRdr813_en_US.msi).
Posted by: anonymous_9363 15 years ago
Red Belt
0
when i go into adobe reader -> help -> about i stillget 8.1.3 An important lesson to learn is that vendors are dumb. The version number you see presented in Help/About may come from a file, a registry setting, or it may be hard-coded in the EXE you're running. Always check the version nunbers of lots of files as well as the date/time stamps.

You don't mention whether or not you followed the advice to create an AIP. Did you? That's the way to handles patches, IMV.
Posted by: gmouse 15 years ago
Orange Senior Belt
0
To let you know just how hard this is...

The acrord32.exe will stay at 8.1, you have to look at acrord32.dll to see 8.1.4.

The GUID used for the product remains at 8.1.3, looking within it, you'll see the 8.1.4 version.
Posted by: lawson23 15 years ago
Senior Yellow Belt
0
Sorry to jump in here but what I need to ask is related to this topic.

First we deploy 8.1.3 via gpo using the first method in post 1 where you download exe run extraction on it and us CIW to create a custom mst file and deploy.

Second I'm trying to now get 8.1.4 installed into this install. I have tried 3 different methods with failing results.
1. add to the setup.ini - PATCH=AdbeRdrUpd814_all_incr.msp
This never installs the patch during deployment
2. use my current acroread.msi and use the patch method msiexec /a c:\somefolder\acroread.msi /p AdbeRdrUpd814_all_incr.msp
creates some folders and updates the acroread.msi. This does not update the Data1.cab file though. So when you install it says installing 8.1.4 and it opens and in help about says 8.1.4 but if you look at any of the dll's they all are 8.1.3 versions. So to me the update was not run.
3. download the AdbeRdr813_en_US.msi run msiexec /a c:\somefolder\AdbeRdr813_en_US.msi /p AdbeRdrUpd814_all_incr.msp creates some foldres and updates the AdbeRdr813_en_US.msi file. So when you install it says installing 8.1.4 and it opens and in help about says 8.1.4 but if you look at any of the dll's they all are 8.1.3 versions. So to me the update was not run.

So in conclusion I have followed every step here but end up with the same result no actual 8.1.4 running adobe install.

Please any information you can provide would be GREAT.
Posted by: ojw 14 years ago
Yellow Belt
0
Hi lawson23,

I had the same problem and have found the answer:
You need to first extract the 8.1.3 with the /a parameter to a folder, and then (in a second msiexec command) patch 8.1.4 onto that folder with the /p parameter - it is not possible to do both at once and it is not possible to patch a "standard" folder (ie: one with a cab file).

I have deployed 8.1.4 by GPO as a new application which upgrades 8.1.3, and I will do the same for 8.1.5 (and now 8.1.6) by making a copy of the admin folder and then patching the copy. The alternative is to use the same folder/application and choose "redeploy".
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ