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 the Sentinel HASP system.)
The latest service packs and security updates must be installed.
Support has been added for Windows XP Embedded and Window 7 Embedded.
Sentinel Admin Control Center user interface and help files incorporate changes in terminology as follows:
When using the Installer GUI to upgrade the Run-time Environment, ensure that:
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:
| 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:
|
| 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 received 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 uninstalled. |
| 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. |
| Reference | Description |
|---|---|
| Ref#8475 (LDK-2196) | When you attempt to integrate the Sentinel LDK Run-time Environment Installer MSM module in your Windows Vista installation package, a warning may be displayed. This is a known issue for the Installer, and the message can be ignored. For more information about this issue, go to this URL. |
| 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 Sentinel 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 © 2013 SafeNet,
Inc. All rights reserved.