Important:

The following procedures enable you to you create Windows or Mac OS packages (MSI or PKG files). You can then use any third-party deployment tool that supports the deployment of native installers (for example Microsoft SCCM, Apple ARD, or JAMF Casper Suite) to deploy the packages to client computers.

Follow this sequence to create and deploy packages with Adobe Creative Cloud Packager:

Step 1: Download Creative Cloud Packager

Download Adobe Creative Cloud Packager from the Adobe Licensing Website (LWS) or Enterprise Dashboard.

Important:

  • It's necessary to use the most recent version of the Creative Cloud Packager to create Photoshop Elements or Premiere Elements deployment packages.
  • Don't install Creative Cloud Packager on a computer 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 computer. However, they should not be running simultaneously for package creation.

Step 2: Create or Edit a package

To create packages using Adobe Creative Cloud Packager, perform the following steps: 

  1. Run Adobe Creative Cloud Packager downloaded in step 1.

    • (Windows) Click the shortcut for the application in the Start menu, under Programs > Adobe > Creative Cloud Packager.
    • (Mac OS) Use the alias at /Applications/Adobe/Creative Cloud Packager.

    Important: You must run Creative Cloud Packager as an Administrator on the computer you are building packages on.

  2. Select an account type for your Photoshop Elements 13 or Premiere Elements 13 product from the options:

    • Administrator for Enterprise Term License Agreement (ETLA)
    • Education Enterprise Agreement (EEA)
    • Government customer

    Select an account type
  3. Sign in with your Adobe ID and password. Use a standard Adobe ID.

  4. After signing in, the Create or Edit Package screen appears. Do one of the following:

    • Click Create Package to start the package creation process.
    • Click Edit Package to modify an existing package, and then browse to an existing .ccp file. The .ccp file is located in the same location as the existing package.
    • Click Create License File. For more information, see Create license file.
    Create or Edit Package screen
  5. In the Package Details screen that appears after selecting Create Package, enter the required details:  

    Enter package details

    Required details:

    Package name

    Enter the name of the package that will be created.

    Save to

    Enter the location to which you want to save the package you create. You can
    Click the Browse icon to locate the destination folder, or enter the absolute path.

    32 bit/64 bit

    In Windows, choose 32-bit or 64-bit processor support. Make
    separate packages for 32-bit and 64-bit installations. A 32-bit package will not run on a
    64-bit machine.

    License type

    Choose Serial Number License for PSE13 and PRE13

    Package configurations

    The settings for package configuration include options such as whether to ignore conflicting processes during installation. To review or change the package configuration settings, click Change, and modify settings in the Advanced Configurations screen.

    Click Next.

  6. On the Enterprise Customers Only screen, enter a Volume Serial Number. (5)

    Enter a volume serial number
  7. On the Application and Updates screen, select the products or updates that you want to include in the package.

    Show archived versions

    By default, only the latest versions of the software are displayed. Enable Show Archived Versions to display a list of archived applications. You can package archived versions of software as well.

    If the product or update that you selected has already been downloaded to your machine, a down arrow appears next to its name.

    Language

    You can also select the language you want to package in by using the drop-down list in the upper-right corner.

    Add Offline Media

    To add applications and updates from a local source, such as a DVD or ESD, instead of downloading from Adobe.com, click Add Offline Media. Browse to the location where the offline media is located. On a Mac, place the DMG file in a directory and browse to that directory. Select the products and updates to package.

    Note: Use media provided by Adobe or downloaded from the Adobe website to ensure that it is not corrupt and does not contain malicious code.

    Click Done to return to the Application & Updates screen. (6)

    Applications & Updates screen

    Note:

    Ensure that the target devices meet the system requirements of the apps being packaged. Deploying apps on unsupported systems can give unexpected results.

  8. Click Build to start packaging the selected applications and updates.

    The Adobe Creative Cloud Packager downloads the products and/or updates that have not been downloaded already to your machine. It then builds the package. The progress is displayed on the Download Progress and the Build Progress screens. (7)

    Creative Cloud Packager progress screen
  9. When the build completes successfully, the Summary page appears.

    You can click the Build Log link to see the detailed progress report, including any errors. (8)

    Note:

    When you create a package, Adobe Creative Cloud Packager creates a configuration file for the package with the name <package_name>.ccp. This file is located in the folder that you specify for the package. This configuration file is for internal use only; do not modify or delete this file.

    Summary page
  10. Do one of the following:

    • To create another package or edit this package, click Main Menu to return to the Welcome screen.
    • To exit Adobe Creative Cloud Packager, click Close.

Step 3: Deploy a package

As part of the build process, two folders are created:

  • The Build folder contains the MSI (Windows) or the PKG (Mac OS) files.
  • The Exceptions folder contains the payloads that must be installed separately.

For information on how to deploy the packages, see Deploy packages.

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