Apr 23, 2019 This post is a SCCM 1902 install guide using baseline media. The SCCM 1902 baseline media is now available for download in Microsoft evaluation center. Step 8 – Supported SQL Server for SCCM 1902. The following versions of SQL server are supported by SCCM 1902. Hope this table helps you decide install the right SQL server version for SCCM. This post contains the SCCM SQL query for Microsoft office 32 bit and 64 bit. Many organizations today use Microsoft office to simply the work. Listing out office versions installed on all machines is a big task. Using SQL queries it’s very easy to find out the Office versions. However note that these are the SQL queries and not the WQL queries.
If you are planning to upgrade your ConfigMgr infrastructure to the latest, plan for updating the SQL Server Native Client to support TLS 1.2If 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 PRIMARY1; 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 Update SQL Native ClientYou 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 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 toThe 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.2Happy Upgrading!Thanks,Arnab Mitra.
Hi,I am receiving this error during SCCM installation.I am using SQL Express 2017, it is officially supported:instance name I have is SQLEXPRESSand when I installed WSUS and choose SQL settings, it is accepted successfully, but not sure why SCCM is not accepting it.I have also updated the SQL Express with the latest update using the following:the server, and same issue appears.any suggestion to solve this issue? Hello,The SQL Express edition can only be used in secondary site.To start a fresh SCCM installation, we could only use standard or enterprise edition of SQL.Based on your screenshot, you are installing SCCM CB, not SCCM 2012 R2, is it right? We could use SQL 2017 standard/enterprise for SCCM CB 1802 baseline; For baseline prior to 1802, SQL 2017 is not supported.Hope my answer could help you and look forward to you feedback.Best Regards,RayPlease remembers to mark the replies as answers if they help.If you have feedback for TechNet Subscriber Support, contact.