SCCM 1810 SQL Server Native Client Update Warning Prerequisite

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

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

Related Posts
Oldest Most Voted
Inline Feedbacks
View all comments

Hi Prajwal, I already ha e 10.4.7001 sql native client installed, but in the prerequisite check I see the warning that the sql native client need to have TLS 1.2… unfortunately I proceeded with tha 1910 upgrade even if the prerequisite check warning me in February 2020 and every thing seems to be ok. Now that I need to import a new operative system image In the content status I see the import in progress But never finish. It stack on “ Detail will be available after the server finishes processing the messages.” I’m afraid the reason is my upgrade.… Read more »


Hi Prajwal,

I need to understand what SQL Native client update I should apply when the version of the current Native Client reads 11.3.6020? Your help would be most appreciated.



Thank you for your response. I was able to run the install from the downloaded content on the SCCM server and I now have the updated SQL Native client and all prerequisites are good to go and ready for the upgrade.



Do you have to upgrade the SQL Server Native Client for the TLS 1.2 warning on your Primary Server or your DB Server?



Where can I download the native client update?o The database for SCCM exists on a different server that is already up to date

Mark Glen


We have 1710 currently installed and am failing 1810 pre-req check with this warning. This is the only warning generated by the check.

The precheck log file suggests the Native Client inst supported for TLS 1.2 “SQL Server Native Client version; Warning; Configuration Manager sites require a supported SQL Server Native Client version.”

We have single server solution and 2012 SQL Native Client is version 11.4.7462.6 which is a supported version i believe.

But we still fail this check, is there anything else we need to do to pass this check?



I get the get the error Microsoft SQL Server 2012 Native Client 11.4.7462.6, the documentation does NOT say what version of SQL native client to install and the example in your guide shows you upgrading to a lower version than 11.4.7462.6 so its unclear what is needed, can you please clarify …… from the comments you can see that a lot of people are having problems here as this part of your excellent guide, simply is not clear

Francisco Pereira

Hi guys,

‘m having a problem with my verification in upgrade version 1806 for version 1810

Checks if the specified SQL Server meets the minimum requirements for site upgrade.

My SQL Version: Microsoft SQL Server 2016 (SP1) (KB3182545) – 13.0.4001.0 (X64) Oct 28 2016 18:17:30 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 (Build 9600: ) (Hypervisor)


Nice articel – works fine for me


I get error [Failed]:Checks if the specified SQL Server meets the minimum requirements for site upgrade.


and I upgrade from SQL Server 2012 sp4 to SQL Server 2017 cu 14


I have got the same error, but I can not find a solution. Do you have fixed it yet?


Hi Prawjal,

I have the Microsoft SQL Server 2012 (SP3) (KB3072779) – 11.0.6020.0 (X64) version but I don’t know which native client version I have to install. Can you help me?


When I updated the native client on my 1806 SCCM server the pre-reqs passed for 1810. Then the next week my server broke . I am not sure if it is because the consultant never setup up a maintenance job to clean up the database and by the time I got to that chapter in the new unleashed book it was more than 50% fragmented.

Michiel Overweel

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?


I found the answer in your other post ( I have a separate DB and the warning was for the Native Client on my site server. After upgrading that and running the pre-req check again, all passed. Thanks!


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.


The best, and the simplest answers to facing problems. Overall this Blog has it all.


I upgraded the SQL to the proper version as shown above but am still get the prereq error.


Thanks Brother to have suggest it


thanks a lot!


Found your previous post about this, just the DB server



Hi Mr Prajwal,

Should I upgrade both native client on sccm and sql servers?



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?


I ignored and rebooted after installation completed. Seems to be fine.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More