News: Introducing Adobe Creative Cloud Packager

About Adobe Creative Cloud Packager

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

Creative Cloud Packager provides workflows for both Creative Cloud for teams and Creative Cloud for enterprise.

Deploying Creative Cloud for teams with Creative Cloud Packager

Watch Adobe Evangelist Andrew Trice as he speaks about deploying Creative Cloud for teams with Creative Cloud Packager.

Deploying Creative Cloud for enterprise with Creative Cloud Packager

Watch Adobe Evangelist Andrew Trice as he speaks about deploying Creative Cloud for enterprise with Creative Cloud Packager.

Download Creative Cloud Packager as follows:

If you are a Creative Cloud for teams customer, download Adobe Creative Cloud Packager from the Team Admin Portal in Adobe Creative Cloud.

If you are a Creative Cloud for Enterprise customer, download Adobe Creative Cloud Packager from the Adobe Licensing Website (LWS). You also get your enterprise license key from the LWS.

Using Creative Cloud Packager, you create Windows and/or Mac OS packages (MSI or PKG files) and then using any third-party deployment tool that supports the deployment of native installers (for example Microsoft SCCM, Apple ARD, or JAMF Casper Suite) deploy them to client machines.


It is recommended that Creative Cloud Packager should not be installed on a system where one or more Creative Suite products or Creative Cloud Manager products have been installed. Adobe Application Manager 3.1 and Creative Cloud Packager can be installed and used on the same machine. However, they should not be running simultaneously during package creation.

Advantages of deployment packages


Adobe Creative Cloud Packager provides several advantages when deploying the Creative Cloud applications across large organizations.

Silent and custom install. Deployment packages enable silent installs. A silent install requires no input from end users on the systems on which it is executed, meaning that all choices affecting what is installed and how it is installed are made before the install is performed. These choices are stored in the package.

When creating a deployment package, you choose the applications and components you want to install from the product you are packaging. When packaging products for delivery on Windows, you can choose 32-bit or 64-bit versions of the applications. You can also easily choose install options that may not be available when users install applications directly. For example, you can direct the install program to ignore conflicting processes during installation.

Easy package creation. Package creation is easy with the Creative Cloud Packager—the Creative Cloud Packager has an easy-to-use GUI that makes it simple to create a deployment package

The packages created by the Creative Cloud Packager are in industry-standard formats (MSI in Windows, PKG in Mac OS) that are compatible with SCCM and ARD.

Modest system requirements: The system requirements for the Creative Cloud Packager are minimal.


Packaging versus Installation


Creative Cloud Packager does not perform an install; it creates a deployment package that records the install decisions you make ahead of time. When you create a package using Creative Cloud Packager, you download the products and their updates, configure product options for enterprise scenarios, and generate an output in native installer formats (MSI or PKG). The packages created are optimized for deployment using enterprise deployment tools.


Creative Cloud Packager Guidelines


Adobe deployment packages do not support snapshot installations.

Adobe deployment packages cannot be used to deploy system or application configuration information other than what is explicitly described in this document. In particular, you cannot deploy application–specific preference settings.

Do not edit the package file (MSI or PKG) created by the Application Manager. The only exception is when you want the user to specify the installation location in Mac OS. In this case, you must modify the Info.plist file in the generated PKG as described in the article Deploying Adobe Packages with ARD.

You can use Creative Cloud Packager to package only the tools and services that are part of the Creative Cloud. You cannot use this tool to package to Creative Suite applications or the desktop versions of other suites.

In Windows, if you want to install on both 32-bit and 64-bit systems, you must create both a 32-bit package and a 64-bit package.

The Creative Cloud Packager does not support the Administrative install point.

The Creative Cloud Packager does not support NFS or SMB.

Caution: Do not attempt to use a PKG package to install on a Windows system.

System Requirements