Upgrade to / install Adobe Acrobat Reader 9 centrally using Active Directory group policies.

Upgrade to / install Adobe Acrobat Reader 9 centrally using Active Directory group policies.

In January 2008 I published an article Installing Adobe Acrobat Reader centrally with Active Directory group policies. The time has come to upgrade to Acrobat Reader 9 now. So I'll be taking you through some simple steps today to get that part done.
If you want to push out Adobe Reader for the first time I suggest you follow the old guide located at http://www.nixadmins.net/node/317 and substitute everything Acrobat 8 related with 9.
What you need to complete this how-to is the Adobe Customization Wizard 9 and Acrobat Reader 9.

Download links:
Adobe customization wizard 9:
http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=3993&fileID=3727
Adobe Reader 9
http://www.adobe.com/products/acrobat/readstep2.html?promoid=BUIGO

Getting the MSI package

As you might have noticed the Acrobat Reader 9 is a .exe file. It does include a MSI we just need to get it out of there.
Run the install from a command prompt or a run field.

D:\temp\AdbeRdr90_en_US.exe -nos_ne

You will find your fresh adobe packages in
Windows XP
%Userprofile%\Local Settings\Application Data\Adobe\Reader 9.0\Setup Files\READER9
Windows Vista
%userprofile%\AppData\Local\Adobe\Reader 9.0\Setup Files\READER9
Copy out all the files in that directory. I copied them to the desktop.

Let's get on to the customization wizard.

Modifying the Adobe reader 9 installation package

Now that we have the MSI package we can start modifying it. So start up Adobe Customization Wizard and open your fresh MSI and let's get started.

Adobe Customization Wizard 9

Now you should read and understand the settings in the wizard. And also read the End user license agreement (EULA). If you select not to show it YOU agree with it for your whole organization.

The following are the settings I changed.

  • Installation options
    • Make Adobe Acrobat reader the default viewer if Acrobat and Reader are installed. I set this because there are some new features in reader 9 and our organization still uses Acrobat 8.
    • Enable optimization
    • Enable caching of installer files on local harddrive
    • Run installation silently, we don't want the user to participate at all in the process.
    • Suppress reboot, users reboot often enough and most our computers are set to install updates 3 A.M so they will reboot soon enough.
  • Shortcuts
    • I left Programs->Adobe Reader 9 but removed the desktop icon. I see no reason at all in having it clutter the desktop. Most I'd guess over 99% of users click the file to open not start up Adobe Acrobat reader and then open the file.
  • EULA and document status
    • Suppress display of End User license agreement. I really don't want the users to see it. Bu be sure to read it yourself BEFORE you accept it.
    • Hide document message bar
  • Online and Acrobat.com features
    • Disable all updates, I want to see to the updates myself, to keep application compatibility.
    • Load trusted root certificates from adobe, check Enable and install silently
    • In adobe reader, disable Help purchase of Adobe Acrobat. All our software is bought by the IT apartment, not single users.
    • Disable product improvement program. I really hate theese.
    • Disable viewing of PDF with ads for Adobe PDF
    • Display in browser, enable
    • Disable all acrobat.com access including initiation and participation.

That's it, now save the file and copy all the files to the fileshare you use to deploy software, in my case \\server\userapps\Adobe Reader 9. On the next page we continue with assigning the policy to the computers in your organization.

I have tried to install

I have tried to install adobe 9, am it's not working, I have attached a log file. I have also read in another post that the .mst must be added, can you advise.

Thanks Mike

=== Verbose logging started: 11/14/2008 11:02:05 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: \??\C:\WINDOWS\system32\winlogon.exe ===
MSI (c) (B4:70) [11:02:05:609]: Resetting cached policy values
MSI (c) (B4:70) [11:02:05:609]: Machine policy value 'Debug' is 0
MSI (c) (B4:70) [11:02:05:609]: ******* RunEngine:
******* Product: {ac76ba86-7ad7-1033-7b44-a90000000001}
******* Action:
******* CommandLine: **********
MSI (c) (B4:70) [11:02:05:609]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (B4:70) [11:02:05:609]: Grabbed execution mutex.
MSI (c) (B4:70) [11:02:05:781]: Cloaking enabled.
MSI (c) (B4:70) [11:02:05:781]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (B4:70) [11:02:05:781]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (5C:84) [11:02:05:828]: Grabbed execution mutex.
MSI (s) (5C:88) [11:02:05:828]: Resetting cached policy values
MSI (s) (5C:88) [11:02:05:828]: Machine policy value 'Debug' is 0
MSI (s) (5C:88) [11:02:05:828]: ******* RunEngine:
******* Product: {ac76ba86-7ad7-1033-7b44-a90000000001}
******* Action:
******* CommandLine: **********
MSI (s) (5C:88) [11:02:05:828]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (5C:88) [11:02:05:828]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (5C:88) [11:02:05:828]: User policy value 'DisableMedia' is 0
MSI (s) (5C:88) [11:02:05:828]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Looking for sourcelist for product {ac76ba86-7ad7-1033-7b44-a90000000001}
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Adding {ac76ba86-7ad7-1033-7b44-a90000000001}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Now checking product {ac76ba86-7ad7-1033-7b44-a90000000001}
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Media is enabled for product.
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Processing net source list.
MSI (s) (5C:88) [11:02:05:828]: SOURCEMGMT: Trying source \\spring-lake\shared\Userapps\reader9\.
MSI (s) (5C:88) [11:02:06:156]: Note: 1: 2303 2: 5 3: \\spring-lake\shared\
MSI (s) (5C:88) [11:02:06:156]: Note: 1: 2303 2: 5 3: \\spring-lake\shared\
MSI (s) (5C:88) [11:02:06:156]: Note: 1: 2303 2: 5 3: \\spring-lake\shared\
MSI (s) (5C:88) [11:02:06:156]: Note: 1: 2203 2: \\spring-lake\shared\Userapps\reader9\AcroRead.msi 3: -2147287035
MSI (s) (5C:88) [11:02:06:156]: Note: 1: 1706 2: -2147483646 3: AcroRead.msi
MSI (s) (5C:88) [11:02:06:156]: SOURCEMGMT: Processing media source list.
MSI (s) (5C:88) [11:02:07:234]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (5C:88) [11:02:07:234]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (5C:88) [11:02:07:234]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (5C:88) [11:02:07:234]: SOURCEMGMT: Processing URL source list.
MSI (s) (5C:88) [11:02:07:234]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (5C:88) [11:02:07:234]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (5C:88) [11:02:07:234]: Note: 1: 1706 2: 3: AcroRead.msi
MSI (s) (5C:88) [11:02:07:234]: SOURCEMGMT: Failed to resolve source
MSI (s) (5C:88) [11:02:07:234]: MainEngineThread is returning 1612
MSI (c) (B4:70) [11:02:07:234]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B4:70) [11:02:07:234]: MainEngineThread is returning 1612
=== Verbose logging stopped: 11/14/2008 11:02:07 ===

Posted by Mike (not verified) on Fri, 2008-11-14 20:54
After I've pushed the Adobe

After I've pushed the Adobe Reader 9, I've lost the icon on my PDF-files... I've really tried everything....
When i install the same package locally, it works - but when i do it with a domain user - the icon is gone...
I've postet a question on Exchange Experts - but I really hope i can correct the "error" thru the AD.

Help?

Posted by AC (not verified) on Thu, 2008-10-30 12:23
Hmmm, I can't find the

Hmmm, I can't find the Software installation policy tab?...

Posted by Anonymous (not verified) on Wed, 2008-10-22 12:59
Thanks for giving it a look.

Thanks for giving it a look. I'll check back next week.

Posted by Adam Bunker (not verified) on Fri, 2008-09-26 22:40
Great guide! I've tried

Great guide! I've tried replicating this on several test computers in my Win2008 / WinXP (SP3) environment to deploy a new installation of Acrobat Pro 9 to no avail. The Application logs on the target computers report an error eventID 1013, then a Fatal error during installation eventID 102. These very same computers are assigned a policy to install Adobe CS3 via script, and it works without a problem. Any ideas? Thanks for the help.

Posted by Adam Bunker (not verified) on Fri, 2008-09-26 19:22
Hi Adam. I'll just post a

Hi Adam.
I'll just post a quick answer now. I'm quite busy this weekend so I'll take a look at that first thing Monday morning.

Posted by Diezel on Fri, 2008-09-26 20:43
Any luck?

Any luck?

Posted by Adam (not verified) on Mon, 2008-10-06 19:44
I'm setting up a new test

I'm setting up a new test environment tonight. I just can't replicate that error.
Does the MSI work normally if you do a normal install using it?

Posted by Diezel on Mon, 2008-10-06 21:40
Yes, the MSI works by

Yes, the MSI works by itself; of course I have to input the serial, and attend the whole install.

Posted by Adam (not verified) on Thu, 2008-10-16 18:40
I just noticed you are

I just noticed you are installing Acrobat, not Reader. I'm guessing your problem is that it asks for a serial. When you assign a MSI to a computer it can't interact with the installer so I'm guessing that's your problem. You need to get the serial into to MSI or use an MST, I've never deployed Acrobat so I really can't help you there.

Posted by Diezel on Mon, 2008-10-20 20:03
The serial is in the .mst

The serial is in the .mst that i setup with the customization wizard, so that's not it. I've figured out that the problem is that rather than just "assigned", the package must be setup as advanced. In properties, under the modifications tab, the .mst must be added. A slight oversight that caused my install to fail every time. But it works as of 5 minutes ago! Thanks for the help looking into it.

Posted by Adam Bunker (not verified) on Wed, 2008-10-22 19:07
Post new comment
The content of this field is kept private and will not be shown publicly.