Prajwal Desai
SCCM | ConfigMgr | Azure | Intune | Tech

SCCM 1810 SQL Server Native Client Update Warning Prerequisite

13 3,442

While installing SCCM 1810 you might encounter warnings during prerequisite check. I had described about the warnings in my previous post. However the solution wasn’t very clear as i couldn’t cover it in detail. In this post I will show you how to fix Microsoft SQL Server Native Client related warning. Although you can skip that warning but it is always recommended to fix them.

While installing SCCM 1810 update, I got the warning at prerequisite check step. Clicking the warning showed the below description.

[Completed with warning]:Verifies that the version of Microsoft SQL Server Native Client installed on the site server meets the minimum requirements to enable TLS 1.2 support.

The configmgrprereq.log file shows the below warning in detail.

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

SQL Server Native Client TLS 1.2 support

First of all let’s start by checking the actual SQL server native client. In my case, it is SQL server 2012 native client and the installed version is 11.2.5643.3. The warning appears because the version of client is lower and you need to upgrade this client version.

SQL Server Native Client TLS 1.2 supportBefore you proceed further you need to know the SQL native client version that you have to download. Go to this link and you will find SQL Server release and the first build that supports TLS 1.2. If you know your installed SQL server version, determine whether your current version of SQL Server already has support for TLS 1.2.

Clicking the above link (the one that we see in log file) takes you here. Click Download button.

SQL Server Native Client TLS 1.2 support

Installing SQL Server Native Client

Right click the sqlncli and run it as administrator. You will now see a warning box. A lower version of product has been detected on your system. Would you like to upgrade your existing installation ?. Click Yes.

SQL Server Native Client TLS 1.2 support

On the Microsoft SQL Server 2012 Native Client setup box, click Next.

SQL Server Native Client TLS 1.2 support

Click Next.

SQL Server Native Client TLS 1.2 support

To begin the installation click Install.

SQL Server Native Client TLS 1.2 support

Finally click Finish to complete the setup.

SQL Server Native Client TLS 1.2 support

A server reboot is must, click Yes to reboot.

SQL Server Native Client TLS 1.2 support

Check the version of Microsoft SQL Server Native Client and it is now 11.4.7001.0.

SQL Server Native Client TLS 1.2 support

Back to SCCM console. Go to Updates and Servicing node. Right click Configuration Manager 1810 update and click Run Prerequisite check. You will notice that SQL Server Native client version step shows completed.

SQL Server Native Client TLS 1.2 support

  • As a quick fix, you can install the updated SQL Server 2012 Native Client that’s included in the ConfigMgr 1810 download. On the site server, the folder location is “EasySetupPayload454b3508-4387-4106-9441-283495dec3ecredist”; the file name is “sqlncli.msi”. Even though the updated Native Client is included in the download, an automated upgrade is not allowed due to licensing restrictions.

  • I have SQL 2012 Native Client v11.4.7462.6 and am getting this warning during pre-req check. What should I do? Is it safe to ignore?

  • Hello, great website, thanks.
    We are stopped in the update as or prerequisite check fails in “SQL Server Configuration for site upgrade”, we can´t guess what the problem is as our SQL should be OK.

  • During installation of the native client I get a “files in use” popup. SMS_executive, SQL Server and SQL Server Agent are blocking the installation. Should I stop the services or ignore?

    • Yes i did see that in my lab setup as well. Yes, i stopped the services, installed the native client and restarted the server.

  • >