User Guide Cancel

Create packages with serial number licenses

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. Enable Adobe Express in Google Classroom
      3. Integration with Canvas LMS
      4. Integration with Blackboard Learn
      5. Configuring SSO for District Portals and LMSs
      6. Deploy Adobe Express through Google App Licensing
      7. Add users through Roster Sync
      8. Kivuto FAQ
      9. 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. 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 products and entitlements
    1. 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
    2. 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
    3. 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
  6. 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
  7. 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
  8. 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. Channel IDs for use with Adobe Remote Update Manager
      3. 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
  9. 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
  10. Reports & logs
    1. Audit Log
    2. Assignment reports
    3. Content Logs
  11. 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
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.

See how to create Named User Licensing packages and Shared Device Licensing packages.

Creative Cloud for enterprise: Serial number licensing

Serial Number Licensing is anonymous licensing, and is not tied to an individual user, but to a particular computer. Serial number licensing can be used to create pre-licensed packages that are deployed remotely. End users do not need to sign in to begin using the desktop apps. Serial number licensing is also suitable for environments where Internet access is prohibited or infrequent.

  • Flexible licensing options
  • Includes complete set of Creative Cloud applications
  • Available through a customizable Enterprise Term License Agreement (ETLA)
  • Creates a package that is already licensed. No further validation is required on the client machine.

Create Serial number-based packages

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

  1. 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.
    Note: You must run Creative Cloud Packager as an Administrator on the machine where you are building packages.

  2. Choose Creative Cloud for enterprise as your account type.

  3. Sign in with your ID and password.

    Note:

    Your ID should be listed as an admin ID for one of the account types.

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

    Creative Cloud Packager

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

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

    • Click Create Package to start the package creation process.

  6. In the Package Details screen that appears, enter the 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.

    Select Organization

    Select the name of your organization.

    32-bit/64-bit

    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 will not run on a
    64-bit machine. 

    License type

    Select Serial Number License. This option creates a package with a valid license. Use this workflow to deploy a product or group of products containing updates to client machines in a licensed state. No further validation is required on the client machine.

    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, see Modify package configuration.

    Creative Cloud Desktop Application

    Adobe Creative Cloud for desktop is the central hub for Creative Cloud activity and allows the users to view applications and updates.

    Caution:

    Deselect this option and do not install the Creative Cloud desktop application. Adobe recommends that you keep this option disabled for serial number license packages. 

    There is a known issue with specific types of account which can cause the license to get removed from the system when the user logs out of Creative Cloud Desktop. It is not a requirement, but there may be unexpected results if users log in and log out again.

    Show Applications and Updates via the Apps panel

    This option is applicable only when Creative Cloud Desktop Application is enabled. When disabled, this option hides the apps panel in Creative Cloud desktop application 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:

    User selection

    Admin users update via Adobe Update Manager

    Adobe Update Manager is disabled (IT manages update distribution)

    Enable Adobe Update Manager

    Disable Adobe Update Manager

    Select Show Applications and Updates via the Apps panel

    Enabled

     

     

     

    Deselect Show Applications and Updates via the Apps panel

     

    Enabled

     

     

    Select Show Applications and Updates via the Apps panel and Use internal update server

     

     

    Enabled

     

    Deselect Show Applications and Updates via the Apps panel and Use internal update server

     

     

     

    Enabled
    Note:
    • Selecting or deselecting this option overrides the updater behavior that you may have changed in the package configurations.. It is recommended that you verify the package configuration updates before proceeding.
    • To install applications or updates from the Apps panel, users must have administrative privileges.

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

    Elevated Privileges

    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.

    Note:
    • You need to relaunch the Creative Cloud desktop Application for this change to take effect.
    • If an end user has entitlements assigned and signs into the desktop app, the existing serial license on the machine is replaced with that user's entitlements.

  7. In the Package Details screen, click Next. You are prompted to enter the enterprise license key. If you do not have your enterprise license key, you can find it at licensing.adobe.com. Enter the key and then click Next.

  8. The Applications and Updates screen appears. Using the drop-down list on the upper-right side, select a language. 

    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.

    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.

  9. The apps and updates list 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.

    Core Components is always selected, and you cannot deselect it. This option deploys the common licensing infrastructure to client machines. 

    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.

    Note:

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

    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 or not 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 affect the language in which the package is installed.

    Match OS language

    Language explicitly specified while deploying a package using command line or Info.plist file

    The package is  installed in...

    Selected

    No

    OS Language

    Selected

    Yes

    Language explicitly specified in command line while deploying a package

    Not Selected

    Not Selected

    No

    Language in which the package is created

    Selected

    Yes, but the specified language is unavailable

    Language in which the package is created

    Not Selected
    Note:
    • When the installer is run, it checks for the locale that is set at the system level and not at the user level. For more details on this setting, see Install Creative Cloud package with Match OS Language option.
    • Adobe Fireworks does not support multi-lingual packages and installs in the language you have created the package in.
    • The Match OS option is not supported for CS6 applications.

  10. To add applications and updates from a local source, such as a DVD or ESD, instead of downloading from the Creative Cloud, see Add Offline Media.

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

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

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

    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.

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

Create Serial number-based packages for Acrobat

If you're creating a package that includes Acrobat, follow these steps after you have created the package and before you deploy the package to client machines.

  1. Open the following file in a text editor:

    <Package name>\Build\Setup\APRO20.0\proxy.xml

  2. Remove the <Argument name="ENFORCE_NGL=">1</Argument> line from prox.xml.

Note:

If you do not follow these steps, the installed Acrobat app will require your users to sign in at startup.

Deploying packages

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

  1. The Build folder contains the MSI (Windows) or the PKG (Mac OS) files.
  2. The Exceptions folder contains the payloads that must be installed separately.
For information on how to deploy the packages, see Deploy packages.  
Note:

For exception media (such as msi or exe) of latest version of Muse, the exception installer is copied in the following location and the user needs to install this exception separately:

Program Files (x86)\Common Files\Adobe\Installers\Third Party\<Sapcode_Of_App>\<package_name>\

Adobe logo

Sign in to your account

Quick links

View all your plans Manage your plans

Legal Notices    |    Online Privacy Policy