Acrobat Classic version can now be included in Named User Licensing packages. This will provide customers with a stable release Acrobat version that provides the ability to limit feature updates while still receiving security and platform enhancements. For more, see Document Cloud Product Tracks.
Last updated on
Oct 3, 2024
|
Also applies to Creative Cloud for enterprise, Creative Cloud for teams, Document Cloud for enterprise
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Deployment home
- K-12 Onboarding Wizard
- Simple setup
- Syncing Users
- Roster Sync K-12 (US)
- Key licensing concepts
- Deployment options
- Quick tips
- Approve Adobe apps in Google Admin Console
- Enable Adobe Express in Google Classroom
- Integration with Canvas LMS
- Integration with Blackboard Learn
- Configuring SSO for District Portals and LMSs
- Add users through Roster Sync
- Kivuto FAQ
- Primary and Secondary institution eligibility guidelines
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage users
- Overview
- Administrative roles
- User management strategies
- Assign licenses to a Teams user
- In-app user management for teams
- Add users with matching email domains
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Overview
- Manage products and entitlements
- Manage products and product profiles
- Manage products
- Buy products and licenses
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Entitle users to train Firefly custom models
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage products and product profiles
- Get started with Global Admin Console
- Adopt global administration
- Select your organization
- Manage organization hierarchy
- Manage product profiles
- Manage administrators
- Manage user groups
- Update organization policies
- Manage policy templates
- Allocate products to child organizations
- Execute pending jobs
- Explore insights
- Export or import organization structure
- Manage storage and assets
- Storage
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Overview
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Manage your Teams account
- Renewals
- Manage contracts
- Reports & logs
- Get help
Introduction
Named user licensing is the default and most popular licensing method to deploy and use Adobe Creative Cloud and Document Cloud products. It is designed for the network-connected scenario where app licenses are managed based on individual user requirements. Using named user licensing, you can provide your end users with the full functionality of the software and services. Users can access all the available apps and services based on your organization's entitlements.
Learn about the various options to deploy and deliver apps and updates to your end users.
|
|
Note:
Availability Of user-generated packages
Starting December 2023, only packages aligned with Adobe's Enterprise & Teams support policy will be available on the Packages tab of the Admin Console.
This will help optimize the performance and load time of the Packages tab.
Self-service packages
Like millions of Adobe users, you can allow your creatives to install applications and updates via the Creative Cloud desktop app. It reduces IT overhead and ensures that your creatives have access to all the tools they need and receive updates when they are released.
If you want to enable self-service even if your end users do not have administrative privileges, you can do one of the following:
- Create a Self-Service package.
- Create a Managed Package with elevated privileges turned on.
- Create a package based on an Adobe Template with elevated privileges turned on.
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.
Note:
Using the Creative Cloud desktop app, your end users can install only the two most recent major versions of Creative Cloud apps. For end users who require older versions, create and deploy Managed packages.
-
Log in to the Admin Console and navigate to Packages > Packages.
-
Click Create a Package.
-
Choose Self-Service Package and click Next.
-
Enter a package name and select the required options:
- Choose a Platform: Choose the operating system and the processor support from the following:
- macOS (Universal)
- macOS (Intel)
- macOS (Apple Silicon)
- Windows (64-bit)
- Windows (32-bit)
- Windows (ARM)
Note:A package made for one operating system and architecture type, cannot be deployed on another.
- It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.
- It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices. Alternatively, you can create a macOS (Universal) package, and use this to install apps on both macOS (Intel) and macOS (Apple Silicon) machines.
Note:If you choose a macOS platform, you can create flat packages. This option is selected by default. For more details, see Creating flat packages.
Language: Select the language in which you want to create the package.
Use OS Locale: Enables you to create a package that deploys in the OS language of client machine. In which case, the OS language is the default fallback language in which the package is deployed.
(Not currently available for Windows ARM devices) Create a folder for extensions & include the Adobe Extension Manager command-line tool: Enables you to create a subfolder in your package folder. In the subfolder, you can include extensions that you want to install with the package. For more, see Manage Extensions in packages.
Redirect to internal update server: Enables you to 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 through the Admin Console.
Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop app. This means that end users can then go to the Creative Cloud desktop app, and install or update these apps. Learn more.
- Choose a Platform: Choose the operating system and the processor support from the following:
-
(Applies to packages for the macOS platform only)
-
Click Create package.
The Packages page is displayed. 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 period for which the package is available for download from the Admin Console.
If you want to check the remaining time for the existing packages in the details pane, click 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 Download for the required package.
|
Caution |
|
If the package that you've created contains one or more revoked apps, the status displays as Revoked. Also, you cannot download this package. 
|
|
The downloaded package file is a .zip file format. If you double-click to unzip the package file, you may encounter the following, Unable to expand error on macOS 10.14 and prior versions. This is because the macOS Archive Utility does not support the unzipping of large files that are zipped using the Zip64 mode. 
To unzip the file, open the terminal in the folder where you've downloaded the file and run the unzip command: unzip <file name>.zip |
Packageinfo.txt
The package that you download, contains a Packageinfo.txt file. This file has the information such as the following about that package:
- Package Name
- Package Type - Self Service or Managed
- Platform
- Locale
- Creative Cloud desktop app version
- Package Configurations
- Remote update manager - Enabled or Disabled
- App Panel - Enabled or Disabled
- Beta App Download - Enabled or Disabled
- Browser Based Auth - Enabled or Disabled
- Files Panel - Enabled or Disabled
- Market Panel - Enabled or Disabled
- Use OS Locale - Enabled or Disabled
The PackageInfo.txt file is for informational purposes only.
With Managed packages, you can decide what gets deployed and when it gets updated. You can create the packages that contain the latest or archived versions of Adobe products. You can then deploy these packages to the user's computers in your organization. You can even perform silent and custom deployment where no inputs are required from your users during installation.
If you plan to use Managed packages, you can:
- Create a Managed Package with elevated privileges turned on.
- Create pre-configured packages using Adobe Templates.
- Create customized packages that contain any one or more of the following:
- Adobe apps and services
- Configuration options
- Marketplace plugins
Use this package to maintain greater control of the Adobe applications and updates that your users can install.
Note:
To create packages that include products such as Adobe Captivate and Adobe Presenter that are not part of Creative Cloud or Document Cloud, customize the available Adobe Templates. You cannot use the following procedure.
-
Sign in to the Admin Console and navigate to the Packages > Packages.
-
Click Create a Package.
-
Choose Managed Package and click Next.
-
On the Configure screen, select the required options:
- Choose a Platform: Choose the operating system and the processor support from the following:
- macOS (Universal)
- macOS (Intel)
- macOS (Apple Silicon)
- Windows (64-bit)
- Windows (32-bit)
- Windows (ARM)
Note:A package made for one operating system and architecture type, cannot be deployed on another.
- It's necessary to create separate packages for Windows 64-bit, Windows 32-bit, and Windows ARM devices.
- It's necessary to create separate packages for macOS (Intel) and macOS (Apple Silicon) devices. Alternatively, you can create a macOS (Universal) package, and use this to install apps on both macOS (Intel) and macOS (Apple Silicon) machines.
- Language: Select the language in which to create the package.
- Use OS Locales: Enable this option to create a package that deploys in the OS language of client machine. The OS language is the default fallback language in which the package is deployed.
- Choose a Platform: Choose the operating system and the processor support from the following:
-
Click Next.
-
On the Choose Apps screen, click
next to the corresponding applications to include them in the package, and then click Next.Click Next on this step if you need to create a lightweight package (without Adobe apps) that includes either or both of the following:
- Configuration options
- Marketplace plugins
Note:If you deploy an application which has special system requirements on an unsupported machine the installer will fail. If required, see the system requirements for the application you are installing.
Optionally, you can filter down the list of Available Applications to choose from.
Latest versions: Display the latest version of all available applications.
Long-term supported versions: Display Adobe's long-term supported versions.
- Creative Cloud: To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy.
- Document Cloud: Named User Licensing now supports Acrobat Classic version. Learn about the Document Cloud Product Tracks.
Beta apps: Display available beta apps. Learn more.
Older versions: Display a list of previous versions of the apps. View versions that don't receive security or feature updates.
Optionally, you can filter down the list of Available Applications to choose from.
Latest versions: Display the latest version of all available applications.
Long-term supported versions: Display Adobe's long-term supported versions. To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy.
Beta apps: Display available beta apps. Learn more.
Older versions: Display a list of previous versions of the apps. View versions that don't receive security or feature updates.
App Add-ons: Certain Adobe apps come with Add-ons. So, when you add an app that includes one or more Add-ons, you have the option to include the add-ons in the package you're creating. By default, Add-ons are not included in the package.
- Configuration options
-
(Not currently available for Windows ARM devices) On the Choose Plugins screen, search and select plug-ins to include in the package, and click Next.
You can select the Show Compatible Plugins Only check box to display the plug-ins that are compatible with the apps in the package. This filter doesn't appear if you only have the Creative Cloud desktop app in your package.
To view the list of selected plug-ins, click Selected Plugins.
Note:The plug-ins that you include in the package do not necessarily need the supporting application to be part of the same package. You can include plug-ins and extensions for apps that are previously installed on your users' computers. Also, if a computer does not have the targeted application for a plug-in, the plug-in is not installed on the computer.
-
If you've not selected any apps and have selected one or more plugins, then you have the following options:
- Create a plugin-only package by keeping the Configuration Options turned off.
- Create a plugin and configuration package by turning the Configuration Options on.
To create a configuration-only package, no apps or plugins should be selected. In this case, the Configuration Options switch will not be available, and the Configuration Options screen will be visible.
Creative Cloud Desktop Options:
- Enable self-service install: Allow users to install and update applications from Apps panel in the Creative Cloud desktop app. Learn more.
- Allow non-admin to update and install apps: Enable self-service for end users who do not have administrative privileges, to install, and manage their applications and updates. Learn more.
- Disable auto-update for end users: Ensure that end users will not be able to automatically update their applications via the Creative Cloud desktop app. Learn more.
- Enable self-service plugin install: Allow end users to install and update plug-ins from the Marketplace tab in Creative Cloud desktop app. If deselected, the users can't browse or install any plug-ins using the Creative Cloud desktop app. Whenever you toggle this option, users must quit and relaunch. Alternatively, they must sign out and sign back into the Creative Cloud desktop app for the changes to reflect. Learn more.
- 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. Read more on disabling file syncing. This option is available for Creative Cloud subscribers in commercial and educational organizations only. It is not available for subscribers in government organizations.
- Enable browser-based login: By default, users must sign in using the Creative Cloud desktop app. Choose this option to redirect users to sign in via the browser. Learn more.
- Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop app. This means that end users can then go to the Creative Cloud desktop app and install or update these apps. Learn more.
- Install package to custom install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. Learn how to set the Preferences.
Also read about other customization options, in Creative Cloud app & services | Customizations.
Management Options:
- Enable Remote Update Manager: Enables the use of Remote Update Manager. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. Learn more.
- Redirect to internal update server: Enables you to 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. Learn how to set the Preferences.
- (Not currently available for Windows ARM or macOS (Apple Silicon) devices) Create a folder for extensions and include the UPIA command-line tool: This option is enabled if you have plug-ins in the package. It creates a subfolder in the package folder to include extensions to install with the package. For more, see Manage Extensions in packages.
- Install package to custom install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. Learn how to set the Preferences.
-
On the Finalize screen, specify the following:
Package name: Enter the name of the package.
Create flat package: If you have chosen a macOS platform, you have the option to create flat packages. This option is selected by default. For more details, see Creating flat packages.
Review the included applications and configuration for this package before building the package.
Click Create package.
You are returned to the package list when the package creation process begins.
If the package is built successfully, you are prompted to download the package.
Also, the Download link is available in the Actions column of the corresponding package row. So you can download the package later.
A package is available in the Admin Console for up to three days. To check the time remaining to download a package, click
to the right of the package name.
If the package that you've created, contains one or more apps that have been rolled back owing to a bug or issue which needs to be fixed, this package displays as Revoked. You will be unable to download this package.
Also, if you have previously downloaded a package that contains a revoked app, you should not deploy it. You should create and deploy a new package with a non-revoked version of the app.
|
The downloaded package file is a .zip file format. If you double-click to unzip the package file, you may encounter the following, Unable to expand error on macOS 10.14 and prior versions. This is because the macOS Archive Utility does not support the unzipping of large files that are zipped using the Zip64 mode.
To unzip the file, open the terminal in the folder where you've downloaded the file and run the unzip command: unzip <file name>.zip |
Packageinfo.txt
The package that you download, contains a Packageinfo.txt file. This file has the information such as the following about that package:
- Package Name
- Package Type - Self Service or Managed
- Platform
- Locale
- Creative Cloud desktop app version
- Package Configurations
- Remote update manager - Enabled or Disabled
- App Panel - Enabled or Disabled
- Beta App Download - Enabled or Disabled
- Browser Based Auth - Enabled or Disabled
- Files Panel - Enabled or Disabled
- Market Panel - Enabled or Disabled
- Use OS Locale - Enabled or Disabled
The PackageInfo.txt file is for informational purposes only.
Acrobat-only packages
If your organization has a Document Cloud-only entitlement on the Admin Console, you can create Acrobat-only packages.
-
Sign in to the Admin Console and navigate to the Packages > Packages.
-
Click Create a Package.
-
Enter a package name, and select the required options.
Choose a Platform:
Choose the operating system and the processor support.
Language:
Select the language in which you want to create the package.
Enable Remote Update Manager:
Enables you to run the updater remotely on the client machine with the benefit of executing as an administrator. For more information, see Remote Update Manager.
-
Click Create 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.
Note:
If you are creating macOS packages, the Adobe Package Downloader is downloaded to your computer. Open and run to complete download of package. For further details, see here.
After you create Acrobat-only packages or packages that include Acrobat using the procedures described in this document, use the Customization wizard to customize your package.
The wizard streamlines the task of customizing or configuring Acrobat features and app in the installer earlier to its organization-wide deployment.