Sentinel LDK and Sentinel HASP Run-time Environment Installer GUI: Readme

# Sentinel® LDK and Sentinel HASP® Run-time Environment Installer GUI for Windows: Readme

## Version 7.32

### April 2015

This document provides information regarding the Run-time Environment Installer GUI for Sentinel LDK and Sentinel HASP, including supported operating systems, enhancements, known compatibility issue, and issues resolved. ("Sentinel LDK" is the next generation of Sentinel HASP.)

The following topics are discussed:

- Operating Systems Supported
- Upgrading the Run-time Environment
- Installing the Run-time Environment
- Accessing Admin Control Center in Internet Explorer Metro Mode
- Compatibility Issues
- Enhancements in This Release
- Issues Resolved in This Release
- Revision History
- Known Issues - Run-time Environment

## Operating Systems Supported

- Windows XP (X86) SP3
- Windows XP (X64) SP2
- Windows Vista SP2
- Windows 7 SP1
- Windows 8.1 SP1
- Windows 10 Technical Preview Build 10041
- Windows Server 2003 SP2
- Windows Server 2008 SP2
- Windows Server 2008 R2 SP1
- Windows Server 2012 R2
- Windows 7 SP1 Embedded standard (x86)

The latest service packs and security updates must be installed.

Back to Topics

## Upgrading the Run-time Environment

When using the Installer GUI to upgrade the Run-time Environment, ensure that:

- No other Run-time Environment Installer is active.
- No other Run-time Environment components are active. Although the installation program terminates applications that are accessing the Run-time, it does not terminate running services. For example, if the Sentinel License Manager is running as a service, you must stop the service before upgrading the Run-time Environment.

Back to Topics

## Installing the Run-time Environment

- The Installer GUI detects the version of the operating system during Run-time Environment installation, before installing the relevant drivers.
- By default, Windows Vista (and later) operating systems display a User Account Control message during driver installation. The user must click Continue to continue the installation. Alternatively, the user can change the default setting from the Control Panel of their operating system.
- A log file of the installation process is written to aksdrvsetup.log in the Windows directory.

Back to Topics

## Accessing Admin Control Center in Internet Explorer Metro Mode

Under Windows 8, Internet Explorer 10 can be operated in "desktop" style or "Metro" style. When users attempt to access Admin Control Center for the local License Manager in the Metro style browser, they get the message "This page can't be displayed". (This problem does not occur when a user attempt to access Admin Control Center for a remote License Manager.)

To access Admin Control Center for the local License Manager under Windows 8 with Internet Explorer 10, the user must do either of the following:

- Operate Internet Explorer in desktop style:
  1. After you receive the message "This page can't be displayed" in Metro style, click the wrench icon at the bottom right of the browser window.
  2. Click View on the desktop. Admin Control Center is displayed.
- Enable Internet Explorer to access Admin Control Center in Metro style:
  1. After you receive the message "This page can't be displayed" in Metro style, click the wrench icon at the bottom right of the browser window.
  2. Click View on the desktop. Admin Control Center is displayed.
  3. Click the cogwheel ("Tools") icon at the top right of the browser window. From the menu, select Internet options > Security. Select the Trusted sites zone. Click the Sites button.
  4. "http://localhost" is already filled in. Click Add. Close the screen.

Back to Topics

## Compatibility Issues

### Control Guard Agent

When Control Guard Agent version 4.0.0.27 is present on a computer, installation of the Run-time Environment will cause the operating system to crash. If this occurs, update to a later version of Control Guard Agent.

### Trend Micro OfficeScan

When Trend Micro OfficeScan is present on a computer, installation of the Run-time Environment may stall.

Trend Micro has released the following hotfix to resolve this issue: Trend Micro OfficeScan 10.6 Service Pack 3 Patch 1.1 Hot Fix - Server Build 5592 and Client Module Build 5445.

Contact the Trend Micro support team to obtain this hotfix. See the readme file included in the hotfix for more details.

Back to Topics

## Enhancements in This Release

Reference | Description
--- | ---

LDK-6934

Sentinel LDK Run-time Environment now supports the SentinelHL Drive microSD key (patent pending). This key has been tested with the following microSD cards:

- Sandisk: 16 GB, 64 GB
- Transcend: 16 GB, 64 GB
- Toshiba: 32 GB
- Samsung: 64 GB
- Kingston: 64 GB, 256 GB, 512 GB

LDK-10090 | Run-time Environment is now supported under Windows 10 Technical Preview Build 10041.

Back to Topics

## Issues Resolved in This Release

Reference | Description
--- | ---

LDK-9325

Given the following circumstances:

- An SL key contains a Feature that allows concurrency but does not allow virtual machines.
- The SL key is installed on a physical machine.

When the SL key is displayed in Admin Control Center on a second physical machine, the Feature is shown as "disabled". However, a protected application that includes that Feature operates correctly.

LDK-8862 | When attempting to access a remote License Manager, Sentinel Admin API would return the incorrect error code SNTL_ADMIN_LM_NOT_FOUND (6002).

LDK-7237

Given the following circumstances:

1. A license with concurrency is installed on a Sentinel protection key. The count criteria is "Per Login".
2. Protected applications that consume seats from the license are started.
3. While the applications are active, the license is updated to change the count criteria (for example, from "Per Login" to "Per Process").
4. One or more protected applications are closed.

The Login count for the license would no longer match the number of actual applications active.
As part of the resolution for this issue, when the count criteria for a network license is modified, all active sessions are automatically terminated.

Back to Topics

## Revision History

### Enhancements in Version 6.65

Reference | Description
--- | ---

LDK-4468

The template for customizing entries for the Access log in Sentinel License Manager has been enhanced.

- A new log element (functionparams2) is available.
- Tags for special characters that could not be used in the template until now are provided.
- Existing elements (sessioncount, logincount, loginlimit) that did not provide reliable results have been corrected.
- The following events are now logged correctly: session timeout, orphaned session logout, manual disconnect, AdminAPI disconnect.

In addition, the template is now used for log entries generated by Embedded License Managers and External License Managers.
For information on the log template, see the Edit Log Parameters screen and related help screen in Admin Control Center. (Click the Edit Log Parameters button from the Configuration - Basic Settings screen.)

LDK-735

Admin Control Center now enables the user to generate a C2V file without the requirement of installing the RUS utility. This is supported for Windows, Mac and Linux platforms. The following limitations apply:

- HL Basic keys are not supported.
- C2V files fetched from HASP HL and Sentinel HL (HASP Configuration) keys will not work with Business Studio.

The C2V file can be generated for locally-connected Sentinel HL, HASP HL, and SL AdminMode keys.

### Issues Resolved in Version 6.65

Reference | Description
--- | ---
LDK-7893 | The License Manager would fail when it attempted to scan more than 128 remote servers. The message “Failed to begin fridge transaction:327683” was displayed.
LDK-7084 | The hasp_get_info() function in the Licensing API did not return consistent results for localhost when no IP address set in etc\hosts file for localhost. The function would return either localhost(127.0.0.1) or IPv4. To resolve this issue, the Licensing API must be upgraded to version 7.3 or later and the Run-time Environment must be upgraded to version 6.65 or later.
LDK-5710 | When the real-time clock battery in a Sentinel HL (Driverless configuration) keys is exhausted, the error code returned by the hasp_login or hasp_login_scope function was HASP_INT_ERR instead of HASP_NO_BATTERY_POWER.
LDK-5390 | If hasplms.exe is locked at the time the user attempts to upgrade the Run-time Environment, a misleading error message was displayed. The error message now provides an appropriate description of the issue.
LDK-8895 | When an activated SL-Legacy license is installed on a machine that contains Products that have clone protection disabled, and a user then attempts to detach a license, error 64 (clone detected) was generated. Now a license can be successfully detached.
LDK-8936 | Installation of certain third party tools would cause the removal of a symbolic link from Hardlock drivers. As a result, HL keys would become inaccessible.

### Issues Resolved in Version 6.64

Reference | Description
--- | ---
LDK-6857 | A compilation error would occur when the RTE 6.62 haspds.msm merge module is used with a WIX-MSI installer.
LDK-7030 | A Stop error (BSoD) would occur when the customer applied a V2C on a machine with a dynamic disk.

### Issues Resolved in Version 6.63

Reference | Description
--- | ---
LDK-6642 | A Stop error (BSoD) was reported with certain flash drives (if connected).

Back to Topics

## Known Issues - Run-time Environment

Reference | Description
--- | ---
12506 | Sentinel LDK communicates via TCP and UDP on port 1947. This port is IANA-registered exclusively for this purpose. At the end user site, the firewall must be configured so that communication via this port is not blocked.
180256 | When a computer names contains UTF-16 characters, Admin Control Center displays the short name for the computer (similar to Windows Explorer). Similarly, the sntl_admin_get function in Admin API returns the short name.
182646 | After Windows 7 is upgraded to Windows 8, the user is not able to use existing SL licenses or to install new SL licenses. Workaround: After you upgrade from Windows 7 to Windows 8, reinstall the Run-time Environment.

LDK-2471

Sentinel Licensing API: On a computer with the Nvidia chip set GeForce 7025/nForce 630a, and where the CPU is AMD Athlon 64 X2, the hasp_read and hasp_encrypt functions may fail with error 39, HASP_BROKEN_SESSION. This problem only exists with HASP HL keys with Firmware version 3.25.
Workaround 1: On the computer described above, when error 39 is returned, call the hasp_read or hasp_encrypt function again. It is not necessary to call hasp_login again.
Workaround 2: Use Sentinel HL keys with Firmware version 4.2x.

LDK-5038 | It is not possible to retrieve the hard disk drive ID in SL-AdminMode fingerprints for Dell PowerEdge R710 and PowerEdge T410 machines.

LDK-8480

With some new USB chipsets, it is possible that the API hasp_update() call, used to update the firmware of Sentinel HL keys to version 3.25, will generate the HASP_BROKEN_SESSION return code, even if the firmware is correctly updated. (This issue does not occur with Sentinel HL Driverless keys with firmware version 4.x.)
Workaround: Install the latest Run-time Environment. The automatic firmware update feature of the License Manager will automatically update the firmware of the key the first time that the key is connected, without the need to call hasp_update().

Back to Topics

Copyright © 2015 SafeNet, Inc. All rights reserved.

DocID 118r Revision 1505-2