Secure Configuration Manager Windows Console Login Fails When TLS 1.2 is enabled

  • 7023700
  • 05-Feb-2019
  • 14-Nov-2019

Environment

Secure Configuration Manager 7.1.1
Secure Configuration Manager 7.2

Situation

If TLS 1.2 is enabled, you cannot log in to Secure Configuration Manager windows Console

Resolution

Perform the following steps on the machine running the Windows Console:

Microsoft SQL 2008 R2:

1. Install SQL Native Client (sqlncli.msi) from the link :

   https://www.microsoft.com/en-us/download/details.aspx?id=57606

2. Create the following registry String key:

   [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PENTASAFE\PSENTERPRISE]

   "DBAProvider"="SQL Server Native Client 10.0"

3. Enable TLS 1.2.

4. Restart the machine.

5. Log in to the Windows Console.


Microsoft SQL Server 2012 and later:

 1. Install Microsoft OLE DB Driver 18 for SQL Server from the link

   https://www.microsoft.com/en-us/download/details.aspx?id=56730

2. Create the following registry String key:

   [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PENTASAFE\PSENTERPRISE]

   "DBAProvider"="MSOLEDBSQL"

3. Enable TLS 1.2.

4. Restart the machine.

5. Log in to the Windows Console.


Cause

Secure Configuration Manager windows Console communicates using only TLS 1.0