Open the Info.plist file at the following location:
As an Admin, you create packages on the Adobe Admin Console for the Adobe apps and services that you want to distribute to your end users.
Once the package is created and downloaded to your computer, you can distribute the package and install the packaged apps by one of the following methods:
Double-click the setup.exe file present inside the Build folder of the package.
If you are using MSI, instead of setup.exe, to deploy a package that has Acrobat in it, Acrobat is not installed.
Double click the .pkg file present inside the Build folder of the package.
To customize the install options, update the Info.plist file:
The package starts installing.
Use the following third-party tools to deploy the packaged Adobe apps and services:
Command line has more required parameters, for which default values are taken if you run Setup.exe by double-clicking.
In the command:
[ADOBEINSTALLDIR] is the installation directory where apps are to be installed on the client machine.
[INSTALLLANGUAGE] is the locale in which the apps are to be installed.
setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=]
setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA
Location of setup.exe:
The initial package will contain applications and the most recent updates. When updates are available, you can provide the updates to your users in the following ways:
If Remote Update Manager was included in your deployment package (default behavior), use your deployment tool to remotely run the Remote Update Manager on client machine. Updates will run with administrator privileges and come from Adobe Update Server.
If you have an internal Adobe Update Server, choose it during package creation. Remote Update Manager pulls updates from your internal server rather than the Adobe server, which saves network bandwidth.
To save network bandwidth, it is also possible to set up your own internal Adobe Update Server. You can use AUSST to set up a server which will host both Windows and macOS Updates.
The deployment of Creative Cloud 2019 and later apps is not supported in a serial or legacy device license deployment environment. For Creative Cloud 2019 and later, you must choose Named User Licensing or Shared Device Licensing. See the overview of Adobe licensing methods.
If you create a package that contains Universal Windows Platform based apps, you will experience unexpected behavior when you deploy the package on an end-user computer. For details, see the issues and limitations document.
Following are the locations of log files for the corresponding Adobe deployment tools:
Adobe Update Server Setup Tool (AUSST)
Remote Update Manager (RUM)
Creative Cloud Packager (CCP)
PDApp log is named PDApp.log
Package Builder log is named as follows:
Creative Cloud download/installation logs
Creative Cloud Packager creates a log file to troubleshoot download issues if a file called "asu.trace" is placed at:
The resulting file, DLM.log is created at:
For Windows errors (for example, 12150) in the DLM.log, see Windows Dev Error Messages.