11/28/2018

2 minutes to read

In this article

If you are planning to upgrade your ConfigMgr infrastructure to the latest 1810 release, plan for updating the SQL Server Native Client to support TLS 1.2

If the SQL Server native client isn't already updated, the prerequisite check will fail with below warning.

The details are available in the ConfigMgrPrereq.log

<11-27-2018 20:27:21> PRIMARY1<FQDN>; SQL Server Native Client version; Warning; Configuration Manager sites require a supported SQL Server Native Client version. To enable TLS 1.2 support, you must install a supported version of SQL Server Native Client on the specified site database server. For more information, see https://go.microsoft.com/fwlink/?linkid=2026746

You do have the option to ignore the prerequisite check, however if you want to support TLS 1.2 now or in even in future, you should upgrade the SQL Native Client.

Refer the link from log snippet to identify the applicable version. You can check Programs and Feature on the Server to identify the currently installed version.

In my case I have SQL Server 2012 Native Client.

From here I can choose to install the applicable version.

This takes me to https://www.microsoft.com/en-us/download/details.aspx?id=50402

The version number here is in fact lower than what we see in Programs and feature screenshot above.

Launch ODBC 64 bit > Drivers tab to validate the right version. 110.6540 is lower.

Install the SQL Native Client Update installer, this will also confirm you are running the lower version and may request a reboot post install.

Launch ODBC once again to validate the updated version to support TLS 1.2

Happy Upgrading!

Thanks,

Arnab Mitra