This document describes the DisableDongle utility which is used to disable Harlequin HLS dongles when performing a transition from HLS to LDK‐secured RIP.


Note: Once disabled, a disabled dongle cannot be reactivated in the field. Before attempting to use the utility ensure the prerequisites are met.


Prerequisites (IMPORTANT – Please Read)

Before the DisableDongle utility can be used the SafeNet SuperPro dongle drivers must be installed. In addition to this the Sentinel LDK runtime environment must be installed which also installs the Sentinel LDK License manager, run as a Windows service or as a daemon on Linux. When the Sentinel LDK runtime environment is installed the Admin Control Center, a web‐based control application, becomes available.


SafeNet SuperPro dongle drivers

If the dongle is being disabled on the computer on which it has previously been securing a Harlequin RIP these drivers will be in place already. If they are not, they have been supplied with Harlequin RIPs for many years and can easily be installed.


Sentinel LDK runtime environment

When the Sentinel LDK runtime environment is installed as part of an LDK secured RIP installation, the Sentinel LDK License server, run as a Windows service or as a daemon on Linux is installed.


If you did not install the RIP on Linux as superuser see the Developer’s guide for infor‐ mation on how to install and start the runtime.


When the Sentinel LDK runtime environment is installed the Admin Control Center, a web‐based control application, becomes available.


The Sentinel LDK license server must be installed and running either on the same computer that the dongle is being disabled on, or somewhere on the same subnet of the same network. Also, a Global Graphics LDK product key must have been activated on that server prior to using DisableDongle. The activated product is of no consequence, that is, it can be for any LDK secured product.


If the Sentinel LDK License server is not on the same computer as the dongle, the LDK runtime must be installed on that machine.

This condition is fulfilled in either of the following cases:

  • A new LDK‐secured RIP has been installed and activated on the same machine as the old RIP and the dongle is being disabled on this same machine.
  • A new LDK‐secured RIP has been installed and activated on a new computer, and that computer is connected to the same subnet as the old RIP computer on which the dongle is being disabled. The LDK runtime must be installed on the old RIP computer before using DisableDongle.
  • The dongle is being disabled on a computer in a dealer’s or OEM’s offices and there is an LDKsecured Harlequin RIP somewhere on the same network and the LDK runtime is installed on the machine on which DisableDongle is used.

If the Sentinel LDK license server is running on a different machine from DisableDongle, open the Sentinel Admin Control Center on the computer to which the dongle is attached and click through to the Configuration::Access to Remote License Managers dialog. Make sure that Allow Access to Remote Licenses, Broadcast Search for Remote License and Aggressive Search for Remote Licenses are all checked. With these selections made the remote license will be discovered automatically.


Procedure to Disable a Dongle

  1. Plug in the dongle you need to disable. Please plug in one dongle at a time.
  2. Go to the folder where the RIP is installed. Then go into the ldk sub-folder.



You will see the file –


disabledongle.exe


Click on the path bar at the top to select the path. The right-click in the empty area in the path bar and select the option Copy.



This will copy the path to disabledongle.exe to the clipboard.

  1. Go to the Start menu and select All Programs. Click on Accessories, then click on Command Prompt.



The Command Prompt window will be prompted.



At the prompt, type in –


cd  <space>



Right-click on the Command Prompt window and select Paste to paste the path to disabledongle.exe.


Click the Enter key.


The current path will be changed to the location where disabledongle.exe is.



  1. You can now type in the command to display the info for the dongle plugged into the computer, type –


disabledongle -report



Click the Enter key to execute the command.


The disabledongle.exe tool will show a short report for the dongle plugged into the computer.



Please check that the serial number is the same as the dongle that you need to disable.


  1. This step will now disable the dongle permanently.


Please double-check that you have the correct dongle as reported in the previous step plugged in.


To disable the dongle, type in –


disabledongle -disable <serial number for the dongle>


e.g.


disabledongle -disable 55048



Click the Enter key to execute the command.


  1. The dongle is now disabled and a report is shown.



A certificate file will be generated for the dongle being disabled at the same location where disabledongle.exe is.


This file MUST be returned to Compose System Limited as proof that the dongle has indeed been disabled.


The certificate file is named –


disabledongle-<serial number>.txt


e.g.


disabledongle-55048.txt



How to Check that a Dongle is Disabled


The DisableDongle tool provide an option to check whether a dongle has been disabled.


At the command prompt and with the current path set to the location of disabledongle.exe, type in –


disabledongle -certify <serial number of the dongle>


e.g.


disabledongle -certify 55048


If the dongle is disabled, it will generate the certificate file for the dongle at the same location where disabledongle.exe is


Tool usage

This section explains the usage of the DisableDongle tool.


The DisableDongle utility is located in the ldk subfolder in the folder where the RIP is installed.


The usage is:

Specify one of:


-certify

write file certifying that specified dongle is disabled

-disable

Disable dongle with specified serial number

-report

report details of any connected dongle


Both -certify and -disable require that you specify the serial number of the connected dongle, so as to guard
against accidentally disabling the wrong dongle.


In the command line must be the dongle serial number, not the dongle security number (which, under HLS, becomes the RIP serial number). With -report the utility reports the details of the connected dongle, for example:


DisableDongle.exe -report

Disable Dongle Utility v1.1r0 Found supported SuperPro dongle:

Customer no:11: Security no: 63759-64: Serial no:47917: Platform: Windows 32-bit

This dongle will enable Harlequin RIP v7, v8 and v9

An upgrade password is required to enable

Harlequin MultifRIP v2, v3, v10


This is the same as is reported in the License Manager and LDK Tool.


With -disable the utility disables the dongle and then reports that it has been disabled, and the name of the “certificate” file:


DisableDongle.exe -disable 47917

Disable Dongle Utility V1.1r0 Found SuperPro dongle:

Dongle serial no: 47917 Disabling dongle …

Successfully disabled dongle: 47917

Generating disabled dongle certificate … Disabled dongle certificate written to:

D:\swhope\trunk\spro21dk\disableddongle- 47917.txt

PLEASE ENSURE THAT THE DONGLE IS PHYSICALLY DESTROYED ONE RECEIPT OF THE CERTIFICATE HAS BEEN ACKNOWLEDGED


With -certify the utility just does the second part of this, having confirmed that the attached dongle has been disabled.


The certificate file, which is written to the current directory, contains:

type disableddongle-47917.txt

Disable Dongle Utility v1.1r0 Dongle serial no: 47917

Original Customer no: 11: Original Security no: 63759-64 Dongle disabled on 2014-12-15 at 16:26 by theuser

0090 00FF 0012 DE63 AD7F 0047 00E0

TheUser2

2014-12-15 16:26:24

644EF63F0A4CDE76B1208D840774 3724646756

Where:

  • the original values and Dongle disabled on are read from the dongle,
  • TheUser2 is the login name of the user who generated the certificate (not necessarily the same as the earlier ʺtheuserʹ who did the disabling),
  • 2014-12-15 16:26:24 is the date and time that the file was created,
  • Other values are Global Graphics proprietary information.


If a disabled dongle is connected -report reports:

DisableDongle.exe -report

Disable Dongle Utility v1.1r0

Found disabled SuperPro dongle:

Serial no: 47917

Original Customer no: 11: Original Security no: 63759-64

Dongle disabled on 2014-12-15 at 16:26 by theuser


Detecting disabled dongles

If a dongle is reported as not working you can detect whether or not it has been disabled by:

  • Using DisableDongle –report
  • Using the Display keys option in the LDK Tool (from HMR v10.1r1 and HHR 4.1r1)


Note: From HMR 10.1r1 the GetDongleInfo utility will refuse to record HLS license details if the attached dongle has been disabled. The GetDongleInfo tool shipped with 10.0r2 and 10.1r0 will attempt to record HLS license details, but the recorded information such as the customer number will be incorrect in the .superpro file.


Note: Once disabled, a disabled dongle cannot be reactivated in the field.