On macOS and Windows
You can 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.
Acrobat DC can also be deployed using the package created by using Creative Cloud Packager but we recommend that you use the create package workflows provided in the Adobe Admin Console.
Based on your business or organization requirement, you can choose one of the licensing programs:
- Adobe subscription license
- Adobe term license
- Adobe Acrobat perpetual license
To find best licensing program for your organization, see Compare licensing Programs.
In Acrobat DC, there are two tracks - Continuous and Classic. Download Continuous track builds. 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.
- This installer is multilingual; it can install Acrobat in any of the languages Acrobat DC supports. See the installation section below for more details.
- Windows installers are self extracting exe files. Run the downloaded .exe once to extract the installer in the Acrobat DC folder on your desktop.
Use the Customization Wizard (Windows and macOS) available in ETK to customize packages. The wizard streamlines the task of configuring (customizing) the installer before 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 skip the standard registration questions, 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.
Want to learn more about Acrobat Enterprise Toolkit (ETK)? See Enterprise Toolkit for Acrobat users.
Use the Customization Wizard to further customize your package, using the one of the following workflows (based on end user machine OS).
To customize Acrobat DC from your downloaded package, you need the latest version of the Customization Wizard, and the downloaded Acrobat Pro .msi file.
- If you have more than one Acrobat DC Pro serial number, you can use the serial number for Creative Cloud for enterprise or Acrobat Pro.
- The serial number field is only used for serialized deployments where the machine is licensed. If you use the Customization Wizard for creating a custom package via the Adobe Admin Console for named users, leave the serial field blank.
To customize Acrobat DC from your downloaded package, you need the latest version of the Customization Wizard, and the downloaded .pkg file.
Next, use Customization Wizard on the Acrobat DC Installer.pkg in the AcrobatVolume folder structure.
You can also set up the plist preferences for your customized packages. To learn more, see Pre-deployment configuration.
Now we have “AcrobatVolume” folder with dmg contents AND Customized Acrobat DC installer.
Next, run the following command line to use AcrobatVolume folder to the create the APRO20.0.dmg:
hdiutil create -volname "Acrobat DC" -srcfolder "/Users/labuser/Desktop/AcrobatVolume" -ov -format UDZO APRO20.0.dmg
Replace labuser with current user username in above command.
Windows: Deploy the modified installer with the Customization Wizard to your clients as described in the Customization Wizard documentation.
macOS: Deploy the package created with the Customization Wizard output.
Proceed to deploy the package created MSI (Windows) or PKG (macOS) file to the client.
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 (macOS) file, but it does 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 the create package workflows in Admin Console 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.
The MSI installer does not handle dependencies such as the Microsoft Visual C++ redistributables relevant to the version of Acrobat (like PDFMaker) being installed.
If you are using hard disk cloning or a similar technology, the software should be installed after the operating system is imaged.
Windows installers are
- Method 1: Install in Command Line mode on the user's machine
- Method 2: Install through GUI Mode on the user's machine.
- Method 3: Install through deployment methods like SCCM.
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:
- If 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
The package is installed in...
Language explicitly specified in command line while deploying a package
Language in which the package is created
Yes, but the specified language is unavailable
Language in which the package is created
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. 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 Locales for different Acrobat configurations.
The following table provides the value of the locale to be specified for the --installLanguage option.
||Acrobat DC locales||Acrobat bundle
||English (North America)||en_US||Acro LS1
|Americas / Europe
|English (North America)
|Spanish North America (es_MX)||es_ES|
|Spanish Latin America (es_LA)||es_ES|
|Chinese Simplified||zh_CN||Acro LS3|
|Chinese Traditional||zh_TW||Acro LS4|
|North African French||fr_FR||Acro LS1|
|Middle Eastern English Arabic||en_US|
|Middle Eastern English Hebrew||en_US|
Navigate to Acrobat DC folder in command prompt and run the following command:
Setup.exe /sl "[LangCode]" /sALL
In the command above:
- [LangCode] is the numerical Acrobat Launch language code based on the following language codes. For example, if you pass “1033” in [LangCode], Acrobat launches in English.
1033=English (United States)
1034=Spanish (Traditional Sort)
1025=English with Arabic support
1037=English with Hebrew support
In this method, you can simply copy the "Acrobat DC" installer folder you extracted from the downloaded exe (and optionally customized) to a user's machine and run Setup.exe to start the installation.
You can also follow usual deployment practices for Acrobat as mentioned in Acrobat ETK – http://www.adobe.com/devnet-docs/acrobatetk/#.
The following example shows Acrobat deployment through SCCM:
Run the downloaded exe to extract the installer in "Acrobat DC" folder. By default, files are extracted to your desktop. Once extraction is completed, do not proceed with install yet. You will have the extracted installer files, which you will use to deploy Acrobat using SCCM. Follow the usual processes for creating a package for deployment in SCCM Configuration manager. Give the path of Setup.exe in the Create Program wizard in SCCM (see below).
Use it to deploy Acrobat using SCCM. Follow the usual processes for creating a package for deployment in SCCM Configuration manager. Give the path of Setup.exe in the "Create Program wizard" in SCCM (see below).
Deploy Adobe Acrobat in a virtualized environment? For information on deploying Acrobat in a virtualized environment, see Virtualized deployments.
To install Acrobat on macOS, simply install the downloaded installer package (or the customized package if you have to use the Customization Wizard).
macOS installers are .pkg type installers that provide the necessary user interface prompts to run.
You can use deployment practices on macOS like ARD to deploy the chained package. More information is available in Acrobat ETK: http://www.adobe.com/devnet-docs/acrobatetk/#.
The Adobe Security Notification Service is a free email notification service that Adobe uses to send information to customers about the security of Adobe products. For more information, see Adobe Security Notifications Registration.
Once you have deployed Acrobat using the package, you can uninstall it using the usual process for uninstalling
The Acrobat Pro MSI package is at the following path for Acrobat DC:
It is recommended to run the package MSI in uninstall mode to remove the Acrobat license. However, if you have installed other apps on the machine that you still require, do not run the package MSI to uninstall Acrobat DC, as it removes the license for other apps as well.
Also it can be done using command line. Here is the command line syntax for uninstalling the Adobe Acrobat DC:
msiexec.exe /x <path to Acrobat msi file> /qn
You can deploy Acrobat DC Updates using deployment practices used in your organization. For more information about updates, see Patch release notes.