About Adobe Creative Cloud Packager

Adobe® Creative Cloud™ Packager makes it easy for you to create packages that contain Creative Cloud products and updates. These packages can then be deployed to the client machines in your organization depending on the license type.

What's new in 1.13

Creative Cloud Packager 1.13 ships with performance improvements and a number of critical bug fixes.

What's new in 1.12

Creative Cloud Packager 1.12 ships with performance improvements and a number of critical bug fixes.

What's new in 1.11

The following features are available in Creative Cloud Packager 1.11:

We have introduced a new workflow called Create Uninstall Package. This workflow allows the IT admin to create a package that facilitates the removal of previous versions of Creative Cloud applications. For details, see Uninstall Creative Cloud products.

When you are creating packages, selecting the Show Applications and Updates via the Apps panel option, ensures that updates are enabled. Deselecting this option ensures that updates are disabled. For details, see Create packages.

What's new in 1.10

The following features are available in Creative Cloud Packager 1.10:

When you create a package, a packageInfo.txt is created inside the build package folder. This file contains the list of products and updates that you have included in the package. For more information see, Deploy packages.

When you create a package, a ConflictingProcessList.xml is created inside the build package folder. This file contains information about processes that will conflict with the installation process. For more information, see Deploy packages.

When you start the installer, it will check for the conflicting processes running on the host computer and exit the installation if any conflicting processes are found.

The latest version of Remote Update Manager will be downloaded and packaged during the package creation process. For more information, see Use Adobe Remote Update Manager.

What's new in 1.9.6

The following features are available in Creative Cloud Packager 1.9.6:

The Deployment Dashboard now allows you to use the two filters for automatically created packages: Single Apps (By Adobe) and Collections (By Adobe). For more information, see Deployment dashboard.

In the Deployment Dashboard, you can now build and download a package containing just the Creative Cloud desktop app. Using this package you can install the Creative Cloud desktop application.

Earlier if two serialized or device pool packages created using same Complete Creative Cloud license were installed on a machine, then on uninstalling one the license got removed from the machine due to which the products of the other package also became unserialized or unsubscribed. When you create a package with the latest Creative Cloud Packager, this issue does not occur. For more information and steps on resolving this issue for the existing Mac packages, see Due to uninstallation of one serialized package, products of another package also became unserialized or unsubscribed.

What's new in 1.9.5

The following features are available in Creative Cloud Packager 1.9.5:

When you package an update for the latest Creative Cloud applications, you can now also install this on a system that does not already have the application. For a list of applications that presently support this functionality, see Applications that can be deployed without their base versions. The following icon appears next to the applications that support this functionality: .

You can now use the command line to uninstall individual products. For more information, see Deploying packages.

The productVersions parameter in Remote Update Manager (RUM) lets you selectively update versions of apps installed on client machines. For more information, see Use Adobe Remote Update Manager.

Using the deployment dashboard you can now download all Creative Cloud applications as single installers, regardless of you purchased entitlement with Adobe.

The Deployment Dashboard has been optimized to decrease the time taken for customization by 40%.

What's new in 1.9.4

Issues, such as the following, are fixed in Creative Cloud Packager 1.9.4:

Package metadata was earlier not uploading to Admin Console if the user was not an organization admin. Now, if an enterprise org user with any role creates a package, the package details appear in Admin Console.

Remote Update Manager (RUM) was earlier overwriting default valued specified by the admin. Now, if "Enable Remote Update Manager Deployment" option is selected on the "Advanced Configuration" screen of Creative Cloud Packager, Remote Update Manager is included in the package and deployed with the package.

What's new in 1.9.3

The following features are available in Creative Cloud Packager 1.9.3:

Packages are now created as multi-lingual. You can use the following to deploy a package in a language different from its default language:

Specify a language in the command line (windows) or using Info.plist file (Mac) while deploying a package.

What's new in 1.7

The following features are now available in Creative Cloud Packager 1.7

Package metadata now available in Dashboard: Customers who have access to the Admin Console are now able to view organization-wide information about the packages they and others in their organization have created. This helps facilitate IT collaboration and standardization. For more information, see Deployment Dashboard.

Apps panel masking: The packager allows the IT admin to deploy the Creative Cloud Desktop app while suppressing the Apps panel. This is advantageous for customers who want to avail Creative Cloud services while restricting the end-users ability to install and update applications without IT intervention.

What's new in 1.6

The following features are now available in Creative Cloud Packager 1.6

What's new in 1.4

The following features are now available in Creative Cloud Packager 1.4

You can edit packages created using Creative Cloud Packager 1.4 to add and remove applications or include latest updates.

You can now also include products from physical media, such as DVD, in addition to downloading the latest applications.

What's new in 1.3

The following features are now available in Creative Cloud Packager 1.3

You can now package native installers using Creative Cloud Packager. This enables you to package apps such as Adobe Muse and Adobe Edge family of products.

You can now package archived or CS6 versions of Creative Cloud apps.

What's new in 1.2

The following issues have been fixed in Creative Cloud Packager 1.2.

In the previous release, you could not deploy a package created with Creative Cloud Packager 1.1 on a machine that has the Creative Cloud Desktop application already installed. This limitation no longer exists in this release.

In the previous release, package installation failed if there was a conflicting process running on the client machine. In this release, the possibility of this happening is lower.

What's new in 1.1

In addition to supporting Adobe Creative Cloud for teams, Creative Cloud Packager now supports Creative Cloud for enterprise. Therefore, if you are an enterprise, government, or education customer with access to Creative Cloud for enterprise, you can use Creative Cloud Packager to create packages for the products for which your license is applicable.

If you are an administrator for Creative Cloud for teams, choose "I am a Creative Cloud team customer" as your account type while signing in.

If you are an administrator for Creative Cloud for enterprise, choose "I am an Enterprise, Government, or Education customer" as your account type while signing in.

Community resources

Adobe has a dedicated forum that covers the topic of deployment for both Creative Suite and Creative Cloud.

An Adobe IT-centric blog is updated regularly and covers a wide range of topics for managing Adobe software.

For a list of the network calls made by the applications and a description of the methods for controlling service access visit the following link.

Many Adobe teams have Twitter accounts and there is one dedicated to the IT tools and the topic of deployment: @Adobe_ITToolkit

Known behavior and issues

The following issues are known to occur in this version of Creative Cloud Packager (CCP).

Problem: On updating the override file, Adobe Creative Cloud desktop app does not take the updated redirection URL from the override file and displays a download error.

Problem: On launching Creative Cloud apps installed using a CCP package, the app might throw an error: "The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem."

Problem: If Adobe Creative Cloud desktop app is not present or the Apps panel is disabled on the machine, the user is not able to apply updates for latest versions of some applications updates using Help > Update.

Workaround: Package/deploy updates using the CCP package itself or use Remote Update Manager to apply updates.

Problem: If the machine is offline (network locked down scenario), then even if Creative Cloud desktop app is present on the machine it will not install updates on using Help > Update.

Workaround: Package/deploy new installer technology updates using the CCP package itself or use Remote Update Manager to apply updates.

Problem: On Mac, Acrobat updates do not sync from AUSST.

Problem: When update installation fails, the base version of the relevant product gets corrupt.

Workaround: Reinstall the base version of the product on the machine.

Problem: Adobe Muse CC fails to launch even after installing successfully on systems where .NET 4.5.2 or later is not present.

Workaround: Use the exception deployment workflow to deploy .NET Framework 4.5.2 or later on the target machines.

Problem: If you have created a package using a CCP version prior to 1.9.3 and you try to modify it using CCP 1.9.3, the modification of the package fails.

Problem: "Oops something has gone wrong" - when CCP displays this alert, often it is because some CCP-related files are corrupted on your machine.

Problem: A sign-in screen comes up on Acrobat DC launch if the Acrobat DC was installed by Exception deployer in the post mode.

Workaround: This happens because you need to deploy Acrobat DC using the setup.exe through the command line (and not Exception deployer tool) before installing the main msi. For more information, see Deploying Adobe Acrobat.

Problem: If Acrobat XI and Acrobat DC are in the same package, Acrobat XI deployment may fail on Mac, as Creative Cloud packager installs Acrobat DC followed by Acrobat XI and a later version of the app is available on the machine.

Problem: Acrobat DC is installed on a machine and you try to install Acrobat XI through Creative Cloud packager. Installation of Acrobat XI fails, as a later version of the app is already available on the machine.

Problem: Updates are not getting enabled with the new CCP package deployment, after we already have acrobat updates disabled initially on the Mac.

Workaround: Deploy the package with changed update configuration.

Problem: For enterprise login, user is not shown sign-in screen even after signing out from previous workflow. User gets automatically signed in with previous user credentials even if the user enters a different user ID in the new workflow.

Workaround: Quit Creative Cloud Packager and sign in again.

Problem: Once an Enterprise ID sign in process is initiated and an email ID entered, there is no way to cancel the process to let another user sign in.

Workaround: Force quit Creative Cloud Packager and sign in again. Alternatively, click the screen and press Delete/Backspace multiple times to go back in the workflow.

Problem: When you run RemoveVolumeSerial executable file, an enterprise subscription license created using Creative Cloud for enterprise volume serial number also gets removed.

Problem: In Windows, offline screen appears instead of Sign In screen when you select Team or Enterprise workflow and then enter proxy credentials in the native proxy dialog.

Workaround: Modify this package so that the latest ASU gets packaged, and then deploy the package to the same machine. Now on uninstallation, the Adobe Setup Utility also gets uninstalled.

Problem: During imaging workflow, it is recommended that Muse is NOT launched on the primary machine before you make an image. You can launch it on secondary machines, after deploying the image.

Problem: Using Flash Builder 4.6 from Creative Cloud diskset (May’13 and Dec '13) has licensing issues. Do not include Flash Builder 4.6 from the diskset.

Problem: If a package with the Creative Cloud desktop app enabled has been deployed on a machine then on installing another package with Creative Cloud app disabled on the same machine, the Creative Cloud desktop app doesn't get disabled or removed from the machine.

Problem: Applications such as Edge Code, Inspect, Reflow, Scout, Lightroom, Adobe Creative Cloud application, Extendscript Toolkit, Gaming SDK will always get installed at their default location on both Windows and Mac OS. Acrobat does get installed at custom location on Windows but it doesn't get installed on custom location on Mac OS.

Problem: Pre-baked license key is already displayed in the registration option under help in Lightroom.

Problem: Check for updates options is not disabled for Reflow, Code, and Lightroom.

Problem: (Windows Only) : On first launch of Adobe Scout, Windows firewall has blocked some features dialog is displayed. On subsequent launches the message is not displayed.

Workaround: On Windows, all of these can be removed via their uninstaller from the ARP. On Mac OS, Lightroom, Muse, Inspect, Code, Reflow, and Scout, can be removed by moving them to trash. Adobe Creative Cloud desktop app can be removed via its uninstaller present in the utilities.

Problem: For a client machine that is running Mac OS X 10.9, the payloads in the Exceptions folder cannot be installed via ssh.

Workaround: For a client machine that is running Mac OS X 10.9, the payloads in the Exceptions folder should be installed via ARD.

Problem: (Mac OS only) If Creative Cloud Connections is installed on a client machine, the package installation will fail if no user is logged in on that machine.

Workaround: Install the package on the client machine when the user is logged in.

Problem: If a Creative Cloud application is running on a client machine, packages cannot be deployed on that machine.

Workaround: Close the Creative Cloud application before installing the package.

Workaround: Create a new Package and deploy these updates using the latest version of Creative Cloud Packager.

Problem: Adobe Application Manager Enterprise Edition version 2.1 cannot be run on the same machine where Creative Cloud Packager is installed.

Problem: Adobe® Encore® doesn’t work in trial mode.

On launching Encore, the serial number screen is displayed if Encore is the first product to be launched.

Workaround: Start the subscription license by launching another product. After this, Encore can be launched successfully.

Problem: Adobe AIR-based exception payloads cannot be installed in unattended mode on client machines that run a proxy server. A proxy authentication dialog is displayed that needs to be responded to before the installation can proceed. This problem also occurs while deploying such payloads through the Adobe Exceptions Deployer Application.

Workaround: Install these products on client machines without running a proxy server.

Problem: On client machines that run a proxy server, a proxy server dialog is displayed on launching any of the following products: Adobe® Dreamweaver®, Adobe® Fireworks®, Adobe® Illustrator®, and Adobe® InDesign®

Problem: Notification for Adobe® AIR® updates is displayed for Adobe Help Manager even if updates are disabled in the package.

Problem: The Adobe AIR End-User License Agreement (EULA) is displayed on launch of Adobe AIR-based products.

Problem: Adobe Help Manager does not get installed if Adobe AIR is already installed (even on different drive) on the machine.

Workaround: Before installing Adobe Help Manager, uninstall any existing Adobe AIR installation from the machine.

Problem: (Mac OS only) When creating a package through Creative Cloud Packager, if you select the "Disable Air Components in Package" option in the Configure Package screen, AIR-based packages such as Adobe Community Help are not included in the package. This is required in certain scenarios, for example while performing an ssh-based installation or for avoiding manual entry of proxy credentials. These packages are copied in the Exceptions folder and you can install them separately on the client machines. However, for a client machine that is running Mac OS X 10.7, the payloads in the Exceptions folder cannot be installed via ssh if no user is logged in to the client machine. For a client machine that is running Mac OS X 10.8, AIR-based payloads cannot be installed via either ARD or ssh if no user is logged in to the client machine.Note: This issue occurs when client machines are running MAC OS X 10.7 or Mac OS X 10.8. Using an admin machine running MAC OS 10.7 or Mac OS X 10.8 does not affect the installation of the packages in the Exceptions folder.

Workaround: For installing Adobe AIR-based packages from the Exceptions folder on a client machine that is running MAC OS 10.7 X or Mac OS X 10.8, ensure that a user is logged in to the client machine when you are installing the packages in the Exceptions folder.

Problem: Adobe Muse cannot be launched on a client machine on which a proxy has been set.

Problem: If an image of a package is created on a machine and the image of the machine is used to deploy the package, the first launch of the first product fails in some cases. The product gets launched the second time onwards.

Problem: Once AIR components are successfully installed, trying to reinstall them might result in failure.

Workaround: Once AIR components are successfully installed, do not try to reinstall them.

Problem: (Mac OS only) Package deployment through Apple Remote Desktop 3.5 or 3.6 fails in the scenario where all of the following conditions exist:

the package name contains double-byte characters

the package is deployed in “Run this task from the Task Server on this computer” mode

Problem: User preferences are not removed from the target machine on uninstall using Creative Cloud Packager. (Windows/Mac OS)

Workaround: Remove user preferences manually.

Problem: Uninstall command is not available for uninstallation of products in the "Exceptions" folder, which are not installed via the deployment package created with Creative Cloud Packager. (Windows)

Workaround: Remove these programs via Add or Remove Programs.

Problem: When creating a package, the packaging process will fail if you try to save the package to a network location on a different operating system. For example, packages created using a Windows machine cannot be saved on a network location on Mac OS and vice versa.

Workaround: When creating a package and saving it on a shared location, save the package on a network location on the same operating system that is on the machine used to create the package.

Problem: In Mac OS, if the root directory of the booted volume is specified as the deployment target when building a package, the installer will deploy to the default location. In Windows, if a drive without a folder name is specified as the deployment target when building a package, installation fails. A descriptive error is written to the Installer logs. (Mac OS/Windows)

Workaround: Do not provide the root folder as the location for package deployment.

Problem: When you deploy through ARD in Mac OS, the deployment fails if a user logs in or out or switches users during the ARD task. (Mac OS)

Workaround: Wait for some time, then redeploy.

Problem: On uninstalling a package from a Mac OS client machine in logged-out mode, Creative Cloud Connection doesn't get uninstalled.

Workaround: Uninstall the package in the logged-in mode.

Problem: On logging in to a Windows client machine after Adobe® Muse™ has been deployed in the logged-out mode, a Windows dialog ‘File Name Warning’ with a message to rename “C:/Program” to “C:/Program1” is displayed.

Workaround: Rename the location to “C:/Progam1”, create a new shortcut for Muse on the desktop, and then launch Muse using the shortcut.

Problem: While Creative Cloud Packager is running, if you try to pin Creative Cloud Packager to the taskbar or dock by right-clicking its icon in the taskbar or dock, the Adobe Application Manager icon is pinned to the taskbar or dock instead of Creative Cloud Packager. If you then launch it by double-clicking the pinned icon, the "Updates Failed" screen is displayed.

Workaround: Do not pin the icon to the taskbar or dock using the above method. Instead, drag the Creative Cloud Packager icon directly from the Start menu to the taskbar or dock.