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.
Using Creative Cloud Packager
For more information on using Creative Cloud Packager, see the Creative Cloud Packager documentation.
What's new in Creative Cloud Packager 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 Creative Cloud Packager 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 Creative Cloud Packager 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 significantly lower.
What's New in Creative Cloud Packager 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.
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 please visit this 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 version 1.4 of Creative Cloud Packager.
- Problem: A disk or an ISO image that contains Windows media is accepted on Mac OS computers and vice-versa. Packages created using such media fail during deployment.
- Problem: Products with native installers, such as Adobe Edge Reflow CC, Adobe Edge Inspect CC, Adobe Edge Code CC Preview, Adobe Gaming SDK 1.1, and Adobe Scout CC, in Creative Cloud media of May’13 cannot be added to the package using the Add Offline Media workflow, as they miss one of the required files.
- Problem: On Windows, products such as Adobe Muse and Adobe Lightroom can be packaged from Creative Cloud media of May '13 but cannot be successfully deployed.
- Problem: On uninstalling the package on Windows (uninstalling MSI, removing exceptions individually from ARP, removing ACC from ARP), “Adobe Setup Utility” still remains on user’s system.
- 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) has licensing issues. Do not include Flash Builder 4.6 from the diskset.
- Problem: When Acrobat is launched and user clicks on Help > Product Registration, a sign-in required message with '32767 days left' is displayed. Acrobat continues to work, and the message can be ignored.
- Problem: In some scenarios, when package building fails due to less disk space/removal of flash drive etc, package gets corrupted. When modifying an existing package if failure occurs as a result of low disk space or inaccessibility of media, corruption to the original package occurs.
- Problem: (Mac OS only) : On modification of an update only package by adding some products, Provisioning tool doesn't get added into the package. When modifying an existing package that contains only updates, if an application then gets added licensing will not occur, even if original package contained license information.
The following issues are known to occur in version 1.3 of Creative Cloud Packager:
- 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: If two serialized packages are installed on a machine then on uninstalling one of them, the license gets removed from the machine due to which the products of the other package also get unserialized.
Workaround: Product still present on machine can be serialized using APTEE.
- 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.
- Problem: Adobe Creative Cloud desktop app, Muse, Inspect, Code, Reflow, Scout, and Lightroom are not removed on uninstallation of the package.
Workaround: On Windows, all of these can be removed via their uninstaller from the ARP. On Mac OS, Lightroom gets uninstalled on uninstallation of the package but Muse, Inspect, Code, Reflow, 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.
- Problem: For Creative Cloud for enterprise, feature-bearing updates cannot be installed through Remote Update Manager or Adobe Updater.
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.
- Problem: On launching Adobe® Edge Animate, Adobe® Photoshop® Lightroom®, or Muse, the Sign-In Required screen is not displayed.
- Problem: On launching Muse, an update screen with the message ‘A new version of Muse available’ is displayed. The EULA for Adobe AIR is also displayed.
- Problem: Adobe product Improvement program is not disabled for Muse, though it is disabled for other products.