Adobe Creative Cloud for Education Deployment Resources
Adobe Family of Deployment Tools for Enterprise
The enterprise deployment tools
Since the release of the Adobe Creative Cloud for Enterprise (CCE) and the Creative Cloud Packager for Enterprise (CCP) this past June, many institutions are preparing their images and applications for fall semester deployment. These tools are free and are used when deploying applications in the Enterprise. Information about these tools and links to these applications can be found at the URLs below and also on your Adobe Licensing Portal (LWS)In this post we will review the role of CCP and it associated tools. To make things easier, a list of resources follows at the end of this post.
Beginning with CS6 was released, Adobe has been hard at work in providing a more enterprise-friendly environment for packaging and provisioning the applications for deployment across the campus. The individual application installers are being standardized so that they can be packaged into either a .MSI file for Windows or a .PKG file for Mac. These common installer file types can distributed by any means that support them.
Changes to packaging process when deploying CCE
Unlike CS6, CCE packages must be packaged thorough the CCP dashboard. This is an application downloaded from the Adobe Licensing Portal (LWS). CCP will then pull the applications from the Adobe Cloud Server to the local IT admin machine where they can be serialized and packaged for distribution to the machines across campus. The advantage of this packaging is that the software will be pre-activated so that once placed on the destination machine, there will be no need to “phone home” periodically (as it does for named user installations like CC for individuals and Teams). This type of packaging and deployment is known as Anonymous (or machine-based deployment). Note: unlike CS6, there is no ability to enter serial numbers to the individual applications when used in the enterprise. They must be entered via the CCP tool or the Adobe Application Provisioning Tool (AAPT).
Some common methods for distribution include:
- Cloning image masters for replication on client machines using such tools as Casper, Ghost, and Apple Remote Desktop to name a few.
- Pushing these packages though Microsoft SCCM, Altiris, or ARD, for example
- When network access to the client machine is not practical. placing the package file on the computer desktop and double-clicking will extract it. You must then delete the package file.
Application exceptions when packaging with CCP
While most of the applications for CCE can be packaged with the CCP dashboard, there are still a few that have not bee standardized to run in the common packaging environment. Adobe is working on getting these applications into the CCP family, but until then these applications need to be installed differently.
As of this post, the exceptions are:
- Windows – LightRoom 5, Acrobat XI, Muse, and the Edge family of applications still under developer preview in Adobe Labs.
- Macintosh – Muse, and the Edge family of applications still under developer preview in Adobe Labs.
Working with Exceptions
Since there are still a few applications that fall outside of the CCP environment, these applications each have a slightly different procedure and requirement for proper deployment. The steps and requirements are available at http://tinyurl.com/ccpackager.
If you do not follow these steps, the apps under exception will not install properly. This includes installing as a trial, or not installing at all so please be sure to review the instructions and test prior to full deployment. The Community Forum is a good place to get more info and answers to specific problems. The Link for the CCE forum can be found here
In Enterprise environments where you are deploying many Acrobat XI installs, you may want to consider packaging Acrobat with the Acrobat Customization Wizard available as part of the Acrobat Enterprise Toolkit at http://tinyurl.com/acroetk. To use this tool, you will enter a separate Acrobat SN in LWS, not the SN supplied with the CC apps. Once the Packages are created they can be deployed as part of your normal distribution process.
Additional Resource Links
• CREATIVE CLOUD PACKAGER DOCUMENTATION
• CREATIVE CLOUD TECHNICAL REQUIREMENTS
• ENTERPRISE TOOLKIT FOR ACROBAT
• WHAT’S NEW IN CREATIVE CLOUD
• ENTERPRISE DEPLOYMENT WEBSITE
• LICENSING AND INSTALLATION BLOG