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

## Installer Version 6.62

## Package Version 6.62

### May 2014

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.)

## Operating Systems Supported

- Windows XP SP3 (x86)
- Windows XP SP2 (x64)
- Windows Vista SP2
- Windows 7 SP1
- Windows 8.1
- Windows Server 2003 SP2
- Windows 2008 SP2
- Windows 2008 R2 SP1
- Windows Server 2012 R2
- Windows XP Embedded standard (x86)
- Windows 7 SP1 Embedded standard (x86)

The latest service packs and security updates must be installed.

## Changes in Terminology

With the introduction of Sentinel LDK, changes to terminology were incorporated in Sentinel Admin Control Center user interface and help files as follows:

- The Sentinel HASP product is now referred to as Sentinel LDK.
- SL keys that were created with Sentinel HASP Business Studio now appear in the user interface as "SL-Legacy" keys.
- References to "Sentinel EMS" in the help files are also valid for Sentinel HASP Business Studio.

## 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.

## 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.

## 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.

## Compatibility Issues

- 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.

## Issues Resolved in This Release

Reference | Description
--- | ---
LDK-6113 | After an end user installed Sentinel LDK Run-time Environment v.6.61, applications that are protected using older versions of HASP4 or Hardlock would not start. Applications that are protected using older versions of HASP4 or Hardlock, or that use older versions of HASP4/Hardlock API would display the message: Driver version mismatch. These issues existed under the following circumstances: These issues existed only with HASP4 API version 8.x or earlier or Hardlock API version 3.83 or earlier. These issues do not exist with the Sentinel LDK API library that also supports the HASP4 and Hardlock API. Support for legacy HASP4 and Hardlock APIs has been restored in Sentinel LDK Run-time Environment v.6.62.

## Version History

### Enhancements in Version 6.61

Reference | Description
--- | ---
LDK-3483 | Admin Control Center now correctly displays information regarding Sentinel HL Board
LDK-3366 | The Local License Manager is now more resistant to potential sources of corruption, such as power failure.
LDK-2877 | Cloned SL-AdminMode keys are now correctly identified by the License Manager and become inaccessible. As soon as the cloned keys or machines are removed, the single remaining key is automatically be re-enabled.
LDK-3129 | Support for SL keys under VM live migration solutions is now provided.

Issues Resolved in Version 6.61

Reference | Description
--- | ---
LDK-5038 | It was not possible to retrieve the hard disk drive ID in SL-AdminMode fingerprints for Dell PowerEdge R710 and PowerEdge T410 machines.
LDK-4821 | Protected application with encrypted swf would not start under Windows 8.1 32-bit. The message "Error E0025 - unknown error" was returned.
LDK-4787 | Documentation has been corrected to state that it is not possible to install vendor-specific SL-UserMode V2C bundled in a branded Run-time Environment.
LDK-4543 | When a Feature that is disabled for virtual machines is installed on a virtual machine, the Run-time Environment did not return the usable tag as false.
LDK-4533 | Memory leaks in the Sentinel Licensing API have been resolved.
LDK-3970 | When a Provisional SL-Legacy license is installed on a machine with Run-time Environment v.6.60, its Product names were not displayed in Admin Control Center.
LDK-3283 | The License Manager would require several minutes to load when Flash Media Bay Reader is connected to the system.
LDK-3255 | A Stratus server would stop responding during synchronization when the Run-time Environment is installed.
LDK-3092 | The Sentinel Admin API function sntl_admin_get would not filter information correctly based on scope template for feature/machine/user tags (Feature ID, computer name or IP address, License Manager user name).
LDK-3005 | In Admin Control Center, an inconsistency existed regarding the display of "allow=all" in "Users" and "Access from Remote Clients" restriction tabs of the Configuration page.
LDK-3885 | Under Windows 8.1 (x86 platform), the Hardlock driver would not detect NtTerminateProcess and NtTerminateThread SST indexes. As a result: When starting a protected application, the Secure Channel Communication error (H0046) would occur. A Stop error (BSoD) would occur.
LDK-2975 | When SkyRecon StormShield Agent version 5.6 is present on a computer, installation of the Run-time Environment would cause the operating system to crash.

### Enhancements in Version 6.60

Support has been added for Windows XP Embedded and Window 7 Embedded.

### Issues Resolved in Version 6.60

Reference | Description
--- | ---
LDK-2119 | After cancellation of an SL AdminMode license on a machine, Features would disappear from other Products and become unusable.
189473 | Under certain circumstances, the License Manager would fail with HTTP scanners.
LDK-1892 | For a "6to4" IPv6 address, network licenses would not be available (disconnect from the NetKey) after a short period. Now the License Manager scans the network interfaces to detect local IP addresses, similar to the RuntimelessAPI. The License Manager no longer asks for the DNS.
LDK-1683 | Product names displayed in Admin Control Center were different from the names specified at creation time. Product names are now handles as follows: Names provided within a license container (for example, a V2C file) are valid just for that container. Names provided manually in a vendorid.xml file always override those container names, retaining backward compatibility (for examples, for translations) vendorid.xml files are never overwritten by the License Manager, so different names for licenses on different machines are no longer mixed up
LDK-2052 | When the login to a Feature would fail, the log file would not contain the username, hostname, FeatureID (and haspid, if specified in scope) .
LDK-2718 | Under certain circumstances, Sentinel HL (Driverless configuration) keys did not appear in Admin Control Center.
LDK-1965 | Under certain circumstances, a protected application under Windows 7 would cause a "Key not found" error.
LDK-2235 | False positive VM detection would occur on a physical machine that had a Hyper-V virtual machine.
LDK-2107 | A reference finger print would not contain the NIC_UID value when the NIC address has an OUI (Organizational Unique Identifier) value of “00:50:56:XX:YY:ZZ” OR “00:05:69:XX:YY:ZZ”. These OUIs (“00:50:56” OR “00:05:69”) are assigned to VMware, and are used by VMware when the NIC address for a VM guest m/c is manually generated.
LDK-1175 | Intermittent H0043 errors would occur when a USB camera was connected to the machine.
LDK-2564 | Under certain circumstances, the bundled RTE installer created using Sentinel EMS would fail.
LDK-1194 | Under certain circumstances, termination of a protected application would cause a Stop error.
LDK-2502 | When using RTE version 6.56: After logging off and then logging on to the machine, a HASP 4 key was not detected.
LDK-2240 | Under Windows XP, when installing haspdinst v.6.51 or 6.55 on an HP 8200 ELITE SFF machine, a stop error would occur.
LDK-2074 | The RTE installer would not add the registry entry “HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers" if it was not present. As a result, end users would receive Error 16 (Inconsistent Filesystem Structure) errors during RTE installation.
LDK-2034 | Licenses that were installed with a bundled RTE were not visible in Admin Control Center if a branded RTE had been first uninstalled and then reinstalled.
LDK-2428 | When a proxy server is used, Admin Control Center was not able to obtain language packs automatically.
LDK-3014 | When no HL key is connected to a machine, the driver package version was shown as as 0.0.

### Issues Resolved in Version 6.56

Reference | Description
--- | ---
170463 | When the user attempted to install Microsoft Office 2010 on a computer that contains the Run-time Environment, the installation would fail and display an "Error 1046" message
185897 | Run-time Environment v6.55 would not recognize a HASP HL key with Firmware v2.16. The key would not be displayed in Sentinel Admin Control Center
186197 | When an application is protected with "Enable data file encryption" selected in Sentinel LDK Envelope, and file extensions are added in the filter, it was not possible to save the encrypted files to a network location.

### Issues Resolved in Version 6.55

Reference | Description
--- | ---
MKS177499 | Under Windows 7 64-bit, protected application process would not exit from the Task Manager after closing.
MKS180520 | A Stop message (BSoD) would occur while running a DataHASP protected application when Norton Internet Security is installed.
MKS179112 | A delay would occur in obtaining the current remaining executions count when using the Licensing API hasp_get_sessioninfo() call soon after the hasp_login() call.
MKS177029 | The NX flag for hasplms.exe was not enabled.
MKS178460 | LM ID content of the LM Server whose information has not been refreshed for a long time would not be shown when more than 512 LM servers exist.
MKS168507 | If the HL key was changed while a machine was sleeping, then afterwards the License Manager would show that the original HL key is still present. The new HL key would not be recognized and would not work.
MKS175770 | hasplms.exe would crash and record an Access Violation error in the system log

## 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.

Copyright © 2014 SafeNet, Inc. All rights reserved.

DocID 118o Revision 1404-5