Deploy packages

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 package file


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 DC in it, Acrobat DC 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:

  1. Open the Info.plist file at the following location:


  2. Add the following entry with the appropriate path in the string tag to configure a custom installation directory where apps will install on the client machine.


    <string>[Path of install directory]</string>

  3. Add the following entry to the file with the appropriate language mentioned in the string tag:

    <key> InstallLanguage </key>


  4. Double-click the .pkg file.

The package starts installing.

Use third-party tools

The following is the sequence of events for deploying packages.

  1. After you create a package on the Adobe Admin Console, the package is downloaded to your computer.

  2. Use the following third-party tools to deploy the packaged Adobe apps and services:

Use the command line


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.



Syntax example:

setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA

Location of setup.exe:


Deploy updates

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.

  • You can create an update-only package in the Admin Console. You can then deploy this package using your chosen deployment tool.


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.

Deploy UWP Apps

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.

Log file locations

Following are the locations of log files for the corresponding Adobe deployment tools:


Log filename

Adobe Update Server Setup Tool (AUSST)


Exception Deployer


Remote Update Manager (RUM)


Creative Cloud Packager (CCP)

PDApp log is named PDApp.log

Package Builder log is named as follows:
Where hhmmss_ddmmyy = hour|minute|second_date|month|year

Licensing logs:

  • Windows: %temp%\oobelib.log
  • macOS: /tmp/oobelib.log

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:

  • Windows: %temp%
  • macOS: ~/Library/Logs

The resulting file, DLM.log is created at:

  • Windows: %temp%\AdobeDownload
  • macOS: ~/Library/Logs/AdobeDownload

For Windows errors (for example, 12150) in the DLM.log, see Windows Dev Error Messages.

Logotip Adobe

Prijavite se v svoj račun