Overview

This document provides some best practices and additional information for deploying Creative Cloud for enterprise in an educational institution environment. For comprehensive deployment documentation, see the main documentation page for Creative Cloud Packager. Creative Cloud for enterprise deployment requires more technical skill and knowledge than previous Creative Suite products. Adobe recommends, therefore, that IT personnel perform all Creative Cloud for enterprise installations.

Prerequisite knowledge and skills required

For a successful deployment of Creative Cloud for enterprise, Adobe recommends the following prerequisite knowledge and skills:

  • Knowledge of software installation in general and the system installation tool (msiexec on Windows, Installer on Mac OS).
  • Knowledge of elevated permission implementations and admin user rights, including User Account Control on Windows and usage of the sudo command on Mac OS.
  • Familiarity with the system command-line interpreter (Command Prompt on Windows, Terminal on Mac OS), understanding of the system command shell, understanding of how to format and enter command-line instructions with appropriate parameters, and how to navigate the system directory structure with the command shell.
  • Knowledge of the managed deployment system, if one is being used.
  • Reading the following documents in the Packager documentation:
  • Understanding how to navigate the system directories both with the graphical shell (Windows Explorer, Finder) and the command shell.

Scenario 1: IT-managed deployment

This scenario involves deploying Creative Cloud for enterprise with a managed deployment solution. Common solutions include:

Windows: SCCM (System Center Configuration Manager, OS vendor supplied) or third party

Mac OS: ARD (Apple Remote Desktop, OS vendor supplied) or third party (commonly: JAMF Casper Suite)

Scenario 2: Image and clone deployment

This scenario involves installation of Creative Cloud for enterprise on a target machine that has its disk imaged with a cloning solution. Then, that cloned image is replicated on a number of similar machines. This method is sometimes referred to as ghosting after one of the common solutions for this workflow, Symantic Ghost Solution suite.

  1. Prepare a Creative Cloud for enterprise package. See Create or edit packages.
  2. If the users are going to self-manage updates, change the package update setting to Admin Users Update Via Adobe Update Manager.
  3. Deploy the package onto the target machine. IMPORTANT: do not launch the applications until after the cloning process has completed!

You may need to deploy exceptions separately. See the Exceptions Deployer section below.

  1. Clone the target machine to a test machine.
  2. Test the cloned deployment. If you don't encounter any issues, proceed with mass deployment of the cloned image.

Scenario 3: Self-managed deployment

Setup file for Windows
Setup executable on Windows
Mac executable
Executable on Mac OS (same name as package)

This scenario involves distributing a package created with the Creative Cloud Packager to end users for self-deployment.

Note: The installation of Creative Cloud for enterprise requires technical IT knowledge. Therefore, Adobe recommends that IT staff install the product for the end user, or at a minimum be available to the end user who needs the package.

  1. Set the packager update setting to Admin Users Update Via Adobe Update Manager.
  2. If end users will install your package, create an alias of the installer (setup.exe on Windows, .pkg file on Mac OS with the same name as your package) in the top level of the package folders. You may want to name this alias descriptively such as "Double-click to install."
  3. After creation of the deployment package, move it to the medium that the end user will use to access the package. A full Creative Cloud deployment is too large to fit on DVD media, but you can break it up. You can also use network shares or USB drives.
  4. If necessary, run the Exceptions Deployer in the "pre" mode. See the Exceptions Deployer section below.
  5. Install the main installation package.
  6. If necessary, run the Exceptions Deployer in the "post" mode. See the Exceptions Deployer section below.
  7. Serialized packages that do not use a named deployment model must be tracked centrally by your organization, as Adobe does not have a method for reporting on these deployments. Follow your organization's standard to indicate what products have been deployed to the end user.

Exceptions Deployer

Due to differences in installation methods, not all Adobe products can be deployed with the primary deployment package. Adobe provides the Exceptions Deployer tool to assist with the installation of these products. The Exceptions Deployer is a command-line interface utility and requires knowledge of using the system shell to be successful. Therefore, Adobe recommends that IT personnel perform these steps.

Exceptions Deployer "pre" mode and Acrobat installation (Windows)

Packages for Windows containing Adobe Acrobat Professional need to have the Exceptions Deployer run in the pre-installation mode. This step is not required on the Mac platform.

Change the "en_US" parameter to the correct parameter for your language. (For details see the parameters section of the Acrobat Enterprise Deployment Guide.) You can place this command in a batch file.

  • Run this command with elevation. For Windows, start an elevated command prompt. For Mac OS, see instructions for the sudo terminal command.
  • On the command line or batch file, use the proper folder self-reference (for example, %~dp0) 
 

Exceptions Deployer "post" mode (Windows)

After the installation of the primary .msi  (Windows), run the Exceptions Deployer in the "post" installation mode if required to complete installation of products that cannot be wrapped into the main package.

You can place this command in a batch file.

  • Run the command with elevation. For Windows, start an elevated command prompt. For Mac OS, see instructions for the sudo terminal command.
  • On the command line or batch file, use the proper folder self-reference (for example, %~dp0).

AIR Components (Mac OS)

On Mac OS, instead of Exceptions Deployer, there are separate .pkg files for AIR components that require separate installation if the "Disable AIR components" option was not selected in the Creative Cloud Packager settings.

Support

If you need assistance with these instructions, or encounter problems with your deployment, open a support ticket on the Admin Console Support tab.

تم ترخيص هذا العمل بموجب الترخيص العام غير المعدل الخاص بالإسناد وعدم التجارة والمشاركة الإصدار 3.0 ‏من ‏‏Creative Commons‏‏  إن بنود Creative Commons لا تشمل منشورات Twitter™‎ وFacebook.

إشعارات قانونية   |   سياسة الخصوصية على الإنترنت