Deploy packages

  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

As an Admin, you create packages on the Adobe Admin Console for the Adobe apps and services that you want to distribute to your end users.

Once the package is created and downloaded to your computer, you can distribute the package and install the packaged apps by one of the following methods:

Double-click the package file

Windows

Double-click the setup.exe file present inside the Build folder of the package.

Note:

If you are using MSI, instead of setup.exe, to deploy a package that has Acrobat DC in it, Acrobat DC is not installed.

macOS

Double click the .pkg file present inside the Build folder of the package.

To customize the install options, update the Info.plist file:

  1. Open the Info.plist file at the following location:

    [package]/Build/xyz_install.pkg/Contents/Info.plist

  2. Add the following entry with the appropriate path in the string tag to configure a custom installation directory where apps will install on the client machine.

    <key>IFPkgFlagDefaultLocation</key>

    <string>[Path of install directory]</string>

  3. Add the following entry to the file with the appropriate language mentioned in the string tag:

    <key> InstallLanguage </key>

    <string>en_GB</string>

  4. Double-click the .pkg file.

The package starts installing.

Use third-party tools

The following is the sequence of events for deploying packages.

  1. After you create a package on the Adobe Admin Console, the package is downloaded to your computer.

  2. Use the following third-party tools to deploy the packaged Adobe apps and services:

Use the command line

Windows

Command line has more required parameters, for which default values are taken if you run Setup.exe by double-clicking.

In the command:

[ADOBEINSTALLDIR] is the installation directory where apps are to be installed on the client machine.

[INSTALLLANGUAGE] is the locale in which the apps are to be installed.

Syntax

setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=]

Syntax example:

setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA

Location of setup.exe:

[Package]\Build

Deploy updates

The initial package will contain applications and the most recent updates. When updates are available, you can provide the updates to your users in the following ways:

  • If Remote Update Manager was included in your deployment package (default behavior), use your deployment tool to remotely run the Remote Update Manager on client machine. Updates will run with administrator privileges and come from Adobe Update Server.

    If you have an internal Adobe Update Server, choose it during package creation. Remote Update Manager pulls updates from your internal server rather than the Adobe server, which saves network bandwidth.

  • To save network bandwidth, it is also possible to set up your own internal Adobe Update Server. You can use AUSST to set up a server which will host both Windows and macOS Updates.

  • You can create an update-only package in the Admin Console. You can then deploy this package using your chosen deployment tool.

 
Note:

The deployment of Creative Cloud 2109 and later apps is not supported in a serial or legacy device license deployment environment. For Creative Cloud 2109 and later, you must choose Named User Licensing or Shared Device Licensing. See the overview of Adobe licensing methods.

Deploy UWP Apps

If you create a package that contains Universal Windows Platform based apps, you will experience unexpected behavior when you deploy the package on an end-user computer. For details, see this document.

Log file locations

Following are the locations of log files for the corresponding Adobe deployment tools:

Component

Log filename

Adobe Update Server Setup Tool (AUSST)

AdobeUpdateServerSetupTool.log

Exception Deployer

ExceptionDeployer.log

Remote Update Manager (RUM)

RemoteUpdateManager.log

Creative Cloud Packager (CCP)

PDApp log is named PDApp.log

Package Builder log is named as follows:
AdobePBhhmmss_ddmmyy.log
Where hhmmss_ddmmyy = hour|minute|second_date|month|year

Licensing logs:

  • Windows: %temp%\oobelib.log
  • macOS: /tmp/oobelib.log

Creative Cloud download/installation logs

Creative Cloud Packager creates a log file to troubleshoot download issues if a file called "asu.trace" is placed at:

  • Windows: %temp%
  • macOS: ~/Library/Logs

The resulting file, DLM.log is created at:

  • Windows: %temp%\AdobeDownload
  • macOS: ~/Library/Logs/AdobeDownload

For Windows errors (for example, 12150) in the DLM.log, see Windows Dev Error Messages.

Adobe logo

Sign in to your account