The below list of products represent configurations of the serial, parallel, and PCI card form factor of Hardlock and HASP4 family.This End of Sale notice affects the following products:

• 948-006519-001
• 948-006667-001
• 948-007428-001
• 948-007430-001
• 948-007535-001
• 948-002844-504
• 948-007439-001
• 948-009485-001

This End of Sales announcement does not constitute a discontinuation of the Hardlock or HASP4 technology; it is simply removal of certain configurations of these products. The technology will still be supported, but we encourage you to consider switching over to our Sentinel HL replacement keys, which are fully compatible with your existing implementations.

Sentinel HL is the preferred form factor for customers wanting to leverage the most advanced licensing capabilities. To learn more about Sentinel HL including features, sizing, and technical specifications, please visit the Sentinel Customer Community.

The Sentinel Protection Installer (SPI) version 7.6.8 for SHK, Sentinel SuperPro and Sentinel UltraPro on Windows is available for download.

 Feature Highlights:

• Sentinel System Driver and Sentinel Protection Installer support installation when Application Compatibility Engine is turned off.
• Support of Java 7 and 8 has been provided in Sentinel Protection Server.

 The package and release notes are available at  http://sentinelcustomer.safenet-inc.com/sentineldownloads/

The sample provided with kit is configured to work with DEMOMA keys. It is linked with "libhasp_windows_demo.lib" & "libhasp_windows_x64_demo.lib".

To make it working with other "Batch codes" keys below are the steps:

• change the VendorCode.
• In addition, there is need to change the hasp static library dependencies, in the linker settings of sample project. 
• Inform the VC++ linker what HASP library files to use for the batch code / Vendor ID.
• Change the settings for both Debug and Release versions, so in the project Properties dialog, under the Configuration field, select "All Configurations".
• Select the "Linker" category of properties and, pick the "Input" option under that.
•  In the "Additional Dependencies" property, add libhasp vendorised library (libhasp_windows_<VENDORID>.lib & libhasp_windows_x64__<VENDORID>.lib) in replacement for the DEMO ones (libhasp_windows_demo.lib & libhasp_windows_x64_demo.lib) 
• Finally, inform the linker about the location of library files kept in different subdirectories  C:\Users\<username>\Documents\SafeNet\Sentinel LDK7.3\Samples\Runtime\C\win32\msc\lib\libhasp_windows__<VENDORID>.lib and C:\Users\<username>\Documents\SafeNet\Sentinel LDK 7.3\Samples\Runtime\C\x64\msc\lib\libhasp_windows_x64__<VENDORID>.lib 
• Select the "Linker" category of properties and, pick the "General" options under that.
•  In the "Additional Library Directories" property, add the appropriate library directory.

The steps mentioned below guides to upgrade EMSDB via the SQL Scripts in case the EMS version is newer than the database version (like EMS v7.3 & EMSDB v7.1)

Note: It’s not mandatory to upgrade the database via the SQL Scripts. The common alternative is upgrade the EMSDB database during the EMS install setup

Steps to be followed:

1. Stop the EMS service

2. Log-in to the EMSDATABASE SQL instance via Management Studio

a. Backup the current state of the EMSDB database

b. Restore the older version of EMSDB database

c. Apply the EMS SQL scripts as following:

i. The scripts are located at C:\Program Files (x86)\SafeNet Sentinel\Sentinel EMS\Database\SQLScripts

ii. Go to Management Studio -> File -> Open each script in the following order

1. In case the SQL Scripts start with USE EMSDev modify to USE EMSDB

2. The scripts e.g. in case of EMS v7.3 and EMSDB v7.1:

a. UpgradeFrom71to72.sql

b. UpdateValuesFrom71to72.sql

c. UpgradeFrom72to73.sql

d. UpdateValuesFrom72to73.sql

3. Quit Management Studio

4. Start the EMS service and log-in

Ensure you are using the latest runtime package available at:

http://sentinelcustomer.safenet-inc.com/DownloadNotice.aspx?dID=8589947119

These drivers are digitally signed but the machine or specific machine configurations might fail to verify the signature. In this case:

1) Open command prompt in elevated mode (Run As Administrator) and execute the following commands:

bcdedit -set LOADOPTIONS DISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON

2) Reboot the machine

3) Try installing the Runtime drivers again after the machine has rebooted

Note: to re- enable driver signature verification, execute the following cmd-line commands 

bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING OFF

and reboot the machine.