Introduction

Packages created with Adobe Creative Cloud Packager (CCP) contain two top-level folders, "Build" and "Exceptions". Installation of the software and license selection is possible using the file setup.exe in the "Build" folder for a majority of applications, but there are a small number of applications which are installed using a separate tool in the "Exceptions" folder, depending on when the package was created and which applications are included within it.

These instructions apply to packages created with version 1.9.3 and above of Creative Cloud Packager; this version was released on 21st January 2016.

Windows package installation

The following steps are requierd to install the applications within a CCP package, depending upon which applications were selected during package creation:

Acrobat XI

If the package contains Acrobat XI (the previous version of the application), it is necessary to install it using the file "ExceptionDeployer.exe" in the "Exceptions" folder. This can be achieved using the following command-line, replacing the final option as necessary depending on the installation language desired:

ExceptionDeployer.exe --workflow=install --mode=pre --installLanguage=en_US

Note: the language must be specified when installing Acrobat XI with the ExceptionDeployer. Further details on this option are available in the list of locales for different Acrobat configurations.

Primary applications, core services and license information

Applications located in the "Build" folder are installed using the file setup.exe in this folder. If the package contains Acrobat DC, this is also installed via the setup.exe; executing the MSI file will not install Acrobat DC.

The file setup.exe can be executed by double-clicking it, or in a script with the following syntax for silent execution:

setup.exe --silent

Note that this command-line option is only available in packages created since version 1.9.3 of CCP. Packages created prior to this date should be installed using the instructions here.

Additional applications in the "Exceptions" folder

A small number of applications need to be installed last. At the time of writing, these include Edge Code, Edge Reflow, Edge Inspect, Adobe Scout, Adobe Help and the Gaming SDK. Packages created prior to version 1.9.3 may place additional applicaitons in this folder; the complete list can be seen within the "Exceptions" folder in a given package.

Applications within the "Exceptions" folder aside from Acrobat XI can be installed using the following command: 

ExceptionDeployer.exe --workflow=install --mode=post

Example Windows installation script

The following example script can be used to deploy a package created with Creative Cloud Packager version 1.9.3 or above. It begins by closing conflicting applications such as the packager itself, installs Acrobat XI if it is present in the "Exceptions" folder, executes the setup.exe in the "Build" folder in silent mode, and then installs any applications in the "Exceptions" folder using the "ExceptionDeployer.exe" application.

Note that this script is just an example, and has not been extensively tested. It should be executed on a test system first to ensure compatibility and may result in data loss if the system is being used at the time of execution, because of the fact it closes certain applications before starting.

The example script can be downloaded from here.

Mac OS X package installation

Installation of a package on Mac OS X can be performed using the "installer" command, which is part of the operating system and provided by default by Apple. The name of the package itself should be cited in the command line, using either a relative or absolute path as in the examples below from the terminal. Any spaces in the package name should be escaped with the backslash character. By default, the target is the root of the filesystem, as opposed to an alternative disk on which a package might be installed:

cd build

sudo /usr/sbin/installer -pkg ./Edge\ Animate\ CC2015\ Mac_Install.pkg -target /

Note that in some circumstances there may be packages in the "Exceptions" folder which will need installing in a similar manner. This is discussed in further detail in this document.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy