Create Shared Device Licensing packages

Last updated on Aug 3, 2026

Learn how to create Shared Device Licensing (SDL) packages for shared computers in educational environments.

Shared Device Licensing assigns Adobe licenses to devices instead of individual users, making it ideal for computer labs and classrooms where multiple users share the same machine. Anyone who logs on to the device has access to Adobe products and services.

Before you begin

Packages cannot be deployed across different operating systems or architecture types. 

Create separate packages for Windows 32-bit, Windows 64-bit, Windows ARM, macOS (Intel), and macOS (Apple Silicon) devices. Alternatively, use a macOS (Universal) package for both Intel and Apple Silicon devices. 

SDL packages require active Shared Device Licensing entitlements and System Admin or Deployment Admin permissions in the Admin Console.

Note

If Adobe XD version 50 or later shows an Unable to verify subscription error, create and install a new SDL package from the Admin Console. This applies to both Windows and macOS.

Build SDL packages

Sign in to the Admin Console and select Packages > Packages.

Select Create a Package, choose Shared Device Licensing, and then select Next.

On the Entitlements screen, select the required entitlement for your deployment, then select Next.

On the Configure screen, choose a platform

  • macOS (Universal) 
  • macOS (Intel)  
  • macOS (Apple Silicon) 
  • Windows (64-bit) 
  • Windows (32-bit) 
  • Windows (ARM)

Select the Language or select Use OS Locale to deploy in each client machine's operating system language, and then select Next. When not available, the OS language is the default fallback language in which the package is deployed.

On the Choose apps screen, select next to each application to include in the package and select Next.

Admin Console showing available applications on the left and selected applications on the right.
Choose applications from the available list to add to the package.

Note

To create a license-only package for devices with existing Adobe applications installed, select Next without adding applications. License-only packages also don't require plugins and management options.

On the Choose plugins screen, search for and select the required plugins, then select Next.

Choose Plugins screen showing available plugins with search and filter options to select plugins for the package.
Select and filter plugins to include in the package.

Select Show compatible plugins only to display plugins compatible with the selected applications.

Note

Plugins don't require the supporting application to be part of the same package. Plugins can be deployed for apps already installed on user devices. If a device does not have the target application, the plugin isn't installed. Not currently available for Windows ARM devices

On the Options screen, choose the required Creative Cloud Desktop options and Management options, then select Next.

Customize using managed packages to decide how users interact with Creative Cloud apps and services.

Caution

Certain Creative Cloud desktop apps require you to keep file syncing enabled. If you deselect it, Creative Cloud files won't sync, though all apps, Adobe Fonts, and Adobe Stock search remain available. Federated IDs can't download Stock previews.

Enter a package name on the Finalize screen. For macOS packages, confirm the Create flat package option, and then select Create package.

After the package build completes, select Download, then save the package to the required location. To check the time remaining to download a package, select preview  to the right of the package name.

Alert

If your package contains revoked apps, the package shows a Revoked status and cannot be downloaded. Create a new package with non-revoked app versions instead. 

If you double-click a downloaded package ZIP file on macOS 10.14 or earlier, you may encounter an Unable to expand error. This is because the macOS Archive Utility does not support unzipping large files zipped using the Zip64 mode. To extract the package, open Terminal in the download folder and run unzip <file_name>.zip.

Note

Starting December 11, 2023, new users and organizations will not be entitled to Creative Cloud Synced files. Starting February 1, 2024, Creative Cloud Synced files will be discontinued for personal accounts that existed before December 11, 2023. Starting October 1, 2024, Creative Cloud Synced files will be discontinued for business accounts associated with organizations that existed before December 11, 2023.

Application filters

Filter menu displaying options such as latest versions, long-term supported versions, beta apps, pre-release apps, and older versions.
Use filters to narrow down available applications on the Choose Apps screen.

Filter

Description

Latest versions

Displays the latest version of all available applications.

Long-term supported versions

Displays Adobe long-term supported versions. To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy. Named User Licensing supports the Acrobat Classic version. Learn about Document Cloud Product Tracks.

Beta apps

Displays available beta apps.

App add-ons

Certain Adobe apps include add-ons. When you add an app that includes one or more add-ons, you can include them in the package. Add-ons are not included by default in the package.

Note

If you add a product with dependent products, those products are added automatically. For example, if you add Photoshop, the dependent products Camera Raw and Adobe Preview are added automatically.

Selected applications panel showing an application with add‑ons options.

Manage add‑ons for selected applications in the package.

Management options

Use the following options on the Options screen to configure management and deployment settings for the package.

Option

Description

Enable Remote Update Manager

Enables the use of Remote Update Manager to remotely run the updater on the client machine with administrator privileges.

Redirect to internal update server

Redirects all package updates to an internal update server. Server details are specified in an override XML in Packages > Preferences in the Admin Console. Set packaging preferences..

Create a folder for extensions

Creates a subfolder in the package folder to include extensions to install with the package. Available only when plugins are included in the package. Not available for Windows ARM or macOS (Apple Silicon) devices. Manage Extensions in packages.

Install package to custom install directory

Installs apps in the package to a custom install directory defined in Packages > Preferences in the Admin Console. Set packaging preferences.

Packageinfo.txt

The downloaded package includes a PackageInfo.txt file with details about the package configuration.

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

If you are creating macOS packages, the Adobe Package Downloader is downloaded to your computer. Open and run it to complete the package download.