Introduction

This article explains how to deploy Adobe® Acrobat® XI and DC if you are using Adobe® Creative Cloud™ for teams or enterprise.

  • Acrobat DC: On Mac and Windows OS Acrobat DC is included in the package file that is created using Creative Cloud Packager. Deploy Acrobat DC using the package setup.exe through the command line or by double-clicking it (and not through the Exception deployer tool).
  • Acrobat XI: On Windows, Acrobat XI is packaged in the exceptions folder instead of the main installation package. Deploy Acrobat XI before you install the MSI package created by Creative Cloud Packager. It should be installed using exception deployer tool in pre mode.

Note:

If you use the CCP package MSI instead of the package setup.exe to deploy the package, Acrobat DC is not installed. 

Note:

Acrobat updates cannot be packaged using Adobe® Creative Cloud™ Packager. However, Acrobat updates are native formats (.msp on Windows and .pkg on Mac OS) and can easily be deployed separately using standard deployment tools. See Acrobat Enterprise Toolkit at http://www.adobe.com/devnet-docs/acrobatetk/ or your vendor's deployment documentation for more information about deploying .msi or .pkg files.

Using the Adobe Customization Wizard

If you are a Creative Cloud™ for enterprise customer, you can use the Adobe Customization Wizard to further customize your Creative Cloud Packager package, using the following workflow.

Windows

If you are a Creative Cloud Enterprise Customer, you can use the Adobe Customization Wizard to further customize your Creative Cloud Packager package, use the following workflow.

  1. Download Adobe Customization Wizard for Windows.
  2. Create a package using the Creative Cloud Packager that contains Acrobat. For more information, see Creating Packages.
  3. For Acrobat XI, copy the Acrobat folder from the Exceptions folder to your desired location. For Acrobat DC, the Acrobat folder is already inside the Setup folder.
  4. Launch the Customization Wizard and customize the copied contents from step 3.
    Note: Do not enter your Creative Cloud Enterprise License key in to the configuration wizard
  5. On Windows, deploy the output of the Customization Wizard to your clients as described in the Customization Wizard documentation. Additionally, skip the pre mode launch of the XDA tool to deploy Acrobat.
  6. Proceed to deploy the Creative Cloud Packager created MSI or PKG file to the client.

Mac OS

  1. Download Adobe Customization Wizard for Mac OS.
  2. Create a package using the Creative Cloud Packager that contains Acrobat. For more information, see Creating Packages.
  3. View the package contents and browse to the Acrobat PKG file and then copy to your desired location.
  4. Launch the Customization Wizard and customize the copied contents from step 3.
    Note: Do not enter your Creative Cloud Enterprise License key in to the configuration wizard.
  5. Overwrite the Acrobat PKG contained in the Creative Cloud Packager created package with the Customization wizard output.
  6. Proceed to deploy the Creative Cloud Packager created MSI or PKG file to the client.
For more information, see the Adobe Customization Wizard documentation (Windows | Mac OS)

Note:  EULA Suppression, update suppression, and registration suppression settings you select in the Creative Cloud Packager workflow take precedence over the settings in the Adobe Customization Wizard XI.

Note: For serialization of Acrobat, specify the serial number of the Suite on the Serial Screen of Creative Cloud Packager while creating the package. After deployment, Acrobat will be launched in the serialized mode. Do not use the Adobe Customization Wizard XI for serializing Acrobat.

Customize Acrobat DC from Creative Cloud Packager download

To customize Acrobat DC from your Creative Cloud Packager download, you need the latest version of the Adobe Customization wizard, and the Acrobat Pro .msi file downloaded by the Creative Cloud Packager.

Note:

The version of the wizard should be the same as the version of Acrobat in the package created by Creative Cloud Packager.

  1. From the File menu in the Customization Wizard, select Open Package to open the Acrobat Pro .msi file downloaded by the Creative Cloud Packager.

  2. In the Personalization Options section, enter CCE serial number in Serial Number field.

    Note:

    If you have one or more Acrobat DC Pro serial numbers, you can either use the CCE serial number or an Acrobat Pro serial number.

  3. Click the Allow standalone Acrobat deployment with CCE serial check box.

  4. Click Grant Offline Exception & Disable Registration.

  5. Save the package. This will generate a "transformations" file (with the extension .mst) in the Acrobat directory. This file is used when installing Acrobat via the package.

Once the MST file (also known as the transformations file) is saved to the Acrobat subdirectory within the package, you can begin to deploy the software to the target systems. It is possible to install Acrobat using its own MSI file, but this will not install the licensing information and any dependencies with the package. It is recommended to use the "setup.exe" in the "Build" directory to install a package created with Creative Cloud Packager which contains Acrobat DC, to ensure these dependencies (such as Microsoft's Visual C++ Redistributables) are also installed. See below for further information in installation.

Note:

If you are using the MSI installer, it will not handle dependencies such as the Microsoft Visual C++ redistributables relevant to the version of Acrobat (like PDFMaker) being installed.

For more information, see Windows cmd line and msiexec

Installing Acrobat on Windows

Note:

If you are using hard disk cloning or a similar technology, the software should be installed after the operating system is imaged.

Acrobat DC

To install a package containing Acrobat DC, you can either invoke the setup.exe (in the "Build" directory) using the command line or by double-clicking it.

The language in which the package is installed depends on three factors:

  • Whether or not Match OS Language option is selected while creating the package.
  • The language you specify in the command while deploying the package.
  • The language in which you have created the package.

The following table details how each of these factors affects the language in which the package is installed. 

Match OS language

Language explicitly specified while deploying a package using command line or Info.plist file

The package is  installed in...

Selected

No

OS Language

Selected

Yes

Language explicitly specified in command line while deploying a package

Not Selected

Not Selected

No

Language in which the package is created

Selected

Yes, but the specified language is unavailable

Language in which the package is created

Not Selected

Note:

When the installer is run, it checks for the locale that is set at the system level and not at the user level. For more details on this setting, see Install Creative Cloud package with Match OS Language option.

Command line has additional required parameters, for which default values are taken if you run package Setup.exe by double-clicking.

In the command:

  • [INSTALLDIR] is the installation directory where Acrobat is to be installed on the client machine.
  • [installLanguage] is the locale in which Acrobat is to be installed. Note that Acrobat might not be available in all languages, so you can only provide a locale that is supported by the Acrobat for that particular media. For example, to install Acrobat in the English (US) locale, specify en_US as the locale in the command. For a list of available locales for Acrobat in a particular suite, see the section Locales for different Acrobat configurations.
 
Syntax 
 
setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=] 
 
Syntax example:
 
setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA
 
Location of setup.exe:
 
[Package]\Build
 
 

Acrobat XI

Syntax:

msiexec.exe /i AcroPro.msi INSTALLDIR="[INSTALLDIR]\Acrobat 11.0" EULA_ACCEPT=NO SUITEMODE=1 OWNERSHIP_STATE=1 IGNOREVC10RT=1 LANG_LIST=en_US INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1 TRANSFORMS=[installLanguage].mst /qn  

Simplified example (default values assumed where not specified):

msiexec.exe /i AcroPro.msi EULA_ACCEPT=YES SUITEMODE=1 IGNOREVC10RT=1 IGNOREAAM=1 TRANSFORMS=en_US.mst /qn

Note:  There are no line breaks in the Command Prompt so if you copy the example text into Notepad make sure to remove any line breaks.

CCP MSI for Acrobat XI

Installing the Creative Cloud Packager MSI file has the following syntax for Acrobat XI:

msiexec.exe /i <CCP_PACKAGE_NAME>.msi /quiet

Uninstalling Acrobat XI and DC on Windows

Once you have deployed Acrobat using the package, you can uninstall it using the usual process for uninstalling msi packages. There are two MSI packages that are necessary to uninstall in a standalone package.  

One for the Acrobat Pro MSI package which is in the Exceptions folder for Acrobat XI and the second MSI package that the Creative Cloud Packager creates for licensing. 

The Acrobat Pro MSI package, which exists in the Exceptions folder for Acrobat XI, is at the following path for Acrobat DC:

[CCPPackage]\Build\Setup\APRO15.0\[locale-set]\AdobeAcrobat\AcroPro.msi

Note:

We recommend running the package MSI in uninstall mode to remove the Acrobat license. If, however, you have installed other apps on the machine that you still require, do not run the package MSI to uninstall acrobat XI or DC, as it will remove the license for other apps as well.

Here is the command line syntax for uninstalling Acrobat:

Syntax Example:

msiexec.exe /x <path to Acrobat msi file> /qn

Here is the command line syntax for uninstalling the Creative Cloud Packager licensing package:

Syntax Example:

msiexec.exe /uninstall <path to the CCP msi file> /quiet

 

Installing Acrobat Professional on Mac OS

On the Mac OS, Acrobat is displayed as part of the product list for Creative Cloud Packager. After you include Acrobat from the list, Acrobat is included in the package file that is created.

Locales for different Acrobat configurations

The following table provides the value of the locale to be specified for the --installLanguage option of the ExceptionDeployer command as explained in the section Exceptions Deployer Application syntax and description.

Suite GEO
Suite locales
Acrobat XI locales
Acrobat DC locales Acrobat bundle
English
English (North America) en_US
en_US Acro LS1
  English (International)
 
 
en_GB
 
 
en_US
 
 
 
  German
 
 
de_DE
 
 
de_DE  
  French
 
 
fr_FR
 
 
fr_FR  
  French Canadian
 
 
fr_CA
 
 
fr_FR  
Japanese
Japanese
ja_JP
ja_JP Acro LS2
Americas / Europe
(Central Europe)
English (North America)
en_US
en_US Acro LS1
  English (International)
 
 
en_GB
 
 
en_US  
  German
 
 
de_DE
 
 
de_DE  
  French
 
 
fr_FR
 
 
fr_FR  
  French Canadian
 
 
fr_CA
 
 
fr_FR  
  Spanish
 
 
es_ES
 
 
es_ES Acro LS6
 
 
  Spanish North America (es_MX)
 
 
es_ES
 
 
es_ES  
  Spanish Latin America (es_LA)
 
 
es_ES
 
 
es_ES  
  Italian
 
 
it_IT
 
 
it_IT  
  Dutch
 
 
nl_NL
 
 
nl_NL  
  Portuguese (Brazil)
 
 
pt_BR pt_BR  
  Swedish
 
 
da_DK
 
 
da_DK Acro LS7
 
 
  Danish
 
 
fi_FI
 
 
fi_FI  
  Finnish
 
 
sv_SE
 
 
sv_SV  
ASIA
Korean
ko_KR
ko_KR Acro LS5
  Chinese Simplified
 
 
zh_CN
 
 
zh_CN Acro LS3
 
 
  Chinese Traditional
 
 
zh_TW
 
 
zh_TW Acro LS4
 
 
Eastern Europe
 
 
Russian
 
 
ru_RU
 
 
ru_RU  
  Turkish
 
 
tr_TR
 
 
tr_TR  
  Ukrainian
 
 
uk_UA
 
 
uk_UA  
  Czech cs_CZ cs_CZ Acro LS8
  Polish pl_PL pl_PL  
  Hungarian hu_HU hu_HU  
  North African French fr_FR fr_FR Acro LS1
  Middle Eastern English Arabic en_US en_US  
  Middle Eastern English Hebrew en_US en_US  

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy