Introduction

Named user licensing is the default and most popular licensing method to deploy and use Adobe Creative Cloud and Document Cloud products. Designed for the network-connected scenario where app licenses are managed based on individual user need for use of the app. Using named user licensing, you can provide your end users with the full functionality of the software and services. Giving your end-users access to all the available apps and services based on your organization's entitlements.

 For more details, see the Licensing overview article.

Types of Named User Licensing packages

Self-service packages

Like millions of Adobe users, you can allow your creatives to install applications and updates via the Creative Cloud Desktop application. It reduces IT overhead and ensures that your creatives have access to all the tools they need and receive updates when they are released.

Create Self-Service packages

If you want to enable self-service even if your end users do not have administrative privileges, you can do one of the following:

  • Create a Self-Service package
  • Create a Managed Package with elevated privileges turned on
  • Create a package based on an Adobe Template with elevated privileges turned on

Use this package to give your users complete control of the Adobe applications and updates that they can download and install. If your users do not have Administrator credentials to manage applications and updates, then you can create a Self-Service package for them.

  1. Log in to the Admin Console and navigate to Packages > Packages.

    The list of available packages is displayed.

  2. Click Create a Package.

    List of packages
  3. Choose Self-Service Package and click Select.

    Self-Service Package
  4. Enter a package name and select the required options:

    Platform: Choose the operating system and the processor support (32 bit or 64 bit). It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't run on a 64-bit machine.

    Language: Select the language in which you want to create the package.

    Use OS Locale: Enables you to create a package that deploys in the OS language of client machine. In which case, the OS language is the default fallback language in which the package is deployed.

    Create a folder for extensions & include the Extension Manager command line tool: Enables you to create a subfolder in your package folder that you can use to include extensions that you want to install with the package. For more, see Manage Extensions in packages.

    Redirect to internal update server: Enables you to redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. For more, see the Preferences section of the Packaging apps through the Admin Console.

  5. Click Build package.

    The Packages page is displayed. You can check the progress of the build in the list of packages.

    A message is shown after the build process is over. If the package is built successfully, the message also indicates the period for which the package is available for download from the Admin Console.

    Validity of Self-Service package

    If you want to check the remaining time for the existing packages in the details pane, click the row item for the package.

  6. In the Save As dialog box, choose a location on your computer to save the package.

  7. To download and distribute the package later, click the package name in the list of packages and then click Download in the right pane.

Managed packages

Using Managed packages, you can decide what gets deployed and when it gets updated. You can create the packages that contain the latest or archived versions of Adobe products. You can then deploy these packages to the user's computers in your organization. You can even perform silent and custom deployment where no inputs are required from your users during installation.

Create Managed packages

If you plan to use Managed packages, you can:

  • Create a Managed Package with elevated privileges turned on.
  • Create pre-configured packages using  Adobe Templates.
  • Create customized packages with the configuration and applications you want your end users to have.

Use this package to maintain greater control of the Adobe applications and updates that your users can install.

See this page for a detailed list of Adobe products that can be packaged using this method.

Примітка.

To create packages that include products such as Adobe Captivate and Presenter that are not part of either Creative Cloud or Document Cloud, you can customize the available Adobe Templates. You cannot use the following procedure.

  1. Log in to the Admin Console and navigate to the Packages > Packages.

    The list of available packages is displayed.

    If you have not created any packages as yet, you are presented with the following screen to help you get started.

    First time experience
  2. Click Create a Package.

    List of packages
  3. Choose Managed Package and click Select.

    Managed package
  4. On the Configure screen, select or enable the required options:

    • Platform: Choose the operating system and the processor support (32 bit or 64 bit).
      Note: It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't be deployed on a 64-bit machine. Also, A 64-bit package can't be deployed on a 32-bit machine.
    • Language: Select the language in which you want to create the package.
    • Use OS Locale: Enable to create a package that deploys in the OS language of client machine. In which case, the OS language is the default fallback language in which the package is deployed.
  5. Click Next.

    Примітка.

    If you add a product that has dependent products, the dependent product is added automatically. For example, if you add Photoshop CC, Camera Raw CC and Adobe Preview CC are added automatically. You can, however, choose to remove the dependent products.

  6. On the Choose Apps screen, click the Plus icons next to the corresponding applications to include them in the package, and then click Next.

    CreatePackages_Managed_ChooseApps_New

    Примітка.

    To display the list of previous versions of the apps under Available applications, select the Show older versions check box.

  7. On the Options screen, select or enable the required options and then click Next.

    Creative Cloud Desktop Options:

    • Show apps panel: Enable or disable the option to display or hide the Apps panel in Creative Cloud desktop application for end users. Enabling or disabling the Apps Panel automatically enables or disables the updates on the client machines respectively.
    • Allow non-admin to update and install apps: Enables the self-service end users, who do not have Administrative privileges, to install and manage their applications and updates.
    • Disable file syncing: Suppress the automatic syncing of files to client systems. Useful when you are installing packages in a test environment where you want to suppress file syncing. Available only to educational institutions.

    Management Options:

    • Enable Remote Update Manager: Enables the use of Remote Update Manager. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. For more information, see Remote Update Manager.
    • Redirect to internal update server: Enables you to redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console article.
    • Create a folder for extensions & include the Extension Manager command line tool: Enables you to create a subfolder in your package folder that you can use to include extensions that you want to install with the package. For more, see Manage Extensions in packages.
    • Install package to custom install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console article.
  8. On the Finalize screen, enter the name of the package, ann then click Build Package.

    You can also review the included applications and configuration for this package before building the package.

    CreatePackages_Managed_Finalize_New

    It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.

    If you want to check the remaining time for the existing packages in the details pane, click the row item for the package.

  9. In the Save As dialog box, choose a location in your computer to save the package.

  10. To download and distribute the package later, click anywhere on the row for the required package and then click Download in the package details drawer.

Acrobat-only packages

If your organization has a Document Cloud-only entitlement on the Admin Console, you can create Acrobat-only packages.

Create Acrobat-only packages

  1. Log in to the Admin Console and navigate to the Packages > Packages.

  2. Click Create a Package.

  3. Enter a package name and select the required options.

    Create Acrobat only package

    Platform:

    Choose the operating system and the processor support (32 bit or 64 bit).
    Note: It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't be deployed on a 64-bit machine. Also, A 64-bit package can't be deployed on a 32-bit machine.

    Language:

    Select the language in which you want to create the package.

    Enable Remote Update Manager:

    Enables you to run the updater remotely on the client machine with the benefit of executing as an administrator. For more information, see Remote Update Manager.

  4. Click Build Package.

    It displays the Packages page. You can check the progress of the build in the list of packages.

    It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.

    Validity of Acrobat-only package
  5. In the Save As dialog, choose a location on your computer to save the package.

  6. To download and distribute the package later, click the package name in the list of packages and then click Download in the right pane.

Use Acrobat Customization Wizard

After you have created your Acrobat-only packages or packages that include Acrobat as one of the products using the procedures described in this document, you can use the Adobe Customization Wizard to further customize your package.

The wizard streamlines the task of customizing or configuring Acrobat features and app in the installer earlier to its organization-wide deployment.

Creative Cloud Packager

Use Creative Cloud Packager to create custom packages when you require licensing other than named, for example device licensing.

Download Creative Cloud Packager

Увага!

Creative Cloud Packager does not support apps version CC 2019 or later. Learn More.

You need to review the system requirements before you download and install Creative Cloud Packager.

  1. Log in to the Admin Console and navigate to Packages > Tools & notifications.

  2. In the Creative Cloud Packager tile, download Creative Cloud packager based on your operating system.

    Choose Creative Cloud Packager

For more information on creating and deploying packages using Creative Cloud Packager, see the Packaging User Guide.

Цей документ захищено ліцензією Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Публікації Twitter™ і Facebook не підпадають під умови ліцензії Creative Commons.

Юридична інформація   |   Політика мережевої конфіденційності