Creating named license packages

Run Adobe Creative Cloud Packager.

• (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.

Select your account type.

Sign in with your ID and password.

If you are a Creative Cloud for team customer, you must use an ID that has been specified as an administrator for your team. If you are a Creative Cloud for enterprise customer, use an Enterprise ID or a standard Adobe ID. For more information on Enterprise ID, see Enterprise ID, sign in, and account Help.

After you have successfully signed in, the Create Package screen appears.

Note: To specify preferences for download location for products, clear the cache, or view help on Creative Cloud Packager, see Edit and save configurations.

In the Create Package screen, do one of the following:

• Click Create Package to start the package creation process.
  

• Click Create License Package. For more information, see Create license package.

In the Package Details screen that appears, enter the required details.

Enter the name of the package that is created.

Select the organization for which you want to create the package. Only members of the selected organization in the Adobe Admin Console, can view and access the package. 

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.

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

Select Named License. This option creates a package that is licensed when the user signs in.

Named Licensing allows users to sign in if they want to license the products they use. This enables members to access Creative Cloud services and gives administrators more visibility into activations. If no user has signed in to license a product, the usage is considered to be trial usage and lasts for 30 days.

As an administrator, you can send your users an invitation to join the team. Once they receive the invitation, they will be able to sign in and license the applications you have deployed to their systems. They will also be able to access Creative Cloud services. The admin portal will be updated to reflect the product activation status.

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. The Advanced Configurations screen appears. For more information, see Modify package configuration.

Adobe Creative Cloud for desktop is the central hub for Creative Cloud activity and allows the users to view applications and updates. For named license, Creative Cloud desktop app is always enabled.

To create a package that contains only the Creative Cloud for desktop app, do not select any Applications or Updates in the subsequent screens.

This option is applicable only when Creative Cloud desktop app is enabled. When disabled, this option hides the apps panel in Creative Cloud desktop app for end-users.

Selecting or deselecting this option results in the following changes to the options in the Advanced Update Manager Behavior section of the Advanced configurations dialog:

You can also retrospectively enable the Apps panel. For more information, see Customize Creative Cloud app for desktop.

This option allows users to manage applications and updates even when they do not have Administrator privileges. To allow your users without Administrator credentials to manage applications and updates, select this option.

Once you have deployed a package with elevated privileges, to revoke the elevated privileges later, you need to create a Creative Cloud desktop app-only package with Elevated Privileges deselected and deploy it. Similarly, to grant elevated privileges to existing users, you need to create a Creative Cloud desktop app only package with Elevated Privileges selected and deploy it.

The Elevated Privileges option is available only when you have selected Show Applications And Updates Via The Apps Panel.

The Applications and Updates screen appears.

Select the products and/or updates that you want to include in the package. For example, you might choose to include the Adobe^® Photoshop^® software and all it updates, as well as (only) the updates for Adobe^® InDesign^®. Select the checkboxes appropriately.

Creative Cloud is always selected, and you cannot deselect it. This option deploys the common licensing infrastructure to client machines. To create a package that only contains the Creative Cloud for desktop app, enable Adobe Creative Cloud from the Package's Advanced Configurations screen. 

You can package archived versions of software as well. Select the Show archived versions check box to display the list of supported previous versions, if any. If the product or update that you selected has already been downloaded to your machine, a Down Arrow appears next to its name.

You can also select the language you want to package in, using the drop-down list on the upper-right side.

Select Match OS language to create just one package that adapts to the client machine's OS language. 

The language in which the package is installed depends on three factors:

• Whether Match OS Language option is selected while creating the package.
• The language you specify in the command while deploying the package.
• The language in which you have created the package.

The following table details how each of these factors affects the language in which the package is installed.

When you package an update for the latest version of some of the applications, you can apply the package to a system that does not already have the base version of the application installed. You can identify such apps with the icon ().  For a list of such applications, see Applications that can be deployed without their base versions.

For example, the update of Photoshop CC 2015.0.1 could be installed on a client machine that already had base version of Photoshop CC 2015 installed. The latest version of Photoshop update can be installed on a machine that may not have the Photoshop base version. So while creating a package, you can choose to package only the update version for the apps that can be deployed without their base versions.

To add applications and updates from a local source, such as a DVD or ESD, instead of downloading from the Creative Cloud, click Add offline media. 

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.

When the build completes successfully, the Summary page appears.

• This page displays a summary of the products or components included in the build. The name of the folder in which the package is created is displayed on the screen. Clicking the folder name opens the folder.
• Click the Build Log link to see the detailed progress report, including any errors.
  
• Enterprise customers only: Packages created using Created Cloud Packager are listed in the Admin Console, so that all Admins can view and track packages across the organization.

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.

To create another package, click Main Menu — this takes you back to the Welcome screen. To exit Adobe Creative Cloud Packager, click Close.