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.
Isolated Feature Restricted Licensing is a method of licensing Adobe Creative Cloud apps on computers that are segregated from networks to protect critical data and systems. In this method, the licenses are installed directly on the computers along with the apps using an Isolated activation package. The package is self-contained, and includes the licensing information specific to the computers where it is installed.
For an Isolated Feature Restricted Licensing package to include licensing information specific to a computer, include the activation code for the computer when generating the package. You can generate activation codes for each computer using Adobe's Licensing Toolkit. After you have generated client codes, create an Isolated Feature Restricted Licensing package in the Admin Console, and deploy it on a user machine.
The Isolated Feature Restricted Licensing option appears in your Admin Console only when Adobe entitles your organization to use this type of licensing. The option does not appear by default.
Launch an application on your computer. The license activates automatically.
To license the Creative Cloud apps on user computers, run the Adobe Licensing Toolkit on each computer. The tool provides a CRC32 checksum of the computer’s machine ID that Adobe uses to issue a corresponding license. CRC32 is not a machine ID, device ID, or any device identifiable information.
The license expiration date is the organization's contract end date.
After you've generated the activation codes, perform these steps to create an Isolated Feature Restricted Licensing package.
Click Create a Package.
Choose Feature Restricted Licensing, and then click Next.
Choose Isolated Activation, and click Next.
Enter the activation codes that you generated using the Adobe Licensing Toolkit.
If you created a CSV file for multiple computers, upload the CSV file.
To create a product-only package, leave the Activation Code box empty and don't upload a CSV file. Use this option is if you want to create install media and licenses separately.
Ensure that you enter the correct license code that you generated using the Licensing Toolkit. This procedure does not check the validity of the error codes that you enter in this step.
However, if you enter invalid license codes, your end users will experience issues when using the associated apps.
On the Entitlements screen, select the required entitlements and then click Next.
On the System screen, select or enable the required options and then click Next.
On the Choose Apps screen, you can choose to create one of the following types of packages:
Type of package
Create this package if the client machines already have Creative Cloud apps installed. Later, you can simply license the installed apps. For example, apps were previously installed using another licensing method. And you want to now license those apps with a Feature Restricted Licensing - Isolated license.
From Available Applications, add only the License File to Selected Applications.
Create this package if the client machine is already licensed with a Feature Restricted Licensing - Isolated license. Then, install apps on the machine.
To generate an Apps-only package, on the Activation Code screen, click Next without entering any challenge code.
Package containing apps and license
Create this package to install and license Creative Cloud apps on a client machine. For example, if you have not previously installed Creative Cloud apps on a machine.
From Available Applications, add applications and the License File to Selected Applications.
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 products are added automatically. For example, if you add Photoshop, the dependent products Camera Raw and Adobe Preview are added automatically.
After you're done with your selections, click Next.
On the Options screen, select the required check box to enable the corresponding options, and then click Next.
In the Name box, 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 the building status of the package in the Status column on the Packages page.
If the package is built successfully, it displays the Download link in the Availability column of the respective package row.
If you want to check the remaining time for the existing packages to download, click the row item for the package. It displays the package details.
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.
To download and distribute the package later, click Download.
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 feature restricted license package, set up the end-user machines with the license:
For details on troubleshoot Creative Cloud apps installation and uninstallation errors, see this document.
If your organization renews the contract, and you require to relicense your users. To get the latest apps, deploy a new package that includes the apps. Deploy a new package to update the apps following a contract renewal. You can either create a package or update a previous package, by performing the following steps:
Click the expired package you want to update.
In the package details pane, click Update Package.
Download the updated package and deploy to user machines.
You can remove a license from a computer in the following scenarios:
Use Adobe's Licensing Toolkit to remove a license. Adobe Licensing Toolkit is a command-line utility that is used to activate or uninstall licenses. It is available in the licensing package that you download from the Admin Console. Alternatively, you can download it directly from the Admin Console under Packages > Tools.
To remove a license, run the following commands with admin privileges:
adobe-licensing-toolkit.exe --precondition --uninstall --filePath <absolute path of the .json file>
sudo ./adobe-licensing-toolkit --precondition --uninstall --filePath <absolute path of the .json file>
For more information, see these steps.
The .json file can be found within the Isolated Feature Restricted Licensing package that was downloaded from the Admin Console and deployed to the user machine. The file contains the licensing information.
In the scenario where multiple licenses have been installed on a single machine, run the following commands with admin privileges to remove the licenses:
adobe-licensing-toolkit.exe --precondition --uninstall --all
sudo ./adobe-licensing-toolkit --precondition --uninstall --all
For more information, see these steps.
Besides removing licenses from a user's computer, you can uninstall the license and the products. By using the Feature Restricted Licensing packages, themselves.
Read the details on how to uninstall packages from a user's computer.
When generating activation code, only the CRC32 checksum of the computer’s device ID (Sha 256) is shared with Adobe. The information shared is not device-identifiable.
Every package is bundled with a license file. To create a license-only package, skip adding any applications to the package.
Create license-only packages to deploy on client computers where applications are already deployed but without licenses or with trial licenses.
Isolated Feature Restricted Licensing licenses expire on the date the contract ends.
Following a contract renewal, the admin can choose to relicense their users by:
Isolated Feature Restricted Licensing does not support Adobe Applications in virtualized environments.
When the admin removes a feature restricted license for an isolated activation package, the license count will not be updated on the Admin Console. It is because there was no communication with the Adobe licensing servers after the package was deployed.
To identify the activated packages on a client computer, follow these steps.
This command displays the licensing information for all the apps installed on a computer.
Adobe Licensing Toolkit (0.1.5.57) License Details NpdId : MWVjZGNlMzMtZGU2Yi00ZmNlLTkzZTktY2MxMjBhZmFiZjg1 AppId : Photoshop1 DeploymentMode : FRL_ISOLATED CacheExpiry : 03/06/19 20:01:56 India Standard Time LicenseId : 511F26523959D15EBD9B LicenseExpiry : 03/06/21 20:01:56 India Standard Time NpdId : YjZiOGU0ZTItYTkxNy00NTFlLWFkOTItZTljNTc2M2U2OTgx AppId : Animate1 DeploymentMode : FRL_CONNECTED Operation Successfully Completed
In the filtered list of packages, click the package. The details of that package are displayed on the right.
The Package License ID on the Admin Console corresponds to the NpdId on the Licensing Toolkit command, above.
Use this to identity the packages installed on a client computer.
The Package License ID is only available for packages created on or after 7/24/2021.