Creative Cloud Packager FAQ
Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.
We recommend that you use the create package workflows provided in the Adobe Admin Console.
See how to create Named User Licensing packages and Shared Device Licensing packages.
The frequently asked questions around Adobe® Creative Cloud™ Packager are answered below.
Creative Cloud Packager is a tool that enables administrators to package all Creative Cloud applications and updates, or a customized subset. Creative Cloud Packager ensures version parity across all desktops, saving support costs and network congestion.
Creative Cloud Packager enables you, the IT admin, to maintain control of how Creative Cloud applications (and feature updates) are installed. Centralized deployment ensures that everyone is on the same version of the software, which reduces support costs. Centralized deployment also prevents network congestion, as you don’t have multiple users downloading the same bits at the same time.
You can tailor the Creative Cloud packages to meet the needs of your team. For example you can package Photoshop, Illustrator and InDesign for some team members, and then provide all of the video production tools to others. As the team grows and evolves, different packages can be created and deployed in order to ensure team members always have the tools they need to be successful. You can choose 32-bit or 64-bit versions of the applications, and specify advanced configuration options, providing greater control.
Creative Cloud Packager has an easy-to-use interface that makes it simple to create a deployment package. The packages created by Creative Cloud Packager are in familiar, industry-standard formats (MSI in Windows, PKG in macOS) that are compatible with familiar, industry-standard deployment solutions such as SSCM and ARD.
For more details, see the help documentation.
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, Government, or Education customer, download Adobe Creative Cloud Packager from the Adobe Licensing Website (LWS) or Admin Console. You also get your enterprise license key from the LWS.
All Creative Cloud and Digital Publishing Suite applications can be packaged.
No. Since Creative Cloud Packager 1.9.5, editing packages is not supported.
No. Business Catalyst and Adobe Fonts are services that do not have a desktop application to install. Your users can access Business Catalyst and Adobe Fonts from creative.adobe.com.
Yes, you can choose the applications and components you wish to install from the product you are packaging. You can also make multiple packages to allow you to easily manage who has what applications. When packaging products for delivery in Windows, you can choose 32-bit or 64-bit versions of the applications. For details, see Create packages.
Creative Cloud Packager does not perform an install; it creates a deployment package that records the install decisions an IT admin makes ahead of time. When creating a package using Creative Cloud Packager, you download the applications and their updates, configure product options, and generate a package in native installer formats (MSI or PKG).
Yes, Creative Cloud Packager supports physical media. For more information, see Physical Media Readme.
It is up to you and your company’s software deployment policies. Companies with locked down IT environments will want to use Creative Cloud Packager. Benefits include greater control, the ability to create custom packages, and the ability to select install options that may not be available to users when installing apps directly. It is also possible to leverage Creative Cloud Packager to just initially download the applications and deploy to your systems; this means each machine is not downloading the same bits multiple times, congesting your network. Once the software is on your users’ machines, they can manage it how they see fit, providing they have the permissions to do so.
Creative Cloud Packager should be used instead of AAMEE for packaging Creative Cloud applications. Log into creative.adobe.com to start using Creative Cloud Packager; a link can be found on the right hand side navigation bar of the Admin Console. For details, see Create packages.
There are two key differences. Creative Cloud Packager allows you to download the Creative Cloud apps directly from the cloud (as opposed to pointing to local, previously downloaded media from LWS or physical disks). Creative Cloud Packager will also be able to download feature-bearing updates, providing you with greater control.
Yes, you can have both AAMEE and Creative Cloud Packager on the same machine. However, you should not have any other Adobe products installed on the machine you are using to create the packages.
If you select the option from within the Creative Cloud Packager settings to disable updates, the Adobe Application Manager updating application will not be available to the end users. In this scenario, you can package updates via Creative Cloud Packager and hence have control over the distribution of updates. For details, see Create packages.
Creative Cloud Packager creates native packages that are designed to work with all industry-standard deployment solutions, including SCCM, ARD, JAMF Casper, Absolute Manage, and LANDesk.
Adobe is offering customers a choice when it comes to deploying Creative Cloud. You can either deploy centrally across your organization using Creative Cloud Packager, or allow your users to download the software on their own using the Creative Cloud for desktop app.
You can find help for Creative Cloud Packager in the Help documentation. You can also get help at the help forums.
When a package created with Creative Cloud Packager is deployed on an end-user computer, all available Visual C++ (VC) runtime versions are installed along with the products specified in the package. However, enterprise administrators can select the runtime versions that are installed on the end-user computers when a package is deployed.
The last version for the Creative Cloud Packager was 220.127.116.11 that was released on 24 July 2018. The Creative Cloud Packager is no longer in development and there will be no more updates.