Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.
We recommend that you use the create package workflows provided in the Adobe Admin Console.
As an Admin, you creates 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:
If you are using MSI, instead of setup.exe, to deploy a package that has Acrobat DC in it, Acrobat DC is not installed.
On macOS, you can double click the .pkg file present inside the Build folder of the package.
To customize the install options, update the Info.plist file:
Command line has additional required parameters, for which default values are taken if you run Setup.exe by
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. Later when new updates become available you may want to make these available to your users. You can do this in a number of ways:
If Remote Update Manager was included in your deployment package (which is the default behavior) you can use your deployment tool of choice to remotely run the Remote Update Manager on the client machine. Updates will run with administrator privileges and come from Adobe Update Server.
If you have an internal Adobe Update Server and during package creation chose to use this server, Remote Update Manager will pull updates from your internal server rather than the Adobe server, thus saving much network bandwidth.
The deployment of Creative Cloud 2109 and later apps is not supported in a serial or legacy device license deployment environment. For Creative Cloud 2109 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 this document.
|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 %temp% (Windows) or ~/Library/Logs (Mac OS) location.
The resulting file, DLM.log is created at: %temp%\AdobeDownload (Windows) or ~/Library/Logs/AdobeDownload (Mac OS)
For Windows errors (e.g. 12150) in the DLM.log, see Windows Dev Error Messages.