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.6
The following features are now available in Creative Cloud Packager 1.6
- Creative Cloud Packager now supports creating a license file to serialize deployed trial or named license packages.
- Creative Cloud Packager now supports creating a Creative Cloud for desktop app only package.
- Fix for "Maximum path exceeded" error on Windows (32-bit), while deploying InDesign CC (2014) or InCopy CC (2014).
What's new in Creative Cloud Packager 1.5
The following features are now available in Creative Cloud Packager 1.5
- Creative Cloud Packager now supports Value Incentive Program (VIP) for education customers.
- You can now deploy specific version updates, rather than just the latest updates.
- Creative Cloud Packager also supports packaging non-Creative Cloud apps.
- Adobe Update Server Setup Tool (AUSST) now supports secure connections (https). The product update binaries, however, are still transferred over http.
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.
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.
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.
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 this version of Creative Cloud Packager.
- Problem: When you run RemoveVolumeSerial executable file, an enterprise subscription license created using Creative Cloud for enterprise volume serial number also gets removed.