User Guide Cancel

Create Named User Licensing Packages

Search
  1. Adobe Enterprise & Teams: Administration guide
  2. Plan your deployment
    1. Basic concepts
      1. Licensing
      2. Identity
      3. User management
      4. App deployment
      5. Admin Console overview
      6. Admin roles
    2. Deployment Guides
      1. Named User deployment guide
      2. SDL deployment guide
      3. Deploy Adobe Acrobat 
    3. Deploy Creative Cloud for education
      1. Deployment guide
      2. Approve Adobe apps in Google Admin Console
      3. Enable Adobe Express in Google Classroom
      4. Integration with Canvas LMS
      5. Integration with Blackboard Learn
      6. Configuring SSO for District Portals and LMSs
      7. Deploy Adobe Express through Google App Licensing
      8. Add users through Roster Sync
      9. Kivuto FAQ
      10. Primary and Secondary institution eligibility guidelines
  3. Set up your organization
    1. Identity types | Overview
    2. Set up identity | Overview
    3. Set up organization with Enterprise ID
    4. Setup Azure AD federation and sync
      1. Set up SSO with Microsoft via Azure OIDC
      2. Add Azure Sync to your directory
      3. Role sync for Education
      4. Azure Connector FAQ
    5. Set up Google Federation and sync
      1. Set up SSO with Google Federation
      2. Add Google Sync to your directory
      3. Google federation FAQ
    6. Set up organization with Microsoft ADFS
    7. Set up organization for District Portals and LMS
    8. Set up organization with other Identity providers
      1. Create a directory
      2. Verify ownership of a domain
      3. Add domains to directories
    9. SSO common questions and troubleshooting
      1. SSO Common questions
      2. SSO Troubleshooting
      3. Education common questions
  4. Manage your organization setup
    1. Manage existing domains and directories
    2. Enable automatic account creation
    3. Set up organization via directory trust
    4. Migrate to a new authentication provider 
    5. Asset settings
    6. Authentication settings
    7. Privacy and security contacts
    8. Console settings
    9. Manage encryption  
  5. Manage users
    1. Overview
    2. Administrative roles
    3. User management techniques
      1. Manage users individually   
      2. Manage multiple users (Bulk CSV)
      3. User Sync tool (UST)
      4. Microsoft Azure Sync
      5. Google Federation Sync
    4. Change user's identity type
    5. Manage user groups
    6. Manage directory users
    7. Manage developers
    8. Migrate existing users to the Adobe Admin Console
    9. Migrate user management to the Adobe Admin Console
  6. Manage products and entitlements
    1. Manage products and product profiles
      1. Manage products
      2. Manage product profiles for enterprise users
      3. Manage automatic assignment rules
      4. Review product requests
      5. Manage self-service policies
      6. Manage app integrations
      7. Manage product permissions in the Admin Console  
      8. Enable/disable services for a product profile
      9. Single App | Creative Cloud for enterprise
      10. Optional services
    2. Manage Shared Device licenses
      1. What's new
      2. Deployment guide
      3. Create packages
      4. Recover licenses
      5. Manage profiles
      6. Licensing toolkit
      7. Shared Device Licensing FAQ
  7. Manage storage and assets
    1. Storage
      1. Manage enterprise storage
      2. Adobe Creative Cloud: Update to storage
      3. Manage Adobe storage
    2. Asset migration
      1. Automated Asset Migration
      2. Automated Asset Migration FAQ  
      3. Manage transferred assets
    3. Reclaim assets from a user
    4. Student asset migration | EDU only
      1. Automatic student asset migration
      2. Migrate your assets
  8. Manage services
    1. Adobe Stock
      1. Adobe Stock credit packs for teams
      2. Adobe Stock for enterprise
      3. Use Adobe Stock for enterprise
      4. Adobe Stock License Approval
    2. Custom fonts
    3. Adobe Asset Link
      1. Overview
      2. Create user group
      3. Configure Adobe Experience Manager Assets
      4. Configure and install Adobe Asset Link
      5. Manage assets
      6. Adobe Asset Link for XD
    4. Adobe Acrobat Sign
      1. Set up Adobe Acrobat Sign for enterprise or teams
      2. Adobe Acrobat Sign - Team feature Administrator
      3. Manage Adobe Acrobat Sign on the Admin Console
    5. Creative Cloud for enterprise - free membership
      1. Overview
  9. Deploy apps and updates
    1. Overview
      1. Deploy and deliver apps and updates
      2. Plan to deploy
      3. Prepare to deploy
    2. Create packages
      1. Package apps via the Admin Console
      2. Create Named User Licensing Packages
      3. Adobe templates for packages
      4. Manage packages
      5. Manage device licenses
      6. Serial number licensing
    3. Customize packages
      1. Customize the Creative Cloud desktop app
      2. Include extensions in your package
    4. Deploy Packages 
      1. Deploy packages
      2. Deploy Adobe packages using Microsoft Intune
      3. Deploy Adobe packages with SCCM
      4. Deploy Adobe packages with ARD
      5. Install products in the Exceptions folder
      6. Uninstall Creative Cloud products
      7. Use Adobe provisioning toolkit enterprise edition
      8. Adobe Creative Cloud licensing identifiers
    5. Manage updates
      1. Change management for Adobe enterprise and teams customers
      2. Deploy updates
    6. Adobe Update Server Setup Tool (AUSST)
      1. AUSST Overview
      2. Set up the internal update server
      3. Maintain the internal update server
      4. Common use cases of AUSST   
      5. Troubleshoot the internal update server
    7. Adobe Remote Update Manager (RUM)
      1. Use Adobe Remote Update Manager
      2. Resolve RUM errors
    8. Troubleshoot
      1. Troubleshoot Creative Cloud apps installation and uninstallation errors
      2. Query client machines to check if a package is deployed
      3. Creative Cloud package "Installation Failed" error message
    9. Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
      1. About Creative Cloud Packager
      2. Creative Cloud Packager release notes
      3. Application packaging
      4. Create packages using Creative Cloud Packager
      5. Create named license packages
      6. Create packages with device licenses
      7. Create a license package
      8. Create packages with serial number licenses
      9. Packager automation
      10. Package non-Creative Cloud products
      11. Edit and save configurations
      12. Set locale at system level
  10. Manage your account
    1. Manage your Teams account
      1. Overview
      2. Update payment details
      3. Manage invoices
      4. Change contract owner
      5. Change reseller
    2. Assign licenses to a Teams user
    3. Add products and licenses
    4. Renewals
      1. Teams membership: Renewals
      2. Enterprise in VIP: Renewals and compliance
    5. Automated expiration stages for ETLA contracts
    6. Switching contract types within an existing Adobe Admin Console
    7. Purchase Request compliance
    8. Value Incentive Plan (VIP) in China
    9. VIP Select help
  11. Reports & logs
    1. Audit Log
    2. Assignment reports
    3. Content Logs
  12. Get help
    1. Contact Adobe Customer Care
    2. Support options for teams accounts
    3. Support options for enterprise accounts
    4. Support options for Experience Cloud

With the release of Creative Cloud desktop app v5.10, the support for Creative Cloud desktop verisons is now updated. For details, see the new Support matrix.

Introduction

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

Learn about the various options to deploy and deliver apps and updates to your end users.

Acrobat Classic version can now be included in Named User Licensing packages. This will provide customers with a stable release Acrobat version that provides the ability to limit feature updates while still receiving security and platform enhancements. For more, see Document Cloud Product Tracks.

Create and manage packages, deploy updates, and troubleshoot installation errors | YouTube video

Self-service packages

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

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.

Note:

Using the Creative Cloud desktop app, your end users can install only the two most recent major versions of Creative Cloud apps. For end users who require older versions, create and deploy Managed packages.

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

  2. Click Create a Package.

  3. Choose Self-Service Package and click Next.

    Self-Service Package

  4. Enter a package name and select the required options:

    • Choose a Platform: Choose the operating system and the processor support from the following:
      • macOS (Universal)
      • macOS (Intel)
      • macOS (Apple Silicon)
      • Windows (64-bit)
      • Windows (32-bit)
      • Windows (ARM)
    Note:

    A package made for one operating system and architecture type, cannot be deployed on another.

    • It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.
    • It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices. Alternatively, you can create a macOS (Universal) package, and use this to install apps on both macOS (Intel) and macOS (Apple Silicon) machines.

     

    Note:

    If you choose a macOS platform, you can create flat packages. This option is selected by default. For more details, see Creating flat packages.

    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.

    (Not currently available for Windows ARM devices) Create a folder for extensions & include the Adobe Extension Manager command-line tool: Enables you to create a subfolder in your package folder. In the subfolder, you can 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.

    Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop app. This means that end users can then go to the Creative Cloud desktop app, and install or update these apps. Learn more.

  5. (Applies to packages for the macOS platform only) 

  6. Click Create 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.

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

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

  8. To download and distribute the package later, click Download for the required package.

Caution

If the package that you've created contains one or more revoked apps, the status displays as Revoked. Also, you cannot download this package.

Revoked package

The downloaded package file is a .zip file format.

If you double-click to unzip the package file, you may encounter the following, Unable to expand error on macOS 10.14 and prior versions.

This is because the macOS Archive Utility does not support the unzipping of large files that are zipped using the Zip64 mode.

Error 1 - Operation not permitted

To unzip the file, open the terminal in the folder where you've downloaded the file and run the unzip command:

unzip <file name>.zip

Packageinfo.txt

The package that you download, contains a Packageinfo.txt file. This file has the information such as the following about that package:

  • Package Name
  • Package Type - Self Service or Managed
  • Platform
  • Locale
  • Creative Cloud desktop app version
  • Package Configurations
    • Remote update manager - Enabled or Disabled 
    • App Panel - Enabled or Disabled
    • Beta App Download - Enabled or Disabled
    • Browser Based Auth - Enabled or Disabled
    • Files Panel - Enabled or Disabled
    • Market Panel - Enabled or Disabled
    • Use OS Locale - Enabled or Disabled

The PackageInfo.txt file is for informational purposes only.

Managed packages

With 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.

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 that contain any one or more of the following:
    • Adobe apps and services
    • Configuration options
    • Marketplace plugins

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

Note:

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

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

  2. Click Create a Package.

  3. Choose Managed Package and click Next.

    Managed package

  4. On the Configure screen, select the required options:

    • Choose a Platform: Choose the operating system and the processor support from the following:
      • macOS (Universal)
      • macOS (Intel)
      • macOS (Apple Silicon)
      • Windows (64-bit)
      • Windows (32-bit)
      • Windows (ARM)
    Note:

    A package made for one operating system and architecture type, cannot be deployed on another.

    • It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.
    • It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices. Alternatively, you can create a macOS (Universal) package, and use this to install apps on both macOS (Intel) and macOS (Apple Silicon) machines.

     

    • Language: Select the language in which to create the package.
    • Use OS Locales: Enable this option to create a package that deploys in the OS language of client machine. The OS language is the default fallback language in which the package is deployed.

  5. Click Next.

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

    Click Next on this step if you need to create a lightweight package (without Adobe apps) that includes either or both of the following:

    • Configuration options
    • Marketplace plugins
    Choose applications

    Note:

    If you deploy an application which has special system requirements on an unsupported machine the installer will fail. If required, see the system requirements for the application you are installing.

    Optionally, you can filter down the list of Available Applications to choose from.

    Latest versions: Display the latest version of all available applications.

    Long-term supported versions: Display Adobe's long-term supported versions.

    Beta apps: Display available beta apps. Learn more.

    Older versions: Display a list of previous versions of the apps. View versions that don't receive security or feature updates.

    Filter available applications

    Optionally, you can filter down the list of Available Applications to choose from.

    Latest versions: Display the latest version of all available applications.

    Long-term supported versions: Display Adobe's long-term supported versions. To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy. 

    Beta apps: Display available beta apps. Learn more.

    Older versions: Display a list of previous versions of the apps. View versions that don't receive security or feature updates.

    Filter available applications

    App Add-ons: Certain Adobe apps come with Add-ons. So, when you add an app that includes one or more Add-ons, you have the option to include the add-ons in the package you're creating. By default, Add-ons are not included in the package.

    App Add-ons

  7. (Not currently available for Windows ARM devices) On the Choose Plugins screen, search and select plug-ins to include in the package, and click Next.

    You can select the Show Compatible Plugins Only check box to display the plug-ins that are compatible with the apps in the package. This filter doesn't appear if you only have the Creative Cloud desktop app in your package.

    To view the list of selected plug-ins, click Selected Plugins.

    Note:

    The plug-ins that you include in the package do not necessarily need the supporting application to be part of the same package. You can include plug-ins and extensions for apps that are previously installed on your users' computers. Also, if a computer does not have the targeted application for a plug-in, the plug-in is not installed on the computer.

    Choose plugins

  8. On the Options screen, choose the required options and select Next.

    If you've not selected any apps and have selected one or more plugins, then you have the following options:

    • Create a plugin-only package by keeping the Configuration Options turned off.
    • Create a plugin and configuration package by turning the Configuration Options on.

    To create a configuration-only package, no apps or plugins should be selected. In this case, the Configuration Options switch will not be available, and the Configuration Options screen will be visible.

    Creative Cloud Desktop Options:

    • Enable self-service install: Allow users to install and update applications from Apps panel in the Creative Cloud desktop app. Learn more.
    • Allow non-admin to update and install apps: Enable self-service for end users who do not have administrative privileges, to install, and manage their applications and updates. Learn more.
    • Disable auto-update for end users: Ensure that end users will not be able to automatically update their applications via the Creative Cloud desktop app. Learn more.
    • Enable self-service plugin install: Allow end users to install and update plug-ins from the Marketplace tab in Creative Cloud desktop app. If deselected, the users can't browse or install any plug-ins using the Creative Cloud desktop app. Whenever you toggle this option, users must quit and relaunch. Alternatively, they must sign out and sign back into the Creative Cloud desktop app for the changes to reflect. Learn more.
    • 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. Read more on disabling file syncing. This option is available for Creative Cloud subscribers in commercial and educational organizations only. It is not available for subscribers in government organizations.
    • Enable browser-based login: By default, users must sign in using the Creative Cloud desktop app. Choose this option to redirect users to sign in via the browser. Learn more.
    • Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop app. This means that end users can then go to the Creative Cloud desktop app and install or update these apps. Learn more.
    • 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. Learn how to set the Preferences.

    Also read about other customization options, in Creative Cloud app & services | Customizations.

    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. Learn more.
    • 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. Learn how to set the Preferences.
    • (Not currently available for Windows ARM or macOS (Apple Silicon) devices) Create a folder for extensions and include the UPIA command-line tool: This option is enabled if you have plug-ins in the package. It creates a subfolder in the package folder to include extensions 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. Learn how to set the Preferences.

  9. On the Finalize screen, specify the following:

    Package name: Enter the name of the package.

    Create flat package: If you have chosen a macOS platform, you have the option to create flat packages. This option is selected by default. For more details, see Creating flat packages.

    Review the included applications and configuration for this package before building the package.

    Click Create package.

You are returned to the package list when the package creation process begins.

If the package is built successfully, you are prompted to download the package.

Also, the Download link is available in the Actions column of the corresponding package row. So you can download the package later. 

A package is available in the Admin Console for up to three days. To check the time remaining to download a package, click  to the right of the package name.

Caution

If the package that you've created, contains one or more apps that have been rolled back owing to a bug or issue which needs to be fixed, this package displays as Revoked. You will be unable to download this package.

Also, if you have previously downloaded a package that contains a revoked app, you should not deploy it. You should create and deploy a new package with a non-revoked version of the app. 

Corrupted package

The downloaded package file is a .zip file format.

If you double-click to unzip the package file, you may encounter the following, Unable to expand error on macOS 10.14 and prior versions.

This is because the macOS Archive Utility does not support the unzipping of large files that are zipped using the Zip64 mode.

Error 1 - Operation not permitted

To unzip the file, open the terminal in the folder where you've downloaded the file and run the unzip command:

unzip <file name>.zip

Packageinfo.txt

The package that you download, contains a Packageinfo.txt file. This file has the information such as the following about that package:

  • Package Name
  • Package Type - Self Service or Managed
  • Platform
  • Locale
  • Creative Cloud desktop app version
  • Package Configurations
    • Remote update manager - Enabled or Disabled 
    • App Panel - Enabled or Disabled
    • Beta App Download - Enabled or Disabled
    • Browser Based Auth - Enabled or Disabled
    • Files Panel - Enabled or Disabled
    • Market Panel - Enabled or Disabled
    • Use OS Locale - Enabled or Disabled

The PackageInfo.txt file is for informational purposes only.

Acrobat-only packages

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

  1. Sign 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.

    Choose a Platform:

    Choose the operating system and the processor support.

    Note:
    • It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices.
    • It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.

    A package made for one operating system and architecture type, cannot be deployed on another.

    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 Create 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.

  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.

Note:

If you are creating macOS packages, the Adobe Package Downloader is downloaded to your computer. Open and run to complete download of package. For further details, see here.

After you create Acrobat-only packages or packages that include Acrobat using the procedures described in this document, use the Customization wizard to 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.

Caution:

Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.

We recommend that you use the create package workflows provided in the Adobe Admin Console to create Named User Licensing packages and Shared Device Licensing packages.

Review the system requirements before you download and install Creative Cloud Packager.

  1. Sign in to the Admin Console and navigate to Packages > Tools.

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

    Admin packaging and management tools

For more information on creating and deploying packages using Creative Cloud Packager, see Deploy and deliver apps and updates.

Uninstall products and licenses

While you create and deploy packages to client machines, you must remove previously installed products and licenses. For example, if your organization migrates from Shared Device Licensing to Named User Licensing, uninstall the products and licenses previously installed on the machine. Also, there's often the case when client machines may contain multiple versions of apps. Or, may be using conflicting licenses. Client machines, might be consuming extra licenses. And these licenses are not being returned to the deployment pool.

In all these scenarios, we recommend that you use one of these procedures to uninstall the products and / or licenses on the client machines:

More like this

 Adobe

Get help faster and easier

New user?

Quick links

View all your plans Manage your plans

Legal Notices    |    Online Privacy Policy