This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 53%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
Looking for some assistance if possible. I do understand that Native Client 11.0 is no longer supported or downloadable. We have an ODBC connection setup through a third-party vendors Azure Blob Storage that uses the Native Client 11.0 drivers.
Problem is, is that a fresh install of Windows 11 Pro doesn't have that driver, which renders that ODBC connection useless. What's weird is that SOME installs of Windows have it, I took two Dell Latitude 5350's, one had the driver, one did not when I imaged them manually. We are using Microsoft AutoPilot though and that does not have it.
Any suggestions besides forcing the third-party vendor to update their driver to ODBC Driver 18?
SNAC never shipped with the OS, but shipped with SQL Server or SSMS.
If you have the install media for SQL 2019 or earlier, you may be able to install SQL Server Native Client alone, but I am not sure.
If you have not, you can find old versions of SSMS here: https://learn.microsoft.com/en-us/ssms/release-notes-ssms#previous-ssms-releases. If this page is to believed, SSMS 18 or older is needed.
Thanks @Erland Sommarskog that worked when I installed SSMS 17.9.1, it installed the proper SQL Native Client 11.0 driver. Kind of sucks that I have to have SSMS on users' laptops haha but I can blame the vendor on using old drivers for that.
Any idea why this became a thing? For example, I can point to at least three laptops I imaged last month where it was installed and working fine while doing our normal imaging process.
Thanks again
Someone changed your imaging process to not include the driver? As I said, SQL Server Native Client has never shipped with the OS.
As for why the vendor is dragging their feet and stick with the old driver, I can only sigh...