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\AdobeUpdater\6 (32-bit Windows)
  • C:\Program Files (x86)\Common Files\AdobeUpdater\6 (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%AdobeReader 9.1Setup Files (on Windows Vista/2008)
  • %USERPROFILE%Local SettingsApplication DataAdobeReader 9.1Setup 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%AdobeReader 9.0ReaderJavaScript:

//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:

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

//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%\AdobeUpdater\6\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 SoftwarePolicies 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.