Caution:

The Creative Cloud Packager cannot be used to create packages that include CC 2019 apps or later. Learn More.

Creative Cloud Enterprise customers can remove old and apply new serialized licensing to end-user machines without reinstalling the software. This article explains how to apply and verify serialized licenses.

You can either apply new serialized licensing or see Solutions, if you are experiencing the following error:

"Your license is expiring"

Note:

Contact your Account Representative or Adobe, if you are unaware about the changes in serialized licensing.

Apply serialized license

Use the Creative Cloud Packager to generate new license files and apply those to your existing user base. The AdobeSerialization and RemoveVolumeSerial application provided must be run with administrative rights. System management tools can be used to deploy these files. No command-line arguments are required. These tools are designed to run silently in the background.

Caution:

Before applying licensing, exit all Adobe applications. They use the licensing files and can damage your licensing if running during this process.

To apply serialized licensing, do the following:

  1. Create the license files.

    Using a valid Creative Cloud ENT serial number, create a set of license files in the Creative Cloud Packager. 

    Use the one year expiring serial number you were provided by your Account Representative, if issued. Otherwise, the Adobe Licensing website contains the most updated Creative Cloud ENT serial numbers. Contact Adobe for assistance locating the correct serial number.

  2. Uninstall the Creative Cloud Desktop application, if installed.

    The Creative Cloud Desktop application is not recommended on serialized machines. Any users that login with a named user license can disrupt serialized licensing.

    Administrative users can run a utility to uninstall the Creative Cloud Desktop application. IT Administrators can silently run a command against machines to remove the application using system management software such as SCCM or Casper. For instructions, see uninstall the Creative Cloud desktop app.

  3. Remove existing serialization from end-user machines.

    Removing your existing expiring serial number prevents future installations using the incorrect licensing. This step removes all Creative Cloud ENT licenses from the machine. Although, a serial number was used to generate the files, it is not required to remove serialization.

    Using the licensing files created previously, run the RemoveVolumeSerial application with administrator rights on the machine or silently with system management application such as SCCM or Casper.

  4. Apply the new serialized licensing.

    The removal and adding of serialization can be combined with a script or task sequence. Applying the license files places the new serial number on the machine and sets it as the active license.

    Using the licensing files created previously, run the AdobeSerialization application with administrator rights on the machine or silently with system management application such as SCCM or Casper.

    Note:

    Additional command-line parameters are not necessary for removing existing serialization or applying new one. The application is designed to run silently. Most users so not even see the command window. The success or failure is recorded in the oobelib.log. For more information, see verify serialized license.

Verify serialized license

There are two methods to verify that your licensing has been applied. The licensing tool logs success and failure in the oobelib.log file. Furthermore, during installation and launch, the products write an ISO file that contains the type of licensing.

Reading licensing tool log files

The RemoveVolumeSerial and AdobeSerialization application write success/failure in the oobelib.log file. If run from a user account, it appears in the user temporary folder. System management tools typically run in System or Root access. These tools place the log in the system log location. 

  • User Log Location
    • Windows
      \Users\<username>\AppData\Local\Temp
    • Mac
      /Users/<username>/Librarly/Logs
  • System and Root Log Locations
    • Windows
      \Windows\Temp
    • Mac
      /tmp

For information on reading the log, see Logging.

Note:

Return code 0 indicates success.

Reading product software tagging (ISO) files

During installation and launch of the Creative Cloud products a software ISO tag is written to the operating system. These can also be used to determine the actual license being used by the product. You can use management systems to scan for the Return codes or software tags to verify the licensing status.

ISO tags are stored in the following locations

  • Windows
    %PROGRAMDATA%\regid.1986-12.com.adobe
  • Mac
    /Library/Application Support/regid.1986-12.com.adobe

Important information for license verification

  • These files are typically generated on installation and product launch. Running the license files does not generate these files.
  • The Creative Cloud Enterprise file resembles regid.1986-12.com.adobe_V7{}CreativeCloudEnt-1.0-{Win|Mac}-GM-MUL.
  • The license being applied to the machine is encoded and near the bottom of the ISO file in a field called <swid:serial_number>. 
  • The encoded version is used by all machines.

To decode the serial number

Self-Service

  1. Use the Create License File mentioned option above to generate license files using your serial number. 
  2. Apply your new serial number to a machine. 
  3. Open the OOBELib.log file and scroll to the bottom. Your encoded serial number appears after LEIDLocForType2A entry written for SN.

Adobe Customer Care

  1. Open a support case through your One Console and include the encoded serial number. 
  2. Adobe representatives can provide you with the last four digits of the decoded serial number. 
  3. You can then match these four digits to the serial number on the Adobe Licensing Website.
swid:serial_number>909606447913687855252363</swid:serial_number>

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