Deploying Adobe Reader 9 for Windows

July 7, 2008

in Deployment

AdobeReaderIcon The latest version of Adobe Reader is available, so here’s a few preliminary details on what you might need to know when deploying it. It seems like only yesterday we were pulling our collective hair out over Adobe Reader 8 and now Adobe Reader 9 has been released and we’ve got to start over again. The Adobe Reader blog has some details on what’s new in this version. You can also find links to all sorts of Adobe Reader resources here too.

First Impressions

As usual consumers will have the Google toolbar pushed on them if they don’t de-select that option when downloading Reader, and now you’ll also get Adobe AIR along with Reader too. Awesome, more stuff we don’t really need. A default install leaves two icons on the desktop now – Adobe Reader 9 plus one for Acrobat.com.

The good news though, is Reader 9.x is fast. I hadn’t ever found Reader 8 to be slow, but version 9 certainty runs noticeably faster than previous versions.

Downloading Adobe Reader

Adobe Reader 9.1 is available for download for many languages, including:

Adobe AIR is only bundled with the English and German versions of Reader 9 so far.

What To Do About Adobe Updater

Reader 9 continues to include the Adobe Updater application which has been updated to version 6. While I haven’t seen it misbehave for some time and it no longer drops an Updater folder in your Documents folder, you might still want to disable it.

There are a few ways to do this. You can disable Updater by running it (click Help / Check for Updates) then click the Preferences link. You will then see the Preferences dialog like this, where you can choose to disable Updater:

UpdaterPrefs

To problem with this approach is that you need Internet access just to get to the preferences dialog. A bit of a problem if you’ve got Internet access issues. To disable Updater from running automatically you can run the following command line as an administrator (or an elevated command prompt in Windows Vista):

REG ADD "HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\9.0\FeatureLockdown" /v bUpdater /d 0 /t REG_DWORD /f

Alternatively, to completely remove Adobe Updater, after installation, delete this folder:

  • C:\Program Files\Common Files\Adobe\Updater6 (32-bit Windows)
  • C:\Program Files (x86)\Common Files\Adobe\Updater6 (64-bit Windows)

If Adobe Reader is running as a standard (or limited) user account, Adobe Updater won’t run at all, so it shouldn’t be an issue if you don’t give users administrative access to their workstations.

If you are virtualising Adobe Reader, then disabling or removing Updater is a must.

Extracting Reader Setup Files

Before deploying Reader 9, you will want to extract the files from the file you’ve downloaded, so that you can create a custom tranform file. To extract the file, run the following command line:

AdbeRdr910_en_US_Std.exe -nos_ne

You will then find the extracted file in these locations:

  • %LOCALAPPDATA%\Adobe\Reader 9.1\Setup Files (on Windows Vista/2008)
  • %USERPROFILE%\Local Settings\Application Data\Adobe\Reader 9.1\Setup Files (on Windows XP/2003)

Once extracted, you will have the setup files for both Reader and AIR. The setup files for Reader are in a sub-folder called ‘Reader9’.

Creating a Custom Transform File

When deploying Reader there are some customisations that I recommend making to the installation, including:

  • Prevent the installation of Adobe Updater 6 (If you want control over the version of Reader)
  • Prevent the Adobe Acrobat SpeedLauncher from being added to the Run key in the registry
  • Prevent the ‘Adobe Reader 9’ shortcut from being added to the desktop (Keep the desktop and tidy)
  • Prevent the installation of the Adobe Syncronizer [See this comment before removing Syncronizer]
  • Accept the EULA

Adobe usually provide a customisation tool for automating the installation of Reader, however the Customisation Wizard for Reader and Acrobat 8 wasn’t released until 6 months after the products themselves were released. To customise the installation I’ve used the excellent InstEd instead.

Here’s what I’ve configured as a minimum in my transform:

Prevent Adobe Updater Installation

  • 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’

Prevent Adobe Acrobat SpeedLauncher At Startup

  • In the Registry table, drop the row containing ‘Registry838’

Prevent the Adobe Reader 9 Desktop Shortcut

  • In the Shortcut table, drop the row containing ‘SC_READER_DT’

Prevent Adobe Syncronizer Installation

  • In the Property table, set the value for SYNCHRONIZER to YES

Accept the EULA

  • In the Property table, set the value for EULA_ACCEPT to YES

Also in the Property table, you could set the value of DISABLE_BROWSER_INTEGRATION to YES, to prevent Reader from opening within the browser. This would be beneficial in Terminal Server environments. When a PDF file is opened within the browser and the user then browses to a different page, the Reader components are stay in memory until the browser is closed.

You can download a transform with all of the modifications listed above here (except disabling Syncronizer; use at your own risk):

Adobe Reader 9.1 Custom Transform

Creating a Custom Transform with Adobe Customisation Wizard 9

Adobe have recently released the Adobe Customisation Wizard 9 which is the best place to start when creating a custom transform for Acrobat or Reader 9. Here are the settings I would recommend you configure when creating a transform:

Under Installation Options set:

  • Run Installation to Unattended
  • If reboot required at the end of installation to Suppress reboot

Under Files and Folders:

  • Add HideMenuItems.js, listed below, to ProgramFilesFolder / Adobe / Reader 9.0 / Reader / JavaScripts

Under Shortcuts:

  • Remove the Adobe Reader 9 shortcut added to the Desktop

Under EULA and Document Status set

  • Suppress display of End User License Agreement to enabled

Under Online and Acrobat.com Features set

  • Disable all updates to enabled to disable Adobe Updater
  • When launching PDF in Internet Explorer, prompt user with Open/Save dialog to enabled for Terminal Server environments
  • In Adobe Reader, disable Help > Purchase Adobe Acrobat to enabled
  • Disable Help > Digital Editions to enabled
  • Disable Product Improvement Program to enabled
  • Disable Viewing of PDF with Ads for Adobe PDF to enabled
  • Display PDF in browser to Disable & Lock for Terminal Server environments
  • Disable all Acrobat.Com access, including initiation and participation to enabled

After you created the transform for Reader 9 with the wizard, you may want to open it in your favourite MSI editor to perform further customisations such as disabling SpeedLauncher.

Disabling Menus and Buttons

In a corporate environment, you may want to disable some of the menu items and buttons. Just as in Adobe Reader 8, most of these items are disabled with a JavaScript file. Yes a JavaScript file. Whilst using the registry would make sense to control UI items, Adobe uses JavaScript files. I’d love to know the reason why. It’s not a solution that scales particularly well.

To disable UI elements, you will first need to list all of the elements by name. To do this, save the following script as ListItems.js in %ProgramFiles%\Adobe\Reader 9.0\Reader\JavaScript:

//ListItems.js
//Open Javascript Console
console.show();

//List Toolbar Buttons in the Console
var toolbarItems = app.listToolbarButtons()
for( var i in toolbarItems)
console.println(toolbarItems + "\n")

//List Menu Items in the Console
var menuItems = app.listMenuItems()
for( var i in menuItems)
console.println(menuItems + "\n")

This will open a dialog box when Reader is started, listing the names of each menu item and toolbar button. You can then create a JavaScript file to remove these items from the UI. Reader 9 includes a number of menu items you might want to remove:

MenusHighlighted

Here’s the code you’ll need to hide those items. Copy and paste into HideItems.js, then copy into %ProgramFiles%\Adobe\Reader 9.0\Reader\JavaScripts.

//HideMenu.js

// [File - Create Adobe PDF Using Acrobat.com], plus toolbar button
app.hideMenuItem("WebServices:CreatePDF");
app.hideToolbarButton("Weblink:CreatePDF");

// [File - Collaborate], plus toolbar button
app.hideMenuItem("Annots:FileCollaboration");
app.hideToolbarButton("Annots:CollabToolButton");

// [File - Digital Editions]
app.hideMenuItem("eBook:Digital Edition Services");

// [Help - Improvement Program Options]
app.hideMenuItem("UsageMeasurement");

// [Help - Online Support], plus sub menu items
app.hideMenuItem("OnlineSupport");
app.hideMenuItem("KnowledgeBase");
app.hideMenuItem("AdobeExpertSupport");
app.hideMenuItem("AccessOnline");
app.hideMenuItem("SystemInformation");

// [Help - Repair Adobe Reader Installation]
app.hideMenuItem("DetectAndRepair");

// [Help - Check for Updates]
app.hideMenuItem("Updates");

// [Help - Purchase Adobe Acrobat]
app.hideMenuItem("Weblink:BuyAcrobat");

Deploying Reader

Deploying Reader should be straight-forward, however you are required to complete a distribution agreement to deploy Reader in your environment.

Using Group Policy Software Installation, or your favourite software deployment tool, create a transform file with your required settings and deploy. If you need to use a script, this command will install Reader:

START /WAIT MSIEXEC /I AcroRead.msi ALLUSERS=TRUE TRANSFORMS=AdobeReader9.mst /QB

Updating Reader

Updating Adobe Reader can be a bit of a challenge, especially for smaller environments using only Group Policy Software Installation. For Reader 8, Adobe released updates as a complete download of the installer rather than patches. I recommend updating using the full installer as updates for version 9 are released.

If you would really prefer to use the Updater to keep Reader current, you could use the following command in a task using Windows Task Scheduler:

"%CommonProgramFiles%\Adobe\Updater6\Adobe_Updater.exe" -AU_LAUNCH_MODE=1 -AU_DISPLAY_LANG=en_US -AU_LAUNCH_APPID=reader9rdr-en_US

I can’t vouch for the effectiveness of this approach or even if it will work, so you’re on your own there. Of course you’ll also need to keep Updater in the Reader install package.

Managing Reader

Managing Reader via Group Policy is pretty simple – Reader 8 and 9 are even policy aware. That is they use the Software\Policies key in the registry. Unfortunately Adobe don’t supply an ADM/ADMX template file for use with Group Policy. C’mon Adobe it wouldn’t take you much effort and we would be very grateful.

So it’s Group Policy Preferences or your favourite user workspace management tool for managing Reader. Paul has taken the time to create a simple ADM file for managing some of Readers features that might suit you.

I’ve also created my own custom Administrative template, which you can download in ADM and ADMX format. There is still some work to go on this template, so use at your own risk:

Adobe Acrobat and Reader 9 Administrative Template v0.1

What Now?

I would recommend updating to Reader 9 if you can. There’s doesn’t look to be any fantastic new features to get excited over, but the performance improvements should make it worthwhile.

  • [11/03/2009] Updated for Adobe Reader 9.1
  • [29/07/2008] Adobe have posted a Deploying Adobe Reader 9 document that has some excellent details.
  • [07/08/2008] Updated for the release of Adobe Customisation Wizard 9.
  • [08/08/2008] Added version 0.1 of custom ADM/ADMX for managing policy settings.

{ 6 trackbacks }

{ 74 comments }

1 Shawn Bass July 7, 2008 at 7:18 pm

Good stuff. Thanks for sharing Aaron.

2 Aaron Parker July 7, 2008 at 9:03 pm

Thanks Shawn.

3 Leonard Rosenthol July 8, 2008 at 8:35 am

Removing Sychronizer from the Reader installation will prevent users from participating fully in comment & review, as well as the new ad-hoc forms workflows. We do therefore do NOT recommend removing it.

Leonard Rosenthol
Adobe Systems

4 Aaron Parker July 8, 2008 at 11:01 am

Thanks Leonard. I’ve updated the post and uploaded a new transform that leaves Syncronizer enabled.

5 Paul July 8, 2008 at 3:16 pm

I was testing the upgrade process from 8.1.2 to 9 today and ran in to a problem where the uninstall of 8.1.2 failed preventing 9 from installing.

It seems that the most recent patch for Adobe 8.1.2 has broken the uninstallation if you originally installed using a transform file. So you cannot remove (via Add Remove Programs) or upgrade (via GPO) without manually tweaking a registry key (see link below).

http://www.adobeforums.com/webx?13@@.59b5b203

6 Brett Chapman July 9, 2008 at 4:32 am

Has anyone worked out how to customise the Toolbars either during or post-installation. I know i did it with the V8.x but i think i configured it on the host machine that used the Customisation Tools.
I presume it is a Javascript to do that as well…(sigh) but i must be missing something. Also my script window doesn’t close after running the HideItems script. Any help appreciated

7 Brett Chapman July 9, 2008 at 5:34 am

Wow, Found a rough way of doing it… Good ol Reg Import…
I set up the toolbars, refreshed the view in Regedit and exported the HKLM\Software\Adobe\Acrobat Reader\9.0\AVGeneral\cToolbars key and added it to the install batch file.

as I said, crude, but effective…. Still get the Script Debugger showing the local variables on when opening though…

8 Justin Walker July 9, 2008 at 12:04 pm

Hi

Had a few problems with this, mainly the installer claiming that IE6 or higher was not installed, removed the IsMinIE Rows from the InstallSequence Table and all ok (hack but works)

However have had a problem with 8.12 and now 9 that Icon assoication does not seem to take place, anyone any ideas?

J

9 oscar July 9, 2008 at 9:35 pm

Hi,
I was testing the adm file listed hear on a test machine with a default install of adobe reader 9 upgraded from 8 installed and when I load the adm file I can see custom polices under user/admin templates and adobe acrobat reader, but no settings to adjust under that. If anyone has any corrections for this I would appreshiate hearing about this.

test machine running
xp pro sp3
default adobe reader 9 install

10 Appreciative July 10, 2008 at 7:30 pm

Thank you for this helpful and informative post. I was not able to find the necessary information on Adobe’s site. I could not figure out how to extract the files or create the .MST on my own. You had everything I needed here and I was able to successfully deploy Acrobat Reader 9 via Group Policy to dozens of workstations in just a few clicks.

Yours is a new blog on my list of must reads.

Thanks again!

11 Aaron Parker July 10, 2008 at 9:19 pm

@Justin, I haven’t seen that problem before, I don’t really have an ideas. Have you tried a clean install?

12 Aaron Parker July 10, 2008 at 9:23 pm

@Oscar, you need to enable non managed policies. Right click the Administrative Templates node to change the view options.

13 Aaron Parker July 10, 2008 at 9:24 pm

Thanks for the feedback Appreciative.

14 Justin Walker July 15, 2008 at 9:24 am

Hi Aaron

Tried everything mate, newly built machines, existing machines, if you have adobe installed previously without Group Policy all ok, if however its installed from Group Policy if comes up, almost like its unable to write a registry entry to do with Icon allocation.

J

15 Joe July 17, 2008 at 5:28 am

I’m a little confused as to whether you disabled Synchonizer in the Custom Transform file you posted. Is it disabled permanently? I don’t think many people want this enabled and looks like Abode spying on people with this Synchronizer enabled. I think the default in your Transform file should be to permanently disable this feature.

Having an Adobe person post immediately to recommend enabling Synchronizer seems suspicious as well.

You said:
“Prevent Adobe Synchronizer Installation

* In the Property table, set the value for SYNCHRONIZER to YES”

So is Synchronizer disabled?

16 MEM July 18, 2008 at 2:11 pm

As mentioned, Adobe Customization Wizard (ACW) 8 was released several months after version 8 was released. FYI, in the ACW 8 version, I can’t even open the version 9′s AcroRead.msi so it’s definitely not version-compatible. I could use AdobeReader9.mst file from here, but I want to review/view it first (just to see if I need to add anything more). Aaron, you mentioned Camwood appEditor, but when I looked at the link, there is no “appEditor”, did you mean “appResolver”?

17 Aaron Parker July 19, 2008 at 4:20 pm

@Joe, the Syncronizer is not disabled in the transform I’ve provided. You can disable it if you like, by modifying the PROPERTY table.

18 Aaron Parker July 19, 2008 at 4:36 pm

@MEM, looks like they’ve changed their site a little, you can find AppEditor here: http://appeditor.software.informer.com/. AppEditor will show you the modifications I’ve made to the transform.

19 Matt G July 22, 2008 at 1:17 am

I was wondering if you know how to prevent the “Adobe Product Improvement Program pop-up from launching the first time you load Reader… Will the hidemenu.js file do it? Or is there another way?

Thanks

20 Matt G July 22, 2008 at 2:04 am

Ok never mind I found it myself.
It is

[HKEY_CURRENT_USER\Software\Adobe\CommonFiles\Usage\Reader 9]
“OptIn”=dword:00000000

Thanks

21 patchm00 July 22, 2008 at 8:35 pm

I downloaded and tried your mst but updates were still checked under edit/preferences/General, however when I run help/check for updates no window pops up.

22 Matt July 23, 2008 at 3:29 pm

Has anyone looked into the memory requirements of version 9? I see an initial memory grab of some 24MB if you minimise it will dop to about 2MB and restoring will bring the memory back up to just under 5MB. I have also noted that the memory usage increases even when leaving the reader open in the foreground with no pdf.

23 cv July 26, 2008 at 3:16 pm

Thanks for the post. Very informative.

Where do we set the property for the serial number as I have the pro version?

Also will this mst work ok with pro?

24 Aaron Parker July 26, 2008 at 7:50 pm

@cv, the transform I’ve got here won’t work for Acrobat Pro, but you could use the same process for creating your own transform.

25 cv July 28, 2008 at 2:29 am

Thanks. Do you know the properties for the serial info?

26 Donald Swentik July 28, 2008 at 3:37 pm

To remove the Adobe Product Improvement Program pop-up.

Remove the references to _Registry_UsageTracking from the MSI file

27 Donald Swentik July 28, 2008 at 4:40 pm

Previous comment was premature…it does not get rid of the pop-up

28 Aaron Parker July 29, 2008 at 10:46 am

@cv, I haven’t looked at the Acrobat Pro MSI, but open it up with your favourite MSI editor and look at the PROPERTY table.

29 Mike August 1, 2008 at 10:47 pm

I am trying to create a Bat file for the install to run silent. I have added reg keys to disable the Updates. I can not figure out what I need to do to disable the EULA from displaying and having my users receive the agreement window. Any ideas? Mikep888@yahoo.com
Thanks,

30 Aaron Parker August 2, 2008 at 11:40 am

Add EULA_ACCEPT=YES to the command line

31 Kym Charlesworth August 2, 2008 at 1:46 pm

I wouldn’t deploy AR9 into any active directory environment using folder redirection of Application Data to a UNC path. AR9 has a bug wrt this circumstance and will crash with a Microsoft Visual C++ Runtime Library error upon opening. Refer to the Adobe reader forum for details. Adobe do not have a time frame on when this will be fixed as of 2.8.08.

32 James August 4, 2008 at 8:51 pm

stealthpuppy… your blog is indispensible. Thank you.

33 Aras Memisyazici August 5, 2008 at 9:06 pm

stealthpuppy you RULE my friend! And thx to “Matt G” as well for the invaluable tip on registry patching for the improvement msg to go away. Thx to you guys I just deployed Rdr 9 to my entire org. via our SMS-like system in no time :D

Thx again!

34 Kym Charlesworth August 6, 2008 at 11:03 am

Matt G is correct but better to use Orca (or an equiv msi editor), apply Aaron’s transform, do a search on Usage and drop those rows (don’t drop the hit found in the EULA) and save the transform. The usage component of AR9 then gets omitted altogether.

35 Sol August 6, 2008 at 1:15 pm

@Matt G
This only seems to work if you open up Adobe Reader manually after installation, before opening PDF’s. If you open PDF’s right away, the settings will not apply.

When packaged and compiled in WISE, it places the HKCU keys in the HKEY USERS > .DEFAULT, and copies the settings over once Adobe Reader is opened in a specific profile. It’s implied that most users will not open Adobe Reader manually, so these settings may never take effect and the Improvement Program window will eventually appear after opening a few PDF’s.

I’m still trying to figure this out. Why Adobe made this feature so hard to remove is beyond me.

36 Paul August 7, 2008 at 9:11 am
37 Alexandre August 8, 2008 at 12:59 pm

Hi, I extracted the msi file and edited it with Adobe Customization Wizard 9 and that created a .mst file. I want to install in silent mode in order to deploy my package with a GPO. However when I double click on the .msi the GUI is displayed.
What should I do?

38 Jonathan August 13, 2008 at 3:15 pm

I noticed that they changed the “Help” system in version Reader 9 so it now opens a browser versus an integrated help system. Being that I am installing on a Terminal Server nearly the last thing I need is an application opening up a browser. I have successfully hidden the Help Menu option but it’s common knowledge that hitting F1 on the keyboard opens help…and in Reader 9′s case…IE.

Any suggestions on how to “De-link” Reader 9 from opening the browser?

39 Aaron Parker August 13, 2008 at 5:09 pm

@Alexandre, double clicking the MSI won’t automatically apply the transform. On a command line you would need to run something like this:
MSIEXEC /I AcroRd32.MSI TRANSFORMS=AdobeReader9.MST

When deploying via Group Policy, add the transform when importing the application into the Software Installation component of the GPO.

40 Aaron Parker August 13, 2008 at 5:10 pm

@Jonathan, obviously I don’t have any experience with your environment, but what’s the issue with Reader opening a browser window?

41 Jonathan August 14, 2008 at 5:34 pm

We don’t allow any internet surfing from our Terminal Servers and Adobe.com is a uncontrolled site…they could have links to anywhere on there.

42 Aaron Parker August 14, 2008 at 7:35 pm

I would consider the task of controlling access to the browser the task of something like Software Restriction Policy, or the task of controlling the Internet access the task of a proxy server that denies access to the Internet from the IP addresses of your Terminal Servers.

43 Jonathan August 14, 2008 at 7:59 pm

We publish several Intranet webpages as applications to 1000s of users so we cannot prevent the use of the Browser using the restriction policy.

We also require internet access from time to time from the Terminal Servers for one reason or another but I should really reconsider the necessity of that.

What we have found that works well is restricting “Access” to the browser. If a user cannot get to a browser then they cannot access the internet.

I know what you are thinking now…but if you publish the Browser for Intranet applications can’t the users just use that to surf the Internet? No, they can’t.

What we have done is created Softgrd sequenced applications with a bogus Proxy Server, hidden address bar, hidden menu bar, etc…essentially a browser shell. We add an exclusion for the Intranet page we are allowing with this Sequence in the bypass proxy for this address section in IE. What this allows us to do is limit access to the Intranet Site only no matter what the content is on that site (since we don’t control that either…someone could put a link to UPS.com and we wouldnt know).

So, why can’t we do that for Reader? We install it locally..if we did Sequence it I would have never asked the question as all I would have done was add a bogus proxy server to the sequence with no exceptions (which is what we do now to almost all applications as we don’t know what application developers have put in their apps that may link out to the internet).

44 Jeffrey Johnson August 19, 2008 at 6:47 am

I cannot open Adobe Reader 9 without Windows Vista giving me a runtime error. What do I need to download to fix this problem?Thanks

45 Aaron Parker August 19, 2008 at 9:49 am

Hi Jeffery, have you attempted to uninstall and then reinstall Reader?

46 Dave August 20, 2008 at 2:18 pm

the second and third times you mention
%ProgramFiles%\Adobe\Reader 9.0\Reader\JavaScripts
above, you write
%ProgramFiles%\Adobe\Reader 9.0\Reader\JavaScript
(missing “s”)

47 Paul August 22, 2008 at 6:10 am

Aaron, I’ve included this page as an MHT as well as your ADM template in our toolkit. Hope thats okay.

48 Alexandre August 25, 2008 at 1:02 pm

Hi Aaron. Thank you for your answer, I found how to add the transform file in the GPO and the application is deploying fine.

The only remaining problem is the following:
The option “Display PDF in Browser” is enabled into the Adobe Customization Wizard but when I try to open PDF file in the browser I’ve got a message that says it’s not possible to open it in the browser… Any idea ?

49 aweheckman September 24, 2008 at 3:09 pm

Hi Aaron,
When you wrote
“Under Files and Folders:
Add HideMenuItems.js, listed below, to ProgramFilesFolder / Adobe / Reader 9.0 / Reader / JavaScripts” is this the script HideItems.js? or where to I get the HideItems.js script from?

50 Aaron Parker September 24, 2008 at 3:21 pm

@aweheckman, the code listing for HideItems.js should be under the text “JavaScript to Hide UI Elements” which you may have to clikc to show it.

If you still can’t see the listing I can e-mail it to you.

Comments on this entry are closed.

Previous post:

Next post: