Feature Restricted Licensing is recommended for organizations that have very specific needs to control data flow in and out of locked down or restricted network environments. Use this licensing model for end users who either don't have access to the internet or are not allowed to use online services. Note that FRL restricts access to certain Adobe apps and services for your end users.

Use Feature Restricted Licensing (FRL) when your end users either do not have access to a network environment or are not allowed to use online services. For more details, see the Licensing overview article.

Types of FRL packages

As an Admin in your organization, you can create the following types of FRL packages:

Connected Activation packages

Use this package to meet the needs of end-users who cannot adopt Named User Licensing since these users are not allowed to use online services. However, these users are periodically connected to the Internet.

Create a Connected Activation package

  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 no packages have been created in your organization as yet, you are presented with the following screen to help you get started.

    First time user experience
  2. Click Create a Package.

    List of packages
  3. Choose Feature Restricted Licensing, click Next.

    Feature Restricted Licensing option
  4. On the Activation Method screen, choose Connected Activation and click Next.

    Activation method
  5. On the Entitlements screen, choose the required entitlement and click Next.

    Entitlements
  6. 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).
      Note: It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't be deployed on a 64-bit machine. Also, a 64-bit package can't be deployed on a 32-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. In which case, the OS language is the default fallback language in which the package is deployed.
  7. On the Choose Apps screen, add the required applications to the package and click Next.

    License-only package:

    Every package is bundled with an FRL License file. This means that to create a license-only package, simply click Next; without adding any applications to the package.

    Create license-only packages to deploy on end-user computers where applications are already deployed but without licenses or with trial licenses.

    Choose apps

    Note:

    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.

  8. On the Options screen, select the required options and then click Next.

    • Enable Remote Update Manager: Enables you to run the updater remotely on the client machine with the benefit of executing as an administrator. For more information, see Remote Update Manager.
    • Redirect to internal Adobe 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 the Packaging apps via the Admin Console article.
  9. On the Finalize screen, in the Name box, enter the name of the package.

    You can also review the included applications and configuration for this package before building the package.

  10. Click Build Package.

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

    FRL Package Building Status

    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 3 days. To check the time remaining to download the package, click the row item for the package. It displays the package details.

    FRL Package Details
  11. To download and distribute the package later, click Download.

Isolated Activation packages

Isolated Activation packages are installed on devices that do not have access (even temporary) to the internet. This is meant for devices on which you need to install licenses directly along with their licensing package and applications. This method requires that the admin run the Adobe Licensing Toolkit once on each isolated computer to be licensed.

Use Adobe Licensing Toolkit to generate unique client codes

Adobe's Licensing Toolkit is a command line utility used to generate unique client codes for FRL Isolated Activation packages. Isolated Activation packages are created for users who do have any access to any network environment. For these users, the packages need to completely self-contained. This means that the licensing information for the package must be contained within the package. To create packages that are bundled with licensing information, you first need to use the Licensing Toolkit to generate unique client codes. After you have generated clients codes (for a single or multiple computers), go ahead and create the Isolated Activation package described in the following section.

Create Isolated Activation packages

After you have generated the unique client codes, follow these steps to create an Isolated Activation package:

  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 no packages have been created in your organization as yet, you are presented with the following screen to help you get started.

    First time user experience
  2. Click Create a Package.

    List of packages
  3. Under Feature Restricted Licensing, click Next.

    Feature Restricted Licensing option
  4. Choose Isolated Activation and click Next.

    Activation method

    Note:

    Download the Licensing Toolkit using the download links (for Mac or Windows) if you have not downloaded yet.

  5. Enter the unique client codes that you generated using the Adobe Licensing Toolkit.

    OR

    If you created a CSV file for multiple computers, upload the CSV file.

    OR

    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.

    Enter unique client codes

    Note:

    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 experiene issues when using the associated apps.

  6. On the Entitlements screen, select the required entitlements and then click Next.

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

    • Platform: Choose the operating system and the processor support (32 bit or 64 bit). 
      Note: It's necessary to make separate packages for 32-bit and 64-bit installations. A 32-bit package can't be deployed on a 64-bit machine. Also, A 64-bit package can't be deployed on a 32-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. In which case, the OS language is the default fallback language in which the package is deployed.
  8. Click the Plus icons next to the corresponding applications to include them in the package, and then click Next.

    License-only package:

    Every package is bundled with an FRL License file. This means that to create a license-only package, simply click Next; without adding any applications to the package.

    Create license-only packages to deploy on end-user computers where applications are already deployed but without licenses or with trial licenses.

    Choose apps

    Note:

    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.

  9. On the Options screen, select the required check box to enable the corresponding options and then click Next.

    • Create a folder for extensions & 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 directory. The directory is defined in the Packages > Preferences tab in the Admin Console. For more, see the Preferences section of the Packaging apps via the Admin Console article.
  10. 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.

    Finalize screen

    It displays the building status of the package in the Status column on the Packages page.

    Build status

    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.

    Package properties
  11. To download and distribute the package later, click Download.

License-only packages

Create FRL license-only packages that allow you to install only FRL licenses on end-user computers.

More details

Your end users can have previously installed Adobe apps (that are not licensed) or you plan to first license the end-user computers and then license them later. In either of these cases, create license-only packages and install these on the end-user computers. For details on how to install and manage license-only FRL packages, see Adobe Licensing Toolkit.

To create license-only packages, follow the procedures to create FRL packages detailed in this document:

Connected Activation packages

Isolated Activation packages

Product-only packages

Create product-only packages that allow you to install only products on end-user computers.

More details

Your end users can have previously installed licenses (see license-only packages) or you can install trial apps on their computers. In either of these cases, create product-only packages and install these on the end-user computers.

To create product-only packages, follow the procedure to create Isolated Activation packages detailed in this document.

Acrobat DC currently cannot be included in FRL package

Caution:

In the following procedures, if you choose an entitlement that includes Acrobat DC, the option to choose Acrobat DC is currently disabled in the Available applications list. FRL support for Acrobat DC will be added at a later date.

If you need to create a package that includes Acrobat DC, you can either create a Named User licensing package or you can use the Creative Cloud Packager to create a serial number package.

Acrobat DC not enabled

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy