The procedures described in this document are applicable for apps version CC 2019 and later.

Shared Device License is a licensing method targeted at educational institutions where software is assigned to a device instead of an individual. Anyone who logs onto the device will have access to Adobe's products and services. This method of licensing is ideal for desktop computer labs and classrooms.

For more details, see Licensing overview.

Note: The content and voice-over for this video is currently available in English only.

How to create Shared Device Licensing packages

To learn how to create packages for Shared Device Licensing, follow the instructions:

  1. Log in to the Admin Console and navigate to Packages > Packages. The history of all packages created by all admins in your organization is displayed.

    If you have not created any packages as yet, you are presented with the following screen to help you get started.

    Start creating a package
  2. Click Create a Package.

    Create a Package
  3. Select Shared Device Licensing from the given licensing options that are displayed on your screen.

    Types of licensing
  4. On the Entitlements screen, choose the required entitlement and click Next.

  5. On the System screen, select the required options and then click Next.

    • Choose a 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: Enables you to create a package that deploys in the OS language of client machine. When not available, the OS language is the default fallback language in which the package is deployed.
    System screen
  6. On the Choose Apps screen, click the plus icons next to the corresponding applications to include them in the package, and then click Next.

    Select the Show older versions check box to display the list of supported previous versions, if any.


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

  7. On the Options screen, select or enable the required options and then click Next.

    Options screen

    Creative Cloud Desktop Options:

    • Enable self-service install: Allow end-users to install and update applications from App panel on the Creative Cloud Desktop app.
    • Allow non-admin to update and install apps: Enables the self-service end users, who do not have Administrative privileges, to install and manage their applications and updates.
    • 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.


    Certain Creative Cloud Desktop Applications require you to keep file syncing enabled.

    If you disable file syncing:

    • All apps load.
    • CC files are not synced. Note that this also applies, for example, to media files in Rush projects.
    • Adobe Fonts are available.
    • Stock search is available (however, Federated IDs are unable to download previews)


    To use Lightroom CC, you must enable File Sync and the users must have access to Cloud storage by one of the following methods:

    • Having access to 2 GB of storage with Adobe Spark.
    • Note that the Photos service is not available with Adobe Spark.
    • Having access to 100 GB of storage from a Creative Cloud license.

    This applies to all user identity types: Adobe ID, Enterprise ID, and Federated ID. Note that if you’ve chosen Open Access in the associated product profile, your users’ Adobe IDs do not have to be added to the Admin Console. For details see, Manage shared device license profiles. Enterprise ID or Federated ID type users, however, will need to be added to the Admin Console.

    If you cannot enable File Sync or provide storage, you need to use Lightroom Classic or use Named User licensing.

    • Enable browser based login: By default, users will need to sign in using the Creative Cloud desktop app. However, you can choose to redirect users to sign in via the browser. Choose this option to ensure users sign-in via the browser. For details, see Enable browser-based login.

    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. For more information, see Use Adobe Remote Update Manager.
    • 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 via the Admin Console article.
    • Create a folder for extensions and include the Extension Manager command line tool: Enables you to create a subfolder in your package folder that you can use to include extensions that you want 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. For more, see the Preferences section of thePackaging apps via the Admin Console article.
  8. On the Finalize screen, enter the name of the package, and then click Build Package.

    You can also review the included applications and configuration for this package before building the 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.

    Building Package Message


    If you want to check the remaining time for the existing packages in the details pane, click the row item for the package.

  9. The build status of the package is displayed in the Status column on the Packages page.

    If the package is built successfully, it displays the Download link in the Availability column.

    Packages Status


    A package is available in the Admin Console for up to three days. To check the time remaining to download the package, click the row item for the package. It displays the package details.

  10. To download and distribute the package later, click Download.

    Download link


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.

Deploy packages

After you create the shared device license package, set up the devices in your lab with the license.

Choose from the following methods to deploy the package:

  • Install by double-clicking the package file. See this document for details.
  • Use third-party tools such as Microsoft System Center Configuration Manager (SCCM), Apple Remote Desktop, or JAMF Casper Suite. See this document for details.
  • Deploy using command line on Windows computers. See this document for details.
  • Deploy using Info.plist file on macOS computers. See this document for details.

Deploy updates

Adobe regularly ships updates and new release to its Creative Cloud apps. This gives your students and staff access to the latest and greatest features of all apps that you have deployed to the shared devices in your labs and classrooms. To get the latest Creative Cloud updates, choose one of the following methods:

  • You can create an update package and deploy it manually on the client machines.
  • Or, you can use Remote Update Manager, which uses the Adobe Update server or an internal update server and deploys the latest updates available on update server to each device on which it is run. You don't have to manually push updates to the individual devices.

Uninstall products and licenses

While you create and deploy packages to client machines, you might also have the need to remove previously installed products and licenses. For example, if your organization has migrated from Shared Device Licensing to Named User Licensing, we recommend that you uninstall all the products and licenses previously installed on the machine. Also, there's often the case when client machines may contain multiple versions of apps. Or, may be using conflicting licenses. Client machines, may just simply be consuming extra licenses. And these are not being returned to the deployment pool.

In all these scenarios, we recommend that you use one of these procedures to uninstall the products and / or licenses on the client machines:

  • Use installed package (recommended): Use this method if you have the package files (that you downloaded from the Admin Console) available. Read how to use the installed package.
  • Create uninstall package: Use this method if the package files (that you downloaded from the Admin Console) are unavailable. Read how to create an uninstall package
  • Bulk uninstall: Use third-party tools such as ARD and SCCM to uninstall the package in bulk (and remotely) on client machines.