User Guide Cancel

Packager automation

Last updated on | Also Applies to Packager

Adobe Enterprise & Teams: Administration guide
Plan your deployment
1. Basic concepts
2. Deployment Guides
3. Deploy Creative Cloud for education
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
5. Set up Google Federation and sync
6. Set up organization with Microsoft ADFS
7. Set up organization for District Portals and LMS
8. Set up organization with other Identity providers
9. SSO common questions and troubleshooting
Manage your organization setup
Manage products and entitlements
1. Manage users
2. Manage products and product profiles
3. Manage Shared Device licenses
Manage storage and assets
1. Storage
2. Asset migration
3. Reclaim assets from a user
4. Student asset migration | EDU only
  1. Automatic student asset migration
  2. Migrate your assets
Manage services
1. Adobe Stock
2. Custom fonts
3. Adobe Asset Link
4. Adobe Acrobat Sign
5. Creative Cloud for enterprise - free membership
  1. Overview
Deploy apps and updates
1. Overview
2. Create packages
3. Customize packages
  1. Customize the Creative Cloud desktop app
  2. Include extensions in your package
4. Deploy Packages
5. Manage updates
  1. Change management for Adobe enterprise and teams customers
  2. Deploy updates
6. Adobe Update Server Setup Tool (AUSST)
7. Adobe Remote Update Manager (RUM)
8. Troubleshoot
9. Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
Manage your account
Reports & logs
Get help

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.

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.

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

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

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

Download

Get file

Use the attached XSD file to edit and build your package configuration file.

Get file

pkgConfigFile.zip

Note:

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.

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.

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.

Packager automation

Ask the Community

Contact Us