This article explains how to deploy Adobe Acrobat DC if you are using Adobe Creative Cloud for teams Single App. It applies to both Acrobat Pro DC and Acrobat Standard DC.
If you have a Creative Cloud All Apps subscription, use Creative Cloud Packager for deploying Acrobat DC. See this page for detailed instructions.
To deploy Acrobat DC as Creative Cloud for teams Single App, perform the following steps in sequence:
After installation of Customization wizard, launch the wizard for Acrobat DC and follow the steps:
To change installer package, do the following:
Acrobat is configured to automatically ping Adobe servers to determine if there is a new patch/update available. If you want to change it for your deployment, you can do that using the Customization wizard.
Windows installers are self extracting exe files. Run the downloaded exe once to extract the installer files. By default, the installer files are extracted in an "Acrobat DC" folder on your desktop. To install Acrobat on Windows, do any one of the following:
Navigate to Acrobat DC folder in command prompt and run the following command:
Setup.exe /sl "[LangCode]" /sALL
In the command above:
1033=English (United States)
1034=Spanish (Traditional Sort)
1025=English with Arabic support
1037=English with Hebrew support
For example, if you pass “1033” in [LangCode], Acrobat launches in English.
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).
Once you have deployed Acrobat, you can uninstall it using the usual process for uninstalling msi packages. It can be done individually using "Add and Remove Programs" in Windows "Control Panel". 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
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 standard 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/#.
You can deploy Acrobat DC Updates using standard deployment practices used in your organization. For more information about updates, see Patch release notes.
For information on deploying Acrobat in a virtualized environment, see Virtualized Deployments.