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.
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.
- 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.
On the Choose Apps screen, click the plus icons next to the corresponding applications to include them in the package, and then click Next.
1. To display the list of previous versions of the apps under Available applications, select the Show older versions check box.
2. 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.
Creative Cloud Desktop Options:
- 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. Prevents syncing the files of multiple users who use a single device.
Certain Creative Cloud Desktop Applications require you to keep file syncing enabled.
- 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.
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 upto three days. To check the time remaining to download the package, click the row item for the package. It displays the package details.
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.