This article describes how to deploy packages for Adobe® Creative Cloud™ created using Adobe Creative Cloud Packager. This article is applicable for both Adobe Creative Cloud for teams and Adobe Creative Cloud for Enterprise customers.

Note: For application-specific behavior and a list of information and solutions for certain scenarios, see the ReadMe.

Packages created with Adobe Creative Cloud Packager (CCP) contain two top-level folders: Build and Exceptions. Installation of the software and license selection is possible using the file setup.exe in the Build folder for a majority of applications, but there are a small number of applications which are installed using a separate tool in the Exceptions folder, depending on when the package was created and which applications are included within it.

Deploy packages

Once the package is created, you can distribute the package and install the packaged apps by double-clicking the package file or use third-party deployment tools.

To deploy a package in a language it was not created in, use one of the following to deploy it:

Install by double-clicking the package file


On Windows, you can double-click the setup.exe file present inside the Build folder of the package. For instructions on installing products in the Exceptions folder, see Installing packages in the Exceptions folder.


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:

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


  2. Add the following entry with the appropriate path in the string tag to set a custom installation directory where apps are to be installed 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 with Adobe Creative Cloud Packager.

  1. Create a package using the Creative Cloud Packager. For more information, see Creating packages.

    As part of the build process, two folders are created:

    1. The Build folder contains the setup.exe (Windows) or the PKG (Mac OS) files.
    2. The Exceptions folder contains the payloads that must be installed separately.
  2. Deploy the packages in the Build folder using an enterprise deployment tool such as Microsoft System Center Configuration Manager (SCCM), Apple Remote Desktop, or JAMF Casper Suite. For more information, see Deploying Adobe packages with ARD and Deploying Adobe packages with SCCM

  3. Install the packages in the Exceptions folder separately. For more information, see Installing Products in the Exceptions folder.

Deploy using command line on Windows machines

Command line has additional 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. 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.

1. You can use Creative Cloud Packager to create an update-only package by selecting only the updates. You can then deploy this package using your chosen deployment tool.

2. 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.

3. 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 Mac Updates.

In scenario 2 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.

For more information, see Using Adobe Remote Update Manager.

Deploy named user license apps

The deployment of named-user license apps (such as Adobe XD) is not supported in a serial or device license deployment environment.  All users, must have an Adobe account (Adobe ID, Enterprise ID or Federated ID) in order to use named-user license apps such as Adobe XD.  Admins will experience issues if they try to deploy named-user license apps in non-named user deployment environments.

For details on the different types of Adobe account, see Manage identity types.

Deploy UWP Apps

If you create a package using Creative Cloud Packager 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.

Serialize trial packages

If you have an Enterprise, Government, or Education account, and have created a trial package, you will need to serialize the package once the trial period is over. You can create and deploy a license package to convert a trial package to a licensed package.

For more information, see Create license package.

Install packages in the Exceptions folder

When you create a package with Adobe Creative Cloud Packager, two folders are created:

  • The Build folder contains the MSI (Windows) or the PKG (Mac OS) file for deployment with Microsoft SCCM or Apple ARD.
  • The Exceptions folder contains the payloads that must be installed separately. The content of the folder depends on whether you are installing on Mac OS or on Windows, and whether you have included Adobe® Acrobat® as part of the package.

Information on installing the products in the Exceptions folder is provided in the article Installing Products in the Exceptions Folder. Information on deploying Acrobat for Windows is provided in the article Deploying Adobe Acrobat.


The Adobe Exceptions Deployer provides an automated way to deploy the packages in the Exceptions folder. For more information, Using Adobe Exceptions Deployer.


For Adobe® Muse™ CC (2015.2) and onwards, the exceptions (such as .NET) are copied in the following location and the user needs to install them separately:

Program Files (x86)\Common Files\Adobe\Installers\Third Party\<Sapcode_Of_App>\<package_name>\

Adobe Creative Cloud Packager logs

When you install or run Adobe Application Manager Enterprise Edition, it creates or writes to log files on the admin system, in your platform’s temporary-file location:

  • In Windows, logs are in the %temp% location
  • In Mac OS, logs are in the folder ~/Library/Logs/

You can check for troubleshooting information related to errors by searching for the "error" string in the logs.

The log names are as follows:

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:
- AdobePBhhmmss_ddmmyy.log
-- where hhmmss_ddmmyy = hour|minute|second_date|month|year

Licensing logs:
- Win: %temp%\oobelib.log
- Mac: /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 %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.

Uninstall products using command line

You can use the command line to uninstall latest versions of some individual products.

For a list of products you can uninstall using the command line and their sapCodes, baseVersions, and platforms, see Applications that can be deployed without their base versions.

Syntax examples:

  • Windows: \Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\HDBox\Setup.exe --uninstall=1 --sapCode=PHSP --baseVersion=17.0 --platform=win32 --deleteUserPreferences=false
  • Mac: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Setup --uninstall=1 --sapCode=PHSP --baseVersion=17.0 --platform=osx10-64 --deleteUserPreferences=true

In the command:

[uninstall] Specify as 1 to uninstall.

[sapCode] is the sap code of the product to be uninstalled.

[baseVersion] is the base version of the product to be uninstalled.

[platform] is the OS on which of the product to be uninstalled.  

[deleteUserPreferences] specify true to delete user preferences on the product to uninstall or false to retain the user preferences. 

Location of setup:

  • Windows: \Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\HDBox\Setup.exe
  • Mac:  /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Setup

Error codes

If incorrect arguments are passed, error code 103 is returned. If incorrect values are passed in any of the parameters, error code 101 is returned. For information on other error codes, see Troubleshoot Creative Cloud apps installation and uninstallation errors.