Situations That Require Sentinel LDK Run-time Environment
Sentinel LDK Run-time Environment is a system component that enables communication between a protected application and a Sentinel protection key. Sentinel LDK Run-time Environment also contains Sentinel Admin Control Center, used to manage licenses.
Installation of Sentinel LDK Run-time Environment requires administrator privileges on the target computer. However, on a Windows or Linux computer, Sentinel LDK Run-time Environment is not required for all protected applications.
The tables that follow indicate when a protected application requires Sentinel LDK Run-time Environment to execute.
Note the following:
>Sentinel LDK Run-time Environment is always required when any of the following are true:
•The protected application executes on a Mac machine.
•The protected application uses the Data File Protection module to encrypt and decrypt data in an external file AND the application was protected using Sentinel LDK v.7.0 or earlier.
•The application is linked with libhasp_windows_bcc_vendorId.lib.
•In addition, Sentinel LDK Run-time Environment is required on any machine that will access the Sentinel LDK-EMS Customer Portal to perform online activation or online update of protection keys.
Standalone Licenses
A Standalone license is for a single protected application that executes on the computer where the protection key is located (no concurrency).
The table that follows indicates when a protected application with a Standalone license requires the presence of the Run-time Environment.
Detachable Licenses
To attach a Detached license to a protected application installed on a remote computer, the Run-time Environment must be installed on the remote computer.
Network Seat Licenses
When a Network Seat license is installed on a given computer, the License Manager on the computer can serve network seats to protected applications than run on the same computer or on remote computers in the same network.
>The Run-time Environment is required on the computer where the Network Seat license is located.
> The Run-time Environment is not required on the remote computer where the protected application executes.
The following Sentinel protection keys support Network Seat licenses:
>SL AdminMode keys with concurrency
>SL Legacy keys with concurrency
>HL (HASP configuration) Net and NetTime keys
>HL (Driverless configuration) keys with concurrency – all types except for Basic
NOTE If all of the following are true:
>A Network Seat license is installed on an HL (Driverless configuration) key.
>The HL key is located on the same machine as a protected application that consumes a network seat.
>The local Admin LM is an older version than the Integrated/External LM.
The access attempt may fail with the error HASP_OLD_LM.
To ensure full functionality, Thales recommends that you install the latest RTE whenever you update the deployed Integrated/External LM.