KB #240150: Upgrading Operating System on a machine with Encryptionizer installed (v2201.1.0 and later)

Type:

Information

Summary:

You are upgrading the operating system of a machine in place, and have Encryptionizer 2201.1.30212 or later installed (NLEMSYS.sys version 2201.611.55 or later)

NOTE: Encryptionizer versions 2401.1.5.5014 or later are no longer impacted by OS in-place upgrades.  An OS upgrade will not deactivate the Encryptionizer software. However, as with any major updates to a machine, it is important that you can confirm encryption keys before proceeding.

Additional Information:

These instructions are specific to Encryptionizer and later (product version 2201.1.1) using NLEMSYS.sys driver version 2201.611.55, as this version uses a different license activation method from previous versions. If you have an earlier version of our software on your machine, please refer to KB 240138. To determine your driver version, refer to KB 240145.

An operating system in-place upgrade in some cases has interferred with our software and may require importing an entry to the Windows registry.

Below are suggested steps when performing the in-place OS upgrade.  We generally recommend that you also update your Encryptionizer software to the latest version to ensure Operating System support.

1. Confirm that you know your encryption keys before proceeding. You can confirm them by taking a database offline, using the Encrypt/Decrypt Wizard, choose the Validate option and enter your key information to compare. Do not proceed until you confirm this information in the event you need to re-enter the encryption key later.
2. Perform your OS in-place update.
3. After the last reboot of the OS upgrade, you will need to import an important registry entry:
   • Download the following file which is a Zip file containing the registry import file:
     https://netlibsecurity.com/files/patches/nlem1402_tag.zip
   • Expand the file and rename the extension from .re_ to .reg
   •  Open Regedit and import the file (nlem1402_tag.reg)
   • Reboot
4. Perform an update of Encryptionizer software, if necessary. You can install it over the existing version.  Reboot.
5. After reboot, ensure that the NetLib Encryptionizer Key Management Service is running (nlcbtask)
   • open a command window with the “Run as Administrator” option, and run the following:

     sc query nlcbtask

     This should return 4 : Running

6. If NLCBTASK is not running, check that your software is still properly activated by launching the Main Menu program (nlmain.exe).  You can also test your license by following the instructions in the KB 240132. You may need to deactivate the license and reactivate it using the License Management option from the Main Menu.
7. Run the Administration Wizard from the NetLib Encryptionizer main menu (nlmain.exe)
8. Does the SQL instance say it is secured? If so, then no additional actions are necessary. Make sure that your encrypted databases are accessible.
9. If the Admin Wizard reports that the SQL instance is not secured, secure it once more with the same settings as previously used. The encryption key must match exactly.
10. Restart the SQL instance, and you should once more have access to your encrypted databases.