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 on to 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.
To learn how to create packages for Shared Device Licensing, follow the instructions:
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.
Click Create a Package.
Select Shared Device Licensing from the given licensing options that are displayed on your screen.
On the Entitlements screen, choose the required entitlement and click Next.
On the System screen, select the required options and then click Next.
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 Show older versions to display a list of previous versions of the apps. Enterprise admins can view more versions that don't receive security or feature updates by selecting Available application versions in package preferences (Admin Console > Packages > Preferences). For more information, see Packaging apps using Admin Console.
To know what versions are supported for your Creative Cloud plan, review the Creative Cloud Support policy.
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.
On the Options screen, select or enable the required options and then click Next.
Creative Cloud Desktop Options:
Certain Creative Cloud desktop apps require you to keep file syncing enabled.
If you disable file syncing:
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.
If you want to check the remaining time for the existing packages in the details pane, click the row item for the package.
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.
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.
To download and distribute the package later, click Download.
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.
The package that you download, contains a Packageinfo.txt file. This file has the information such as the following about that package:
The PackageInfo.txt file is for informational purposes only.
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:
Adobe regularly ships updates and new release to its Creative Cloud apps. This way, your students, and staff can access the latest features of apps that you deployed to the shared devices in your labs and classrooms. To get the latest Creative Cloud updates, choose one of the following methods:
While you create and deploy packages to client machines, you might also require to remove previously installed products and licenses. For example, if your organization migrated from Shared Device Licensing to Named User Licensing, 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 be consuming extra licenses, which are not 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: