1 HOME


© 2013 Adobe Systems, Inc. All rights reserved.

Updated Aug 12, 2014.

2   Administration Basics

2.1   Installation best practices

  • Start with a fresh set of files.

  • Accept the Reader Distribution Agreement.

  • On Windows:

    • Create an MST file or make changes on the command line.
    • Set the file’s read-only attribute on a vendor MSI for which you’re creating a transform.
    • Save your MST in case you need to upgrade with a full installer (MSI or EXE) which would uninstall the existing Reader installation and remove your customizations.
  • If there is a problem, patch on a virgin copy of the original files as a test.

  • Before updating, verify what’s already installed.

  • Know the supported update orders.

  • When installing a product of one type over another type (e.g. Acrobat Pro Extended on machines where Acrobat Standard is already installed), always uninstall the other product first. Do not rely on MSI parameters such as REINSTALLMODE=amus to do the work for you.

  • Develop a pre-deployment configuration plan. Know what settings, files, and functionality you need to support or block.

  • Know the product end of life schedule: The schedule is set several years in advance as described at http://www.adobe.com/support/products/enterprise/eol/eol_matrix.html#86.

2.1.1   Back up the original files

Adobe recommends that you back up all files and use MST files or the command line to modify the installer rather than editing the original download directly. Doing so lets you maintain access to a supported and tested configuration (the default). If you are doing a chained installation, the archive folder should contain the major release installer and the requisite update files. For example:

  • 10.x and later products offer cumulative installers (quarterly installers are cumulative to the last MSI and patches are cumulative to the last quarterly. Thus, for an upgrade to 10.1, the folder would contain:

    • The base install from the CD installer, the unpacked download from the Reader Download center, or download from the enterprise FTP site.
    • The 10.1 update. (note you do not need 10.0.1, 10.0.2, or 10.0.3).
  • If installing 9.0 and the 9.1 and 9.1.2 updates and patches, the folder would contain:

    • The base install from the CD installer, the unpacked download from the Reader Download center, or download from the enterprise FTP site.
    • AcroProStdUpd910_T1T2_incr.msp (for example, 910 MSP update files for tier 1 & 2 languages).
    • AcrobatUpd912_all_incr.msp (912 MSP update file).

2.2   Supported workflows

2.2.1   Windows

  1. Download the requisite installer(s).

  2. Optional: Modify the installer and the installed product. If you create an MST, save it for future use. You’ll need to apply it again for Reader MSI installs which uninstall the previous version (and therefore destroy your custom settings).

  3. Determine your installation workflow:

    • Administrative (full-file) updates: Full file updates are patch administrative installation points (AIP) or clients directly from expanded installer files residing on a network share.
    • Client (binary) updates. These patch existing files using the bootstrapper setup.exe. Client updates are designed only for individual machines and cannot be used to update an AIP.
  4. Set MSI and Adobe properties as needed to perform the actual install as follows:

    • If you’re using the MSI installer, configure abcpy.ini.
    • If you’re using the Setup.exe bootstrapper installer, configure setup.ini.
    • On your command line, you can use msiexec and Adobe properties and switches.
  5. Deploy.

Deployment overview

_images/installworkflow.png

2.2.2   Macintosh

Adobe now introduced with 10.x kproducts an installer for the Macintosh platform and support for Apple Remote Desktop (ARD). Unlike previous product versions which required manual installs, product installation and some configuration can be automatically managed for enterprise deployments. At a high level, deployment involves:

  1. Download the requisite installer(s). Links to information about installers and sequencing reside at http://www.adobe.com/go/acro_releasenotes.

  2. For batch preserialization, EULA suppression, etc., download the Adobe Provisioning Tool from:

  3. Use ARD to deploy the application.

2.3   Enterprise vs. end user

2.3.1   Enterprise installers

Adobe provides enterprise IT with a download site that contains all available installers. Most admins download the product, updates, and patches from ftp://ftp.adobe.com/pub/adobe/reader/ (or Acrobat). This FTP site provides the following:

  • An archive of all currently supported binaries for all products, versions, updates, and patches.
  • Deprecated application versions which are no longer supported.
  • Vanilla installers without additional components. For example, 9.x installers on the FTP site do not include the Adobe Air runtime (9.x).

2.3.2   End user installers

End users typically download installers from the Reader Download Center (RDC) at http://get.adobe.com/reader/.

As of July 13, 2010, Reader downloads include a chained installer that includes all requisite patches and updates. Prior to July, 2010, product downloads from the download center only included the original major release version of the product such as 8.0 and 9.0. These older installers did not include the latest patches and thereby created two problems:

  • Users would have to apply the latest updates and patches to get to the latest version.
  • The product was less secure and subject to known vulnerabilities if it was not patched.

To resolve these issues, the download center now only provides chained installers that include all the updates in one bundle. This delivers a single install to get the latest product version.

2.4   Expanding EXE packages

These steps apply to EXE installers, including those downloaded from the Reader Download Center, the FTP site, or Adobes LWS site.

Note

If you are using SMS (not officially supported since 9.0) and do not need to customize the installer, you can use the Nosso-compressed file directly with the SMS installer.

  1. Open a command prompt.
  2. Expand the MSI package with a set of command line switches. The general form of the command to convert a Nosso-compressed file to an MSI package is:
<user-specified installation path>\AdbeRdr<version>_<locale code>.exe
[<Nosso, 7-zip, or Adobe switches>...]

Note

For example, the following command specifies that no files are to be executed after the expansion or installation, and the resulting files are to be placed in a folder named “Reader9”:

<user-specified installation path>\AdbeRdr90_en_US.exe
-nos_o"MyFolder" -nos_ne

Note

Do not use an existing directory, and do not leave any spaces after -nos_o or -sfx_o command. Note that the compression technology changed from Nosso to 7-zip with 10.0.

The command in specifies that no files are to be executed after extracting Reader 9.0 files. The installer will not run after expanding the files to a directory named “Reader9”.

Expanding EXEs: Nosso compressed

<user-specified installation path>\AdbeRdr90_en_US.exe
-nos_o"MyFolder" -nos_ne

The command in specifies that no files are to be executed after extracting Reader 10.0.1 files. The installer will not run after expanding the files to a directory named “Extract”.

Expanding EXEs: 7-zip compressed

AdbeRdr1001_en_US.exe -sfx_ne -sfx_o"<some path>\Extract
Switches for expanding the Nosso installer
Nosso switch (9.x) 7-zip switch (10.x) Description
-nos_ne -sfx_ne Do not execute any file after installation (overrides the -e switch) This switch should be used if user only wants to extract the installer contents and not run the installer.
-nos_nd -sfx_nd Do not delete files after installation (overrides the -r switch) The -r switch uses the existing folder and overwrites the extraction files to the same folder without creating an additional extraction folder.
-nos_o -sfx_o Specifies the name of folder where the contents of the expanded package are to be placed. The folder name should be enclosed in quotation marks. It is best if you do not use an existing folder, and there should be no space following the -nos_o. For example: <path>\AdbeRdr90_en_US.exe -nos_o"TestFolder" -nos_ne. The default output folder is %TEMPDIR%/Adobe <Productname>.
  -sfx_va Validates the decompression of the deliverables.

2.5   Versioning policy

Adobe uses version numbers to clearly communicate to IT professionals the deployment model for a given release.

Acrobat and Reader version numbers contain 3 integers and two dots:

  • The first integer identifies the major release; for example, 9.0.0, 10.0.0, or 11.0.0 (sometimes XX.0 for short).
  • The second integer is incremented when a quarterly update is delivered as a full installer; for example, 9.1.0, 9.2.0, and 10.1.0. These always include previously released out of cycle patches.
  • The third integer is incremented for all other updates and out of cycle patches; for example, 9.4.3, 9.4.4, 10.0.1, 10.0.2, etc. Note that 11.0 products use the format: 11.x.xx (with two integers identifying minor updates starting with 01).

Updating Acrobat is straightforward because all update types are incremental and every one must be installed in order. For Reader, however, use the version number and file type to determine your update strategy. For a list of installer types see the release notes 10.x and 11.x | 8.x and 9.x.

2.6   Installer file types

New and existing installations may work with one or more of the following file types.

  • Windows

    • MSI: A full installer. Only the Acrobat base install is ever an MSI. For Reader, MSI’s may occasionally be released when the second dot number is incremented (e.g. 10.0 > 10.1).
    • EXE: A full installer. Only the Acrobat base install is ever an EXE. For Reader, EXE’s may occasionally be released when the second dot number is incremented (e.g. 10.0 > 10.1), but they are often available for quarterly releases of tier 1 languages.
    • MSP: An incremental patch installer.
    • MST: MST files are used for a Microsoft Windows Installer transform. The file can perform transforms, adds, deletes, or change properties in a Microsoft Windows Installer (.MSI) package to enable customization of the installation for different groups of users. If you’re using the Customization Wizard, you’ll create an MST file that is applied to the original MSI file.
  • Macintosh

    • PKG: Includes both full and update installers. The download is a DMG file.

2.7   Naming conventions

Installer names have several components that help identify what it contains:

_images/installer_naming.png
Installer naming conventions
OS Name Description
All Tier_# 10.x and later. The language group. For example, Tier_1 is English, French, German, and Japanese.
All _cum A full installer for a MUI version.
All _all All languages are supported: used for some MSP patches.
All T1T2 An older language ID used by 9.1 and 8.1 and earlier.
All _en_US A language ID; in this example, English.
Mac _i386 Identifies installers for Apple products that use Intel’s 32 bit i386 CPU.
Mac _ppc Identifies installers for Apple products use PowerPC CPUs.
Mac .pkg The uncompressed installer file.
Mac .dmg The compressed installer that contains the PKG file.
Win .msp A non-full installer: can be a quarterly update or out of cycle patch.
Win .msi A full installer that includes all previous releases.
Win .exe A full installer; not typically used in enterprise settings.
Win _mui An installer that supports a multilanguage selection user interface. MUI updates always roll back to the base release and patch over it.

2.8   Installer languages

Installers may or may not be language-specific. There are three types:

  • Language specific installers: These are identified by a language code in the installer’s file name.
  • Language agnostic installers: These don’t have a language code in the installer’s file name. Most patches and updates are language agnostic and can be applied to whatever language-specific install is already present. In these cases, language selection is not pertinent and update is simply applied in the language that has been selected during original installation.
  • MUI installers: These are identified by _mui in the file name. They contain all supported languages and the admin pre configures the language or the end user select the desired language at install time.

Note

All Acrobat 11.0 installers are MUI installers. Because every installer includes all language files, there are no longer separate installers for specific languages. 11.0 ships 1 installer for Professional and Standard for Windows and Mac, thereby reducing the number of installers from dozens to a few.

2.8.1   Language tiers

Tier information does not apply to MUI installers which support all languages. All Acrobat 11.0 installers are MUI installers.

Beginning with the first 10.0 update, installers may be named by the language group (or tier). To identify the available language, refer to the release notes or Table 2 below. For example, the 10.0.1 update is named as follows:

  • Windows: Acrobat Upd1001_Tier_1.msp. Tier 1 indicates the installer is for English, French, German, and Japanese.
  • Macintosh: AdbeRdrUpd10 01.dmg. The absence of the a tier identifier indicates the installer is generic and should be used for updating any language version.

Most planned updates and out of cycle updates (and any Acrobat update/patch) are language agnostic and can be applied over any product. For Reader, language-specific installers may be provided from the Reader Download Center at http://get.adobe.com/reader/ and the ftp site for some Planned updates. In those cases, use the installer file name to identify the language for which the installer is intended.

Multilanguage (MUI) installers: Some releases include MUI installers that provide support for multiple languages and allow the user to configure the language at install time. These are only available on Windows and are identified by _MUI in the filename. All Acrobat 11.0 installers are MUI installers.

2.8.2   11.x language support

Tier 1
Language Name Locale SKU abbreviation Comments
Universal English en_US UE All products
French fr_FR F All products
German de_DE D All products
Japanese ja_JP JPL All products
French Canadian fr_CA FC Mapped to fr_FR
International English en_GB EAP, EUE, EUW, IE, LAE Mapped to en_US
Tier 2
Language Name Locale SKU abbreviation Comments
Dutch nl_NL NL All products
Italian it_IT I All products
Spanish es_ES E All products
Latin/North American Spanish es_MX LAS, NAS mapped to es_ES
Brazilian Portuguese pt_BR PB All products
Portuguese pt_PT P mapped to pt_BR
Swedish sv_SE S All products
Danish da_DK DK All products
Finnish fi_FI SF All products
Norwegian nb_NO N All products
Tier 3
Language Name Locale SKU abbreviation Comments
Chinese Simplified zh_CN CS All products
Chinese Traditional zh_TW CT All products
Korean kr_KR KOR All products
Tier 4
Language Name Locale SKU abbreviation Comments
Czech cs_CZ CZ All products
Hungarian ht_HU HU All products
Polish pl_PL PL All products
Russian ru_RU RU All products
Ukrainian uk_UA UKR All products
Turkish tr_TR TR All products
Slovak sk_SK SL Windows only
Slovenian sl_SI SVN Windows only
Basque eu_ES none Windows Reader only
Catalan ca_ES none Windows Reader only
Croatian hr_HR none Windows Reader only
Romanian ro_RO none Mac and Windows, Reader only
Tier 5
Language Name Locale SKU abbreviation Comments
North African French fr_MA NAF All products (no locale for Mac since the UI appears in the OS locale)
Middle Eastern English for Arabic en_AE MEA All products (no locale for Mac since the UI appears in the OS locale)
Middle Eastern English for Hebrew en_IL MEH All products (no locale for Mac since the UI appears in the OS locale)

2.8.3   10.x language support

Language support for 10.x
Tier Windows Macintosh
Tier 1 English, French, German, Japanese English, French, German, Japanese
Tier 2 Italian, Spanish, Dutch, Brazilian Portuguese, Swedish, Danish, Finnish, Norwegian Italian, Spanish, Dutch, Brazilian Portuguese, Swedish, Danish, Finnish, Norwegian
Tier 3 Chinese Traditional, Chinese Simplified, Korean Chinese Traditional, Chinese Simplified, Korean
Tier 4 Russian, Ukrainian, Romanian, Turkish, Czech, Hungarian, Polish, Slovak, Croatian, Slovenian, (Reader only: Catalan, Basque) Russian, Ukrainian, Romanian, Turkish, Czech, Hungarian, Polish
Tier 5 Greek, Arabic, and Hebrew Greek, Arabic, and Hebrew

2.8.4   Locale and language codes

Installer filenames include a locale identifier consisting of consists of a language code and a country code. For example, the Reader installer filename is in the form of AdbeRdr<version>_<language code>.exe. Thus, AdbeRdr10_en_US.exe is an English installer.

Note

Details about what languages are supported in each release appear in the Release Notes.

Installer components and workflows adhere to the ID system used by Microsoft. For details, see:

These IDs are also used on the command line, in installer tables, and elsewhere.

Locale and language codes
Language Code Language ID code
Basque eu 1069
Bulgarian bg 1026
Catalan ca 1027
Chinese (China) zh_CN 2052
Chinese (Taiwan) zh_TW 1028
Croatian hr 1050
Czech cs 1029
Danish da_DK 1030
Dutch nl_NL 1043
English en_US 1033
Estonian et 1061
Finnish fi_FI 1035
French fr_FR 1036
German de_DE 1031
Hungarian hu 1038
Italian it_IT 1040
Japanese ja_JP 1041
Korean ko_KR 1042
Latvian lv 1062
Lithuanian lt 1063
Norwegian nb_NO 1044
Portuguese – Brazilian pt_BR 1046
Romanian ro 1048
Russian ru 1049
Slovak sk 1051
Slovenian sl 1060
Spanish es_ES 1034
Swedish sv_SE 1053
Turkish tr 1055
Ukrainian uk 1058
English with Arabic en_AE 1025
English with Hebrew en_IL 1037
North African French fr_MA 6165
Polish pl_PL 1045

2.8.5   Machine-level details

The application language is selected at the time of installing the initial major version using Setup.exe. The language selected at that time is stored on the system. For example, on Windows, it’s in:

[HKEY_CURRENT_USER\Software\Adobe\<product name>\<version>\Language]"UI"="ENU"

The product UI language is actually determined by the sidecar dll stored in:

[HKEY_CURRENT_USER\Software\Adobe\<product name>\<version>\Language]"current"

Therefore, if a user switches the dll under current or changes the UI key the two keys may not match. Ultimately, the dll under current determines the product language.

Note that Adobe uses standard MSI technology for installation on Windows, so patches and updates are language agnostic and they are applied to whatever language-specific install is already present. Therefore, application language selection is not pertinent to updates: Patches are simply applied in the language that has been selected during original installation.

2.9   Multilanguage installers

Multilanguage (MUI) installers provide a way to install the product with support for more than one language. Features include:

  • Support for more than one language so that users can switch languages.

  • Automatic selection of the language based on the language of the current OS.

  • 11.0 introduces a MUI installer for Acrobat on both Windows and Macintosh which provide the following benefits to enterprise IT and OEM vendors:

    • A reduction in the number of Acrobat installers from twenty to two (1 each for Pro and Standard).
    • For those supporting multiple locales, one or two downloads (as opposed to up to 20) and a simpler patching and update workflow.
    • Smaller patch sizes. In 10.0 and earlier, Acrobat patches needed to provide separate files for 20 installers. 11.0 and later MUI installers use fewer files.
    • Simplified licensing: Both Windows and Macintosh use a limited number of serial number types to specify the product language.

The base installer is an MSI file, and MSP patches are also periodically released which can only be applied over the base mui MSI install. Both installers are identified by “_mui” in the filename.

Note

MUI installers are only created in tandem with full MSI installers. They are not created for MSP updates and patches. For example, 10.0 and 10.1 include MUI installers while 10.0.1, 10.0.2, and 10.0.3 do not. What this means for your deployment methodology is that you simply install the generic installer over your MUI install if there is a no MUI-specific installer. If there is a MUI-specific installer, you must use that. Download the MUI installer from ftp.adobe.com/pub/adobe/reader/.

The MUI Reader always contains the base English resources. To support another language, an additional resource bundle is added to the installation. Therefore, English is always present, and the single language Reader is about the same size as the MUI Reader.

The installation size varies with the type of install:

  • Bootstrapper (setup.exe) or UI-based installer: The size is significantly larger than the single language version because the full installer is kept on the disk.
  • AIP install: Except for minor differences in some of the text files, the size of the MUI Reader will be about the same as the single language Reader.

2.9.1   Windows MUI installers

Windows MUI installers for Acrobat behave as follows:

  • All serial numbers are language based.

  • There are two types of serial numbers: one for all languages and one for a single language.

  • The installer gets the language attributes from serial number.

  • English is always installed in addition to any specified locale.

  • End user installs with a retail non-MUL serial number do not provide additional language options at install time.

  • Language specification occurs as follows:

    • An “all language” serial number installs Acrobat in the OS language (Typical Installation).
    • A “single language” serial number installs Acrobat in the specified language.
    • End users can choose any combination of languages to be installed via a custom installation.
    • End users will be able to install one or more languages via Installer Repair/Modify option.
    • The LANG_LIST property can be used for command line installs.

2.9.2   Macintosh MUI installers

Since there is no Acrobat Standard for Macintosh, there is a single MUI installer which behaves as follows:

  • All serial numbers are language independent.
  • All languages will be installed by default.
  • The OS language will determine the language in which Acrobat will be launched.

The serial number is read by the application at launch time, and the OS locale controls which language the application should load. Trials are available all supported languages, although only a single trial language can be installed at any point of time.

2.10   Update rules and constraints

The version number indicates the number of releases that have been issued since your last install and what type of file and chaining workflow to use when updating Reader. For example, some quarterly installers where the second number increments are full installers which can be applied over the base release.

Details about each updates bug fixes, features, changes, file sizes, and so on can be found at the following in the release notes:

Note

Attempting to update in an unsupported order results in a failure that serves to prevent the use of updates that Adobe does not recommend.

2.10.1   10.x-11.x Acrobat updates

To get to the latest version, non-AIP installations should use this order: Base release > latest quarterly > latest security update.

Note

Installing the latest version always gets you the most functional and secure version. However, you should develop an update plan appropriate for your deployment methodology and business requirements.

Tips, tricks, and gotchas

  • Patch and update installers are always MSPs.
  • Quarterly updates are cumulative to the base release and security patches are cumulative to the last quarterly. Thus, quarterlies always include all previously released out of cycle security patches.
  • You cannot rollback updates.
  • In AIP workflows, you cannot apply quarterly updates over a non-10.0 install: e.g. 10.1 over 10.0.1|2|3. AIP workflows are subject to constraints that don’t apply to bootstrapper workflows. Always archive your AIPs so you can restore to a previous version in case such a psuedo-rollback is required (uninstalling and starting over). While you can use the vomus switches to apply updates to end user machines directly, future installs via an AIP will require uninstalling and starting over with a new AIP.
  • In Bootstrapper workflows, install everything in order.
  • Save your MST for future use.

2.10.2   10.x-11.x Reader updates

To get to the lasted version, install the product in this order: Latest MSI > latest quarterly > latest security update.

Note

Installing the latest version always gets you the most functional and secure version. However, you should develop an update plan appropriate for your deployment methodology and business requirements.

Tips, tricks, and gotchas

  • Installers can be MSIs or MSPs. MSI’s uninstall the product, so save your MST to reuse your customizations for future installs.
  • Quarterly updates are cumulative to the latest MSI (e.g. 10.1 replaces the base release of 10.0) and security patches are cumulative to the last quarterly. Thus, start with the latest MSI and add the latest MSPs.
  • Quarterlies always include all previously released out of cycle security patches.
  • You cannot rollback updates, so archive your AIPs in case you need to uninstall with /x <guid> and reinstall an earlier version. This may be required in those cases where workflows break due to changes in the product or bugs.
  • In AIP workflows, you cannot apply quarterly updates over a previous quarterly or security patch: e.g. 10.1 over 10.0.1|2|3. AIP workflows are subject to constraints that don’t apply to bootstrapper workflows. Always archive your AIPs so you can restore to a previous version in case such a psuedo-rollback is required (uninstalling and starting over). While you can use the vomus switches to apply updates to end user machines directly, future installs via an AIP will require uninstalling and starting over with a new AIP.
  • In Bootstrapper workflows, install everything in order.
  • Save your MST for future use.

2.10.3   8.x-9x Acrobat updates

To get to the lasted version, install the product in this order: Base release > all the quarterlies > latest security update.

Tips, tricks, and gotchas

  • Installers are always MSPs.
  • Start with the latest MSI (e.g. 9.3 replaces the base release of 9.0)
  • Install all the MSP quarterlies in order. These include interim security updates. In other words, quarterly updates include the most recent out of cycle patches. You do not need to apply any out of cycle patches if you are applying a more recent quarterly update.
  • Install the latest MSP out of cycle patches. Do not apply a quarterly updates to an AIP in which an out of cycle patch was the most recently applied update. To deploy a new, full quarterly update from an AIP, create a new AIP.
  • You cannot rollback updates, so archive your AIPs in case you need to uninstall with /x <guid> and reinstall an earlier version. This may be required in those cases where workflows break due to changes in the product or bugs.
  • In AIP workflows, you cannot apply quarterly updates over a previous security patch. AIP workflows are subject to constraints that don’t apply to bootstrapper workflows. Always archive your AIPs so you can restore to a previous version in case such a psuedo-rollback is required (uninstalling and starting over). While you can use the vomus switches to apply updates to end user machines directly, future installs via an AIP will require uninstalling and starting over with a new AIP.
  • In Bootstrapper workflows, install everything in order.
  • Save your MST for future use.

2.10.4   8.x-9x Reader updates

To get to the lasted version, install the product in this order: Latest MSI > all the latest quarterlies > latest security update.

Tips, tricks, and gotchas

  • Installers can be MSIs or MSPs. MSI’s uninstall the product, so save your MST to reuse your customizations for future installs.
  • Start with the latest MSI (e.g. 9.3 replaces the base release of 9.0)
  • Install all the MSP quarterlies in order. These include interim security updates. In other words, quarterly updates include the most recent out of cycle patches. You do not need to apply any out of cycle patches if you are applying a more recent quarterly update.
  • Install the latest MSP out of cycle patches. Do not apply a quarterly updates to an AIP in which an out of cycle patch was the most recently applied update. To deploy a new, full quarterly update from an AIP, create a new AIP.
  • You cannot rollback updates, so archive your AIPs in case you need to uninstall with /x <guid> and reinstall an earlier version. This may be required in those cases where workflows break due to changes in the product or bugs.
  • In AIP workflows, you cannot apply quarterly updates over a previous security patch. AIP workflows are subject to constraints that don’t apply to bootstrapper workflows. Always archive your AIPs so you can restore to a previous version in case such a psuedo-rollback is required (uninstalling and starting over). While you can use the vomus switches to apply updates to end user machines directly, future installs via an AIP will require uninstalling and starting over with a new AIP.
  • In Bootstrapper workflows, install everything in order.
  • Save your MST for future use.

2.11   Reader distribution

Distributing Reader requires signing a distribution agreement. Acrobat deployments require a license.

To distribute Adobe Reader on a CD, with a computer product, or within your enterprise, you must

  1. Go to http://www.adobe.com/products/reader/rdr_distribution1.html.
  2. Choose Apply to distribute Reader.
  3. Read the information on the page and fill out the required information.
  4. Fill out the form and choose Accept and Submit. After responding, you will be notified within two days whether your application has been accepted or denied.
  5. Your confirmation e-mail will contain a link for the Reader download. The license agreement is good for one download. The license agreement is good for one year, and you will receive a reminder by e-mail in advance of the expiration date.

Note

For details about Acrobat installations, see 4   Installation Workflows.