Log in to the Admin Console and navigate to the Packages > Packages.
The list of available packages is displayed.
The Packages tab in the Admin console allows you to create custom packages. The create workflow provides you with granular control of what applications are included in a package. You can also specify settings such as the targeted platform and language.
In the Packages tab, you can create the following types of packages:
Self-Service Package:
Installs the Adobe Creative Cloud Desktop app on your users' computers with admin privileges. See Create a Self-Service Package.
Managed Package:
Allows you to control application installs and updates that are installed on your users' computer. See Create a Managed Package.
Acrobat-only Package:
If your organization only has a Document Cloud entitlement on the Admin Console, you can create Acrobat-only packages.
If you want to create packages that include products such as Adobe Captivate and Presenter that are not part of either the Creative or Document Clouds, you can customize the available Adobe Templates. You cannot use the procedures described in this document.
Use this package to give your users complete control of the Adobe applications and updates that they can download and install. If your users do not have Administrator credentials to manage applications and updates, then you can create a Self-Service package for them.
Log in to the Admin Console and navigate to the Packages > Packages.
The list of available packages is displayed.
Click Create a Package.
It displays a dialog box to choose your deployment method.
Choose Self-Service Package and click Select.
Enter a package name and select the required options:
Platform: Choose the operating system and the processor support (32 bit or 64 bit). It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't run on a 64-bit machine.
Language: Select the language in which you want to create the package.
Use OS Locale: Select to create a package that deploys in the client machine's OS language. In which case, the OS language is the default fallback language in which the package is deployed.
Create a folder for extensions & include the Extension Manager command line tool: Create a sub-folder in your package folder that you can use to include extensions that need to be installed with the package. For more, see Manage Extensions in packages.
Redirect to internal update server: Redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console.
Click Build package.
It displays the Packages page. You can check the progress of the build in the list of packages.
A message is shown after the build process is over. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.
You can also check the time left for which a package is available in the Admin Console for existing packages in the details pane by clicking the row item for the package.
In the Save As dialog box, choose a location on your computer to save the package.
To download and distribute the package later, click the package name in the list of packages and then click Download in the right pane.
Use this package to maintain greater control of the Adobe applications and updates that your users can install.
To create packages that include products such as Adobe Captivate and Presenter that are not part of either Creative Cloud or Document Cloud, you can customize the available Adobe Templates. You cannot use the following procedure.
Log in to the Admin Console and navigate to the Packages > Packages.
Click Create a Package.
It displays a dialog box to choose your deployment method.
Choose Managed Package and click Select.
Select the required options:
Platform: Choose the operating system and the processor support (32 bit or 64 bit). It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't run on a 64-bit machine.
Language: Select the language in which you want to create the package.
Use OS Locale: Select to create a package that deploys in the client machine's OS language. In which case, the OS language is the default fallback language in which the package is deployed.
Show apps panel: Show/hide the Apps panel in Creative Cloud desktop application for end users. Enabling /disabling the Apps Panel automatically enables/ disables the updates on the client machines.
Allow non-admin to update and install apps: Allows self-service end users, who do not have Administrative privileges, to install and manage their applications and updates.
Enable Remote Update Manager: Enable the use of Remote Update Manager, select this option. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. For more information, see Remote Update Manager.
Create a folder for extensions & include the Extension Manager command line tool: Create a sub-folder in your package folder that you can use to include extensions that need to be installed with the package. For more, see Manage Extensions in packages.
Redirect to internal update server: Redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console article.
Install to custom directory: Install the apps in this package to a custom directory. The directory is defined in the Packages > Preferences tab in the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console article.
Disable file syncing: Suppress the automatic syncing of files to client systems. Useful when you are installing packages in a test environment where you want to suppress file syncing. Available only to educational institutions.
Click Next.
It displays a screen that allows you to choose the applications that you need to add to the package.
If you add a product that has dependent products, the dependent product is added automatically. For example, if you add Photoshop CC, Camera Raw CC and Adobe Preview CC are added automatically. You can, however, choose to remove the dependent products.
Click the Plus icons next to the corresponding applications to include them in the package, and then click Next.
In the Finalize screen, enter the name of the package you are creating.
You can also review the included applications and configuration for this package before building the package.
Click Build Package.
It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.
You can also check the time left for which a package is available on the Admin Console for existing packages in the details pane by clicking the row item for the package.
In the Save As dialog, choose a location on your computer to save the package.
To download and distribute the package later, click anywhere on the row for the required package and then click Download in the package details drawer.
If your organization only has a Document Cloud entitlement on the Admin Console, you can create Acrobat-only packages.
Log in to the Admin Console and navigate to the Packages > Packages.
Click Create a Package.
Enter a package name and select the required options.
Platform:
Choose the operating system and the processor support (32 bit or 64 bit). It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't run on a 64-bit machine.
Language:
Select the language in which you want to create the package.
Enable Remote Update Manager:
Enable the use of Remote Update Manager, select this option. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. For more information, see Remote Update Manager.
Click Build Package.
It displays the Packages page. You can check the progress of the build in the list of packages.
It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.
In the Save As dialog, choose a location on your computer to save the package.
To download and distribute the package later, click the package name in the list of packages and then click Download in the right pane.
You can use Creative Cloud Packager to create custom packages when you require licensing other than named, for example serial number-based licensing.
To download the Creative Cloud Packager, log in to the Admin Console and navigate to Packages > Tools & notifications.
Click the download option in the Creative Cloud Packager tile based on your operating system.
The packages created through Creative Cloud Packager are not listed in Packages tab of the Admin console.
Also, review the system requirements before you download and install Creative Cloud Packager.
For more information on creating and deploying packages, see the Packaging User Guide.
After you have created your Acrobat-only packages or packages that include Acrobat as one of the products using the procedures described in this document, you can use the Adobe Customization Wizard to further customize your package.
The wizard streamlines the task of customizing or configuring Acrobat features and app in the installer prior to its organization-wide deployment.