Courtesy of Brook Hudson, who provided clarification for encrypting SCOM data –
Question – Can we update the OLE DB Driver from 18.6.5 to 18.6.7 and the ODBC driver from 17.10.3 to 17.10.5.1 without breaking anything?
This configuration applies to SCOM2016 forward –
MS OLE DB Driver 18.6.7: https://go.microsoft.com/fwlink/?linkid=2242656
ODBC Driver 17.10.5.1: https://go.microsoft.com/fwlink/?linkid=2249004
I did NOT have success with this for SCOM2019 and SCOM2022 –
If the SQL endpoint is secured with encryption, then the following drivers can be used.
MS OLE DB Driver 19.3.2: https://aka.ms/downloadmsoledbsql
ODBC Driver 18.3.2.1: https://aka.ms/downloadmsodbcsql
If you want to use these newer drivers then SQL encryption is required, more information about enabling SQL Encryption: Configure SQL Server Database Engine for encryption – SQL Server | Microsoft Learn – https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-sql-server-encryption?view=sql-server-ver15
The SQL team noted that the newer versions are defaulting Encrypt to be Yes/Mandatory. That is why the new drivers were having an issue. Setting up a certificate in the SQL endpoint would have allowed the connection to work:
Enable encrypted connections – SQL Server | Microsoft Docs
Certificate Management (SQL Server Configuration Manager) – SQL Server | Microsoft Docs
OLE DB Driver 19.0 for SQL Server Released – Microsoft Tech Community
ODBC Driver 18.0 for SQL Server Released – Microsoft Tech Community
IMPORTANT:
Update: Hotfixes released for ODBC and OLE DB drivers for SQL Server – Microsoft Community Hub