Packaging apps via the Admin Console

  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 roles
    2. Deployment Guides
      1. Named User deployment guide
      2. SDL deployment guide
    3. Deploy Creative Cloud for education
      1. Deployment guide
      2. Integration with Canvas LMS
      3. Integration with Blackboard Learn
      4. Configuring SSO for District Portals and LMSs
      5. Kivuto FAQ
      6. Primary and Secondary institution eligibility guidelines
  3. Set up your organization
    1. Set up identity
      1. Identity types | overview
      2. Set up organization with Enterprise ID
      3. Set up organization with Federated ID
        1. SSO overview
        2. Setup Azure Connector and sync
          1. Set up SSO with Microsoft via Azure OIDC
          2. Add Azure Sync to your directory
          3. Azure Connector FAQ
        3. Set up Google Federation and sync
          1. Set up SSO with Google Federation
          2. Add Google Sync to your directory
          3. Google federation FAQ
        4. Generic SAML
          1. Set up SSO with other SAML providers
          2. Set up SSO with Microsoft Azure ADFS
          3. SSO Common questions
          4. SSO Troubleshooting
        5. Education SSO
          1. Configure SSO for District Portals and LMS
          2. Common questions
          3. Dovetail
      4. Verify ownership of a domain
      5. Add and manage domains
      6. Link domains to directories
      7. Use directory trust to add pre-claimed domains
      8. Migrate to new authentication provider
    2. Asset settings
    3. Authentication settings
    4. Privacy and security contacts
    5. Console settings
    6. Manage encryption
  4. 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. User management API (UMAPI)
        5. Microsoft Azure Sync
        6. 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 self-service policies
      4. Manage app integrations
      5. Manage product permissions in the Admin Console  
      6. Enable/disable services for a product profile
      7. Single App | Creative Cloud for enterprise
      8. Optional services
    3. Manage Shared Device licenses
      1. What's new
      2. Deployment guide
      3. Create packages
      4. Recover licenses
      5. Migrate from Device Licensing
      6. Manage profiles
      7. Licensing toolkit
      8. Shared Device Licensing FAQ
  5. 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
  6. 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 6.x Assets
      4. Configure and install Adobe Asset Link
      5. Manage assets
      6. Adobe Asset Link for XD
    4. Adobe Sign
      1. Set up Adobe Sign for enterprise or Teams
      2. Adobe Sign - Team feature Administrator
      3. Manage Adobe Sign on the Admin Console
    5. Creative Cloud for enterprise - free membership
      1. Overview
      2. Getting started
  7. 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 with SCCM
      3. Deploy Adobe packages with ARD
      4. Install products in the Exceptions folder
      5. Uninstall Creative Cloud products
      6. Use Adobe provisioning toolkit enterprise edition
      7. 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
  8. Manage your account
    1. Manage your Teams account
      1. Overview
      2. Update payment details
      3. Manage invoices
      4. Change contract owner
    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. Purchase Request compliance
    6. Value Incentive Plan (VIP) in China
    7. VIP Select help
  9. Reports & logs
    1. Audit Log
    2. Assignment reports
    3. Content Logs
  10. 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

Introduction

The Packages page in the Admin Console provides the following functionality. Use them when you plan to deploy Creative Cloud and Document Cloud applications to end users in your Enterprise.

  • Download pre-configured packages by using Adobe Templates.
  • Create customized Named User Licensing or Shared Device Licensing (for educational institutions) packagers with the configuration and applications you want your end users to have.
  • Enable email notifications, so you get notified when new product versions become available.
  • View previous packages you or other administrators in your organization have created. Also, view details of a specific package and track available updates for the apps in the package.
  • Download the IT tools like Remote Update Manager and Adobe Update Server Setup Tool.
  • Download the Adobe Extension Manager command-line tool to install extensions and plug-ins from the ZXP file container format.
Hoiatus.

To create device license (legacy) or serial number license (legacy) packages, use Creative Cloud Packager.

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.

Using packages in the Admin Console

Tools

Download the Creative Cloud Packager, Adobe Extension Manager command-line tool, Adobe Update Server Setup Tool, or Remote Update Manager.

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

Creative Cloud Packager

Adobe Creative Cloud Packager makes it easy for you to create packages that contain Adobe Creative Cloud products and updates. These packages can then be deployed to the client machines in your organization.

For more information, see Packager.

Märkus.

Creative Cloud apps released on October 15, 2018 (Creative Cloud 2019) or later are not available in Creative Cloud Packager. For more information, see this document.

Adobe Update Server Setup Tool

Adobe Update Server Setup Tool allows you to set up an on-premise server that hosts Creative Cloud updates. It allows IT to save bandwidth and control when Updates become available for end users.

For more information, see Using Adobe Update Server Setup Tool.

Remote Update Manager

Remote Update Manager allows you to remotely call the updater on a client machine. It allows you to seamlessly manage when your client systems install updates. You can specify a particular product or update all products at the same time. When used with the Adobe Update Server Setup tool, the updates are pulled from your own premise server.

For more information, see Use Adobe Remote Update Manager.

Adobe Extension Manager command-line tool

The ExMan command-line tool allows the admin to install extensions and plug-ins from the ZXP file container format. When you create a package, you can select to include extensions or you can download the stand-alone tool for Mac or Windows.

Preferences

Set preferences for notifications, AUSST, and custom package directories.

Märkus.

Package preferences are local to the logged in Admin. That means, any preferences that you set, apply to you and the packages that you create.

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

Package preferences

Notifications

You can choose to receive email notifications for updates available to any Creative Cloud products.

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

  2. To enable or disable notifications, check or not highlight the box in the Notifications section.

Select Available application versions to display app versions that do not receive security or feature updates.

While creating packages, select Show older versions in the Choose Apps screen.

Hoiatus.

While Adobe fully supports the latest version of apps, support for older versions is limited. Creative Cloud for enterprise plans also include a designated LTS version that receives security updates. Adobe recommends that you create packages with the latest or LTS versions of the apps. However, if you choose an older app version, see the Creative Cloud Support policy to know the extent to which Adobe provides support for it.

Internal Update Server

To configure an internal update server, download Adobe Update Server Setup Tool from the Tools section. Next, generate the override file, and paste its contents in the Internal Update Server box.

Also, in the create package workflow, choose this option to redirect updates to the internal update server.

Bypass internal update server

Use this preference to ensure that, if your internal udpate servers is unavailable, your end-user compuers will get Adobe updates from the Adobe servers. Learn more.

Custom Install Directory

If the apps in your packages support custom install directories, specify the directory to which you want the packages to install these apps. For details, see Create packages.

Märkus.

The directory path that you specify must be an absolute path. If you are creating a package to be deployed on Windows computers, specify the path that includes the drive letter. For example: C:\<folder path>.

Also, when creating a folder, you cannot use any of the characters that Windows does not support: \/:*?<>|.

Adobe logo

Logige oma kontole sisse