2009
May 
20

Install Adobe Reader 9.1.1 across the network

Filed under: Technical — admin @ 11:44 pm

Here is an example of one way to push out Adobe Reader 9.1.1 across your network.

To begin, you’re going to need a couple of downloads:

Adobe Customization Wizard 9 (click to download direct)

Adobe Reader 9.1.0 minus Adobe Air (click to download direct)

Adobe Reader 9.1.1 Update (click to download direct)

Extract the MSI

Install the Customization Wizard for later steps. Now open a command line, traverse the file system to the folder you saved your AdbeRdr910_en_US.exe to, and type in:

AdbeRdr910_en_US.exe -nos_o./InstallFiles -nos_ne

This will create the folder InstallFiles from the directory you saved the executable in, and extract the contents there. This will generate a file, AcroRead.msi. This MSI file still needs to be administratively extracted to your network install point:

msiexec /a <path to msi from above> /t:<desired network location>

Now we want to apply the update:

msiexec /p <path to msp> /a <desired network location, same as above>

In order to work with the Customization Wizard in the next step, we need a setup.ini file in the network location, so you can create one from scratch, or copy the one that ended up in InstallFiles to the network location.

Modify the MSI

From here, you can customize the .msi file to automatically accept the EULA, silently install, as well as other options. This will create a silent installation that will uninstall any previous version of Adobe Reader as well. Open Adobe Customization Wizard 9 and open the AcroRead.msi file from the InstallFiles folder.

Make changes under “Default viewer…” and “Run Installation”:

Scroll through to the “EULA and Document Status” and auto accept the EULA:

Next, go down to the Direct Editor and make the changes that appear in the list following this image:

- In the Component table, drop any row containing ‘AdobeUpdater’ or ‘Adobe_Updater’
- In the Feature table, drop any row containing ‘AUM’ or ‘Updater’
- In the FeatureComponents table, drop any row containing ‘AUM’ or ‘Updater’
- In the File table, drop any row containing ‘AdobeUpdater’ or ‘Adobe_Updater’
- In the ModuleComponents table, drop any row containing ‘AdobeUpdater’ or ‘Adobe_Updater’
- In the MsiFileHash table, drop any row containing ‘AdobeUpdater’
- In the Registry table, drop any row containing ‘Adobe_Updater’
- In the Registry table, drop the row containing ‘Registry838′
- In the Shortcut table, drop the row containing ‘SC_READER_DT’

Save the new MSI file now. Now you have a silent installer that will remove previous versions of Adobe and install 9.1.0. Copy the resulting files that are in “InstallFiles” up to a network location that all systems have read access to, and copy the AdbeRdrUpd911_all_incr.msp file from the updater you installed to this directory as well.

Script

Let’s write a script that will first check for the existence of 9.1.0 if it’s already installed, then silently install this rebuilt MSI package. This script will also install 9.1.1 if any other previous version is installed.

:: Script to install/upgrade to Adobe Reader 9.1.1
:: Created 05/22/2009
:: By Jason Knight
:: Please contact the IT department if you have
:: any trouble with this script

If exist %systemdrive%\adobe_911.txt (
Goto eof
) else (
goto install
)

:install
msiexec /uninstall {AC76BA86-7AD7-1033-7B44-A91000000001} reboot=suppress /quiet
msiexec /i “<network path\acroread.msi>” TRANSFORMS=”<network path\acroread.mst>” /qn
echo %date% > %systemdrive%\adobe_911.txt
Goto eof

:eof

Group Policy

Easiest to utilize group policy to push this update out. Remote desktop to a server, or if you have the tools installed locally on your workstation, launch gpmc.msc. You will want to create a new policy and link it to at least your Computers OU. I run it against my entire domain so that all machines get it, since I want it installed on all my servers and all machines. You can pick your own level of granularity. Edit the policy and create a new logon script:

When you double click on Logon, you will be prompted as to the location of your adobe.bat file we created earlier. You need to determine where to place this script by clicking Browse…

As you can see, it puts it under a unique GUID. Click start… run… and type in file:///C|/domain.com (where domain is your local domain). Open up SYSVOL/domain.com/Policies and locate the GUID that this GPO is using, then User, Scripts, Logon and place the script there. Then add it to the GPO. As long as the workstation is recieving group policy correctly, the script will run. You can test this out on a virtual machine. Grab a snapshot before you implement to make sure the script is doing what it is supposed to.

PSExec

You can use psexec to push this installation out via script as well. Copy the above mentioned adobe.bat script file somewhere on your local computer and use psexec like:

psexec.exe \\* -u “DOMAIN\username” -p “yourpassword” -i -c -d “C:\Users\username\Desktop\adobe.bat” /passive

This will enumerate your domain and run the psexec command against all active machines.

Acknowledgements

Thanks to these websites and blogs for help in putting this all together:

Vulnerability Note VU#970180

http://www.kb.cert.org/vuls/id/970180

Adobe Forums thread

http://forums.adobe.com/message/1990217#1990217

Other sites

http://blog.stealthpuppy.com/deployment/deploying-adobe-reader-9-for-windows

http://www.appdeploy.com/packages/detail_pf.asp?id=1328

http://www.msfn.org/board/index.php?showtopic=113643

24 Comments »

1

If you perform msiexec /a (without /t: which doesn’t seem to work for me)
You will be prompted for administrative install location

If msiexec /p /t doesn’t work:

msiexec /a Path\Acroread.msi /update Path\updatename.msp

worked for me.

Also you want to take caution in using the “Make the Acrobat the Default Viewer” option as this may cause issues with Adobe Acrobat reader files opening within IE.

Ishmael @ June 8, 2009 9:24 am

2

Thanks for the input!

admin @ June 9, 2009 10:24 am

3

There is an error in the path to apply the update…
You have to target the msi file :

Now we want to apply the update:

msiexec /p /a

Q1t1 @ June 19, 2009 4:11 am

4

I forgot to protect the balise symbols :

msiexec /p \ /a \

Q1t1 @ June 19, 2009 4:12 am

5

msiexec /p path_to_msp /a path_to_msi_in_desired_network_location

Q1t1 @ June 19, 2009 4:13 am

6

Yes, mentioned that early in the article:

Now we want to apply the update:

msiexec /p [path to msp] /a [desired network location, same as above]

admin @ June 19, 2009 3:43 pm

7

Question, What if I just want to install 9.1 (no updater)? Attempted via GPO and got the following;

Product: Adobe Reader 9.1 — Error 2709.The specified Component name (‘Adobe_Updater.exe.77F6876D_C3C1_484B_B77B_3052FB676E32′) not found in Component table.

Dave @ July 24, 2009 6:41 am

8

Actually I’m betting I missed something in your list for omitting updating. DOH!

Dave @ July 24, 2009 6:53 am

9

Instead of using the script to first uninstall Reader you can just run:

msiexec /i “” TRANSFORMS=”” REINSTALL=”ALL” REINSTALLMODE=vomus /qn

This tells windows installer to run from the original source then re-cache the package and Reinstall even if an older version is present.

Eli @ August 12, 2009 10:50 pm

10

File paths got striped out…
msiexec /i “path\acroread.msi” TRANSFORMS=”path\acroread.mst>” REINSTALL=”ALL” REINSTALLMODE=vomus /qn

Eli @ August 12, 2009 10:51 pm

11

I am just now learning (attempting) to use this for network deployment, however, I am not being very successful.
I continually get the Windows Installer screen that gives me a list of correct syntax for using the MSIexec command. Since I have copied and pasted the commands from above, I would have to assume that the syntax is incorrect and/or incomplete.
However, since I’m a “noob”, I’m guessing that the instructions above have left out some information that is totally obvious to the trained IT professional.
Can anyone direct me a “Noob’s Step-by-Step” format?

C

Jason @ September 14, 2009 7:37 am

12

Please clarify:
Do you integrate the *.msp files into the AcroRead.msi file BEFORE or AFTER you extract it to the network location?

Jason @ September 14, 2009 8:43 am

13

Sorry about any incorrect syntax. It’s been a while since I’ve done this, so I would have to go through the steps to see where the error is.

Integrate the msp file after extracting to the network location. Steps should be in order. Please let me know if you still have issues.

admin @ September 14, 2009 8:26 pm

14

OK..I got it worked out for the most part.
this is basically what I did:
1)extracted the EXE to a local directory (INSTALLFILES)
2)extracted that MSI (in INSTALLFILES) to the Network Location
3)Created a Custom Installer using the (INSTALLFILES) and copied the setup.* files to the Network Location.
4)Ran the *.msp files (up to 9.1.3) against the Network Location

However, I still get errors when using the Setup.exe to install silently on clients. :( (“Missing Components”)
The AcroRead.msi works fine…So Im back to recreating the Custom Installer and patching it again.

Jason @ September 18, 2009 6:37 am

15

@ Dave:
I had the same problem. I fixed it by downloading instedit from http://www.instedit.com and used it to drop rows from the tables. it worked like a charm.

@Admin
Thank you for your help.

Nori @ September 21, 2009 1:45 pm

16

I’m trying to push Adobe via SMS 2003. I’ve tied falling these steps but I’m a little confused. At the end, after we do the Adobe customize wizard, you say copy the msi file from the installfiles directory up to a network location, then copy the msp from the updater we created. At what step did we create the updater? Also, what was the purpose of performing an administrative extraction to a network install if we’re using the orginal from the adberdr910_en_us.exe file? I’m just curious because I can’t get mine to work, so far, so I’m back at creating the custom install again….Thanks

Gerry @ September 24, 2009 3:29 pm

17

Here’s what I did so far
1)Downloaded AdbeRdr910_en_US.exe and extracted it to a local drive (InstallFiles)
2)Performed the administrative extraction (msiexec /a) to a network drive
3)Applied the update (msiexec /p) to the network drive’s msi file (updated to 9.1.3)

Here’s where I’m confused, which MSI file should I be running the Adobe Customize Wizard against, the one in InstallFile (orginal extraction without MSP update) or the one on the Network drive (with latest MSP update)?

Gerry @ September 24, 2009 3:49 pm

18

Modify the MSI in the network location. Everything is in the order of the steps I took. This is for silent installation, etc.

admin @ September 24, 2009 3:57 pm

19

I was referring to the file, setup.ini, that needs to exist for the Customization wizard, not the MSI file.

admin @ September 24, 2009 4:00 pm

20

This is insane. Why doesn’t Adobe just release a true silent and full install like most everyone else does and make all of this crap not necessary. It doesn’t have to be made this involved.

Jeff Alan @ September 24, 2009 8:29 pm

21

Welcome to IT. With Adobe, nothing is that simple.

admin @ September 27, 2009 11:31 pm

22

I am trying to make a script that applies a number of MSP (about 8!) as painlessly as possible…

The main thing that is preventing me from doing this is: every time you run the MSP against the MSI AIP, you are asked to specify the network location again…

Running using /passive causes the installer to hang on the “gathering information” step. Anyone know how to work around this…?

Tai @ August 16, 2011 8:45 am

23

Found my answer – use /passive with TARGETDIR=C:\Acro9aip

Tai @ August 16, 2011 9:26 am

24

Thanks for the feedback Tai!

admin @ September 27, 2011 10:36 am

Leave a comment