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

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 file through the command line or by double-clicking it (and not through the Exception deployer tool).

You can also use the Enterprise Toolkit (ETK) to deploy customized products across your organization, set up virtualized installs, and create enterprise PDF workflows. Acrobat ETK provides wide range of IT details about Adobe Acrobat Document Cloud configuration and deployment, also, about the earlier product versions.

Adobe Acrobat Licensing

Based on your business or organization requirement, you can choose Adobe subscription license, Adobe term license, or Adobe Acrobat perpetual license. To find best licensing program for your organization, see Compare licensing Programs.

Adobe Acrobat Licensing are associated with Continuous track.  For more information on tracks, see Document Cloud Product Tracks. Once you have chosen a licensing program and the required product track, download the installer to proceed further in the deployment process.

Download installer

If you no longer have the installation media of Acrobat DC (Non-subscription, serial number based), you can download the replacement installer from the Download Acrobat DC | Non-subscription page.

You can use Adobe Licensing Website (LWS)  to find serial numbers, track orders, view purchase histories, check upgrade entitlements and points, change or add account contacts and information, merge accounts, and download software. For more information, see the documentation on Adobe Licensing Website (LWS).

Security Notification Service

The Adobe Security Notification Service is a free e-mail notification service that Adobe uses to send information to customers about the security of Adobe products. For more information, see Adobe Security Notifications Registration.

Application Security

Adobe provides a security model designed to help you protect your environment from security attacks. To explore the options for tuning applications for the desired security level, see Application Security Overview.

Adobe Customization Wizard DC

Adobe Customization Wizard DC (Windows and Mac OS X) is available in ETK. The Wizard streamlines the task of configuring (customizing) the installer prior to organization-wide deployment. For example, if you have a volume license, you do not need to register and personalize each copy of the product you install. You can customize the installer to not only skip the standard registration questions, but also accept the End User License Agreement and fill in your organization name automatically.

The Wizard DC can only be used to tune Acrobat DC products. 

Use Customization Wizard to customize Acrobat packages

If you are an enterprise customer, you can use the Adobe Customization Wizard to further customize your package, using the following workflow.

To customize Acrobat DC from your downloaded package, you need the latest version of the Adobe Customization wizard, and the downloaded Acrobat Pro .msi (Windows) or .pkg (mac OS) file.


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

  1. Create a package using either of the following methods:

  2. Launch the Customization Wizard.


    Do not enter your Creative Cloud Enterprise License key in to the configuration wizard if already specified in the Create Package workflow.

  3. From the File menu in the Customization Wizard, select Open Package and browse to the Acrobat Pro MSI (Windows) file or Acrobat PKG (mac OS) file for the package created in step 2.

  4. In the Personalization Options section, enter the serial number of Creative Cloud for enterprise in the Serial Number field.


    • If you have one or more Acrobat DC Pro serial numbers, you can either use the serial number of Creative Cloud for enterprise or an Acrobat Pro serial number.
    • If you use the Customization Wizard for creating a custom package for named users, leave the serial field blank.

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

  6. Click Grant Offline Exception & Disable Registration.

  7. Save the package.

    Windows: This will generate a "transformations" file (with the extension .mst) in the Acrobat directory. This file is used when installing Acrobat via the package. Deploy the output of the Customization Wizard to your clients as described in the Customization Wizard documentation.

    mac OS: Overwrite the Acrobat PKG contained in the Creative Cloud Packager created package with the Customization wizard output.

  8. Proceed to deploy the Creative Cloud Packager created MSI (Windows) or PKG (mac OS) file to the client.

For more information, see the Adobe Customization Wizard documentation (Windows | Mac OS)


For a Windows 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 (Windows) or PKG (mac OS) 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.

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


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 run 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...



OS Language



Language explicitly specified in command line while deploying a package

Not Selected

Not Selected


Language in which the package is created


Yes, but the specified language is unavailable

Language in which the package is created

Not Selected


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 example:
setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA
Location of setup.exe:

Uninstalling Acrobat 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 stand-alone package.  

One for the Acrobat Pro MSI package and the second MSI package that the Creative Cloud Packager creates for licensing. 

The Acrobat Pro MSI package is at the following path for Acrobat DC:



Itis recommended to run 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 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.

Suite GEO
Suite locales
Acrobat DC locales Acrobat bundle
English (North America) en_US Acro LS1
  English (International)
  French Canadian
ja_JP Acro LS2
Americas / Europe
(Central Europe)
English (North America)
en_US Acro LS1
  English (International)
  French Canadian
es_ES Acro LS6
  Spanish North America (es_MX)
  Spanish Latin America (es_LA)
  Portuguese (Brazil)
sv_SV Acro LS7
ko_KR Acro LS5
  Chinese Simplified
zh_CN Acro LS3
  Chinese Traditional
zh_TW Acro LS4
Eastern Europe
  Czech cs_CZ Acro LS8
  Polish pl_PL  
  Hungarian hu_HU  
  North African French fr_FR Acro LS1
  Middle Eastern English Arabic en_US  
  Middle Eastern English Hebrew 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