Packager automation

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

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.

You can automate the creation of the packages. Using an input XML file that specifies the various settings and options in the package, you can automate the package creation with Creative Cloud Packager.

  1. Sign into Packager and accept the EULA. Do not sign out while using the automation process. 

  2. Create an XML file with the following options specified in it.

    Your XML file should conform to the attached XSD (schema): pkgConfigFile.zip. 

    Laadi alla

    Märkus.

    In the input XML file, if you set the appsPanelEnabled flag for false, then you must also set the adminPrivilegesEnabled flag to false.

    Example 1: The following XML file automates creation of a serialized package that includes all entitled latest updates:

    <CCPPackage>
      <CreatePackage>
     <packageName>AllLatestUpdates Package</packageName>
     <outputLocation>C:\Temp\CCPPkg.9a137bb2-d7b4-4302-bf90-e9f89c502afa\WIN32\mul</outputLocation>
     <is64Bit>true</is64Bit>
     <customerType>enterprise</customerType>
     <organizationName>Adobe Production Validation: GAR</organizationName>
     <matchOSLanguage>true</matchOSLanguage>
     <rumEnabled>true</rumEnabled>
     <updatesEnabled>false</updatesEnabled>
     <appsPanelEnabled>true</appsPanelEnabled>
     <adminPrivilegesEnabled>false</adminPrivilegesEnabled>
     <serialNumber>11111111111111111111111</serialNumber>
     <ProductCategory>AllLatestUpdates</ProductCategory>
     <IncludeUpdates>true</IncludeUpdates>
        <Language>
          <id>en_US</id>
        </Language>
      </CreatePackage>
    </CCPPackage>

    Example 2: The following XML file creates a team device pool package with all latest updates:

    <CCPPackage>
      <CreatePackage>
     <packageName>All Product Package</packageName>
     <outputLocation>C:\Temp\CCPPkg.9a137bb2-d7b4-4302-bf90-e9f89c502afa\WIN32\mul</outputLocation>
     <is64Bit>true</is64Bit>
     <customerType>team</customerType>
     <organizationName>Adobe Production Validation: GAR</organizationName>
     <matchOSLanguage>true</matchOSLanguage>
     <rumEnabled>true</rumEnabled>
     <updatesEnabled>false</updatesEnabled>
     <appsPanelEnabled>true</appsPanelEnabled>
     <adminPrivilegesEnabled>false</adminPrivilegesEnabled>
     <devicePoolName>Complete</devicePoolName>
     <ProductCategory>AllLatestProducts</ProductCategory>
     <IncludeUpdates>true</IncludeUpdates>
        <Language>
          <id>en_US</id>
        </Language>
      </CreatePackage>
    </CCPPackage>

    Example 3: The following XML file creates an enterprise named package with a custom list of products and updates: 

    <CCPPackage>
      <CreatePackage>
     <packageName>Custom Package</packageName>
     <outputLocation>C:\Temp\CCPPkg.9a137bb2-d7b4-4302-bf90-e9f89c502afa\WIN32\mul</outputLocation>
     <is64Bit>true</is64Bit>
     <customerType>enterprise</customerType>
     <organizationName>Adobe Production Validation: GAR</organizationName>
     <matchOSLanguage>true</matchOSLanguage>
     <rumEnabled>true</rumEnabled>
     <updatesEnabled>false</updatesEnabled>
     <appsPanelEnabled>true</appsPanelEnabled>
     <adminPrivilegesEnabled>false</adminPrivilegesEnabled>
     <ProductCategory>Custom</ProductCategory>
     <IncludeUpdates>true</IncludeUpdates>
        <Language>
          <id>en_US</id>
        </Language>
    //Add the products tag for a custom list of products to be deployed. Inside the Products tag add a Product tag for each of the products to be deployed and specify its sap code and version in it
        <Products>
            <Product>
                <sapCode>AEFT</sapCode>
                <version>12.0</version>
            </Product>
        </Products>
    //Add the HDUpdates tag for a list of updates to be deployed for products that can be installed without their base versions. Inside the HDUpdates tag add an HDUpdate tag for each of the updates to be deployed and specify its sap code and version in it
        <HDUpdates>
            <HDUpdate>
                <sapCode>AEFT</sapCode>
                <version>13.8.1</version>
            </HDUpdate>
        </HDUpdates>
    //Add the Updates tag for a list of updates to be deployed for products other than the products that can be installed without their base versions. Inside the Updates tag add an Update tag for each of the updates to be deployed and specify the update's refId in it
        <Updates>
            <Update>
                <refId>AdobePhotoshopCC2015-16.0/16.1.2</refId>
            </Update>
        </Updates>
      </CreatePackage>
    </CCPPackage>

    To specify a custom list of products to be deployed in the XML file, add the Products tag. For each of the products to be deployed, add a Product tag and inside it specify the Sap Code (<sapCode>) and Version (<version>) for each of the products to be deployed. The sap code and versions for the applications that can be deployed without their base versions are listed on this page. For other applications, you can view the Sap Codes and Versions on the CCP Application screen.

    To specify a custom list of updates in the XML file, you need to enter one of the following:

    • For updates of applications that can be deployed without their base versions, you need to add the HDUpdates tag to the XML config file. Inside the HDUpdates tag, you need to enter an HDUpdate tag for each of such updates and specify the Sap Code (<sapCode>) and Version (<version>) of the update in it. The sap code of updates are the same as mentioned for the relevant products in this page. You can find the version for such updates from the Creative Cloud Packager screen for the relevant product. 

     

    • For updates of other applications, you need to enter the Updates tag. For each of the updates, specify an Update tag and enter only the refID for the update. You can create the refID of the update by adding the Channel ID of the product with the version of the product in the following format: ChannelID/Version. For example, AdobePhotoshopCC2015-16.0/16.1.2. You can find the Channel IDs of the various products on this page. You can find the versions of the product update in Creative Cloud Packager. 

  3. Optionally, you can use the following customizations in the XML:

    • If you have specified ProductCategory as Custom, you also need to specify the exact product and update sap code versions for products and ref IDs for updates in the XML file.
    • serialNumber is an optional tag and is relevant only when the customerType is specified as Enterprise. If Serialnumber tag is present and specified in the XML file, the automation process creates a Serial Number license package. Otherwise, the automation process creates a Named license package.
    • devicePoolName is optional and is only relevant when customerType is specified as Team. If devicePoolName tag is present and specified in the XML file, the automation process creates a Device license package. Otherwise, the automation process creates a Named license package.
  4. Run the PDApp with the following parameters specified:

    Parameter

    Value

    Path of the PDApp executable

    Specify the path of PDApp executable on your machine in double quotes

    Mac: Applications/Utilities/Adobe Application Manager/core/Adobe Application Manager.app/Contents/MacOS/PDApp

    Win: C:/Program Files/Common Files/Adobe/OOBE/PDApp/Core/PDApp.exe

    --appletID

    CCP_UI

    --appletVersion

    1.0

    --workflow

    ccp

    --automationMode

    ccp_automation

    --pkgConfigFile

    Name and path of the XML package configuration file as created in step 1.

    Following is an example of command for Windows. 

    "C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\PDapp.exe" --appletID=CCP_UI --appletVersion=1.0 --workflow=ccp --automationMode=ccp_automation --pkgConfigFile="<path of input XSD>"

    The package gets created. In the same path as your input XML file, another XML file gets created with the name [pkgConfigFileName]_result.xml.

    In case of any errors, you can use the [pkgConfigFileName]_result.xml file for more information on the errors and debugging the errors. PDApp and other logs are created as usual.

Adobe logo

Logige oma kontole sisse