If you’re installing the latest “DC” products, please see Document Cloud Product Tracks.
For 11.x and earlier, admins license and activate the product prior to deployment. DC products provide the additional option of named user deployments. Support for enterprise and federated IDs as well as the ability to manage usage rights via the Enterprise Dashboard provides admins with new tools for managing software, users, and devices. For a comparison of the two entitlement types, see Document Cloud Product Tracks.
The Adobe Enterprise Dashboard provides a central location for managing your Adobe entitlements, including specific users and groups, across your entire organization. The dashboard allows you to manage licenses for users and groups for all Adobe products. For more information, see:
Start with a fresh set of files.
Accept the Reader Distribution Agreement.
- 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 a virgin copy of the original files as a test.
Before updating, verify what’s already installed. Two versions of Acrobat or two versions of Reader cannot coexist. It is possible to have different versions of Acrobat and Reader on the same machine.
Know the supported update order:
- DC products: All updates, including out of cycle patches, are cumulative to the base release. Chaining updates is never required.
- 11.x and earlier: The update order is the last base installer (exe or msi) + last quarterly + last security patch (if any).
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.
Adopt an update strategy. Many admins disable updates to control deployments. If you can, leave updates set to install automatically.
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.
Back up the original files. Do not modify the original download. 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 a copy of the original installation media as well as the 10.1 update.
- Older installers are not cumulative. For example, if installing 9.0 and the 9.1 and 9.1.2 updates and patches, the folder would contain the original installation media as well as all required updates.
Read the release notes. These provide links to installers as well as details about new features and bugs.
Download the requisite installer(s).
Preconfigure the installer. Options include:
- Windows: Customization Wizard and manual registry modification
- Macintosh: Customization Wizard and manual plist modification
Set cmd line properties as needed to perform the actual install:
- 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.
- Use the Adobe Provisioning Tool to set properties for preserialization, EULA suppression, etc.
Deploy according to the recommendations in this guide.
DC products provide two tracks. “2015” installers are typically deployed by enterprise while “DC” installers are usually installed by end users. However, this method is not a requirement.
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:
If you need to perform additional authenticity checks other than getting your download from adobe.com or ftp://ftp.adobe.com/pub, check the installer’s signature using third party tools.
You can also view the certificate, the counter signer’s certificate, and the certificate chain to the trust anchor for both.
If you download from Adobe’s download center, Adobe’s download manager downloads the bits. Once you mount the
dmg, verify its signature using the codesign tool:
$ codesign -vvv /Volumes/Adobe\ Reader\ Installer/Install\ Adobe\ Reader.app
To check a
pkg which has been extracted from a
$ pkgutil --check-signature Adobe\ Reader\ XI\ Installer.pkg or pkgutil --check-signature AdbeRdrUpd11009.pkg
These steps apply to EXE installers, including those downloaded from the Reader Download Center, the FTP site, or Adobe’s LWS site. Note the following:
To expand an EXE:
<path>\<product_name>.exe <Nosso, 7-zip, or Adobe switches>...]
For example, the following command specifies that the EXE file is not executed after file extraction (the installer doesn’t run). The files are placed in a directory called “MyFolder”.
<path>\Acrobat_2015_Web_WWMUI.exe -nos_o"MyFolder" -nos_ne
Do not use the current directory, and do not leave any spaces after
The following example expands Reader DC using the format
<path>\AdobeReaderEXE> -sfx_nu /sALL /msi <Any MSI parameter>.
AcroRdr20151500630032_MUI.exe -sfx_nu /sALL /msi EULA_ACCEPT=YES
Expanding Nosso compressed EXE
<path>\Acrobat_2015_Web_WWMUI.exe -nos_o"MyFolder" -nos_ne
Expanding 7-zip compressed EXE
AdbeRdr1001_en_US.exe -sfx_ne -sfx_o"<some path>\MyFolder"
|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_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
|-sfx_nu||Silently extracts the installation files from the EXE.|
DC track release schedules and their respective versions will be different, but both the Continuous and Classic tracks share an identical methodology. The new strategy is designed to provide better granularity, support more frequent releases, and aid in troubleshooting by providing build information. In it’s generic form, the version number will appear as
|major||1-255||The last two digits of the release year.*|
|minor||1-255||An internal number indicating when code moves from Trunk to Beta.|
|minor_minor||1-65535||The first two digits indicate the track. 20 = Continuous. 30 = Classic.|
|Hidden 4th field||Changelist number||Only visible if user clicks on the version number in the About box.|
* The year-based version number is not the same as the Classic track name. While the Classic track version begins with
15 and the current track version is
2015, the track name only changes at each major release–not every year. The version number increments every year.
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:
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:
New and existing installations may work with one or more of the following file types.
- 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.
- PKG: Includes both full and update installers. The download is a DMG file.
All updates, including out of cycle patches, are cumulative to the base release. Chaining updates is never required. For all products and tracks, install the base release and the last update.
The version number helps you determine the number of releases that have been issued since your last install. Attempts to update in an unsupported order will result in failure.
To get to the latest version, install the product in this order:
- Acrobat: Base release > latest quarterly > latest security update
- Reader: Latest MSI > latest quarterly > latest security update
Quarterly updates are cumulative to the base release (or the last installed MSI in the case of Reader), and security patches are cumulative to the last quarterly. Thus, quarterlies always include all previously released out of cycle security patches.
To distribute the desktop or mobile Reader in any form, do the following:
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.
For details about Acrobat installations, see Common Deployment Options and Methods.