Latest ODBC Driver 18 for SQL (18.7.1.1) breaks SCCM Site Server > SQL connectivity
We have an automated update configured for ODBC Driver 18 for SQL which kicked in last night and took our install on the site server from 18.6.2.1 to 18.7.1.1 which seems to have completely broken Site Server -> SQL server connectivity. Rolling back to 18.6.2.1 and restarting the Site Server is the fix (for now) but I'm sure our Information Security team will be asking to get patched again soon. For info, the hman.log shows some threads stopping and then just goes dead when the update is applied and the Application event log is filled with "Complus" errors all related to the msodbcsql18.dll... The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below. Component Prog ID: 0[ODBC][C:\Windows\system32\msodbcsql18.dll] Method Name: IDispenserDriver::CreateResource Process Name: sitecomp.exe Exception: c0000005 Address: 0X00007FFA85FD2C10 How do we raise this with Microsoft? Has anyone else seen the same? Site Server is on Server 2019 (patched monthly). Our SCCM site is version 2603. Site Server and SQL DB on two different servers. Running E-HTTP mode. I note that something similar happened not too long ago... https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/setup-migrate-backup-recovery/update-odbc-18611-causes-issues-configmgr Thanks Stuart
Become a Microsoft Endpoint Configuration Center Ninja
Do you want to become a ninja for Microsoft Endpoint Configuration Manager? We can help you get there! We collected content to get you from endpoint newbie to becoming a MEME "Microsoft Endpoint Manager Expert". The content is structured into three different knowledge levels, with multiple modules: Fundamentals, Intermediate, and Expert. We will keep updating this training on a regular basis and highlight new resources. Content Coming Soon!
MCM V2609 - Release Date?
Everything seems to have gone quiet about Version 2609. It was due for release this month and the month is almost over. Just wondering if any info on when it might be making an appearance? Just finishing up our migration to W11, so finally have time to upgrade from the old version we are running, so would like to get it on ASAP.
SCCM - 23/24H2 to 25H2 Upgrade
Hello SCCM Community! Having an issue with upgrading devices from 23 and 24H2 to 25H2, I am downloading the newest version in SCCM under Windows Servicing and Feature Upgrades and deploying it to the targeted collection, but nothing shows in Software Center. Upon checking the UpdatesDeployment log, it shows Actionable Updates = 0 in one of the lines, but I'm wondering why WUA is determining updates do not apply to the machine. I believed this could be a GPO restriction but I've confirmed that there are no conflicting GPOs or Registry Edits. Any suggestions? Thanks!All Windows Server OS(Mostly 2019) DP's not upgrading to 2207
FYI... This issue is happening again since last week and this time it is not just server DP's but Windows 10 DP's also. It is not a result of MECM server upgrade maybe Feb patches got installed on the primary server but very few DP's are fine. Last friday i upgraded CM from 2203 to 2207 version. I saw no error after the upgrade. I have a bunch of Win 10 computers as DP's and those DP's got upgraded to new version(5.00.9088.1000) but all the Windows Server OS DP's failed to upgrade. FYI... Site server is an admin on all the DP's and nothing has changed. Here is a screenshot of distmgr.log error. vcredist_x64.exe is already installed on all the server DP's last year probably with 223 upgrade. I do not see any errors in the firewall or antivirus software. Not sure what could be the issue.UPGRADE_EXPERIENCE_INDICATORS in Resource Explorer
We are seeing that the Config Manager hardware inventory contains the UPGRADE_EXPERIENCE_INDICATORS section which shows data that appears to be about upgrade compatibility to specific builds (with CO21H2 being Windows 11 21H2, for example). Could someone please share what the attributes named Upg Ex Prop and Upg Ex U and the color values they have actually mean? We've seen Red, Orange, Yellow, and Green, but it doesn't appear to be documented anywhere what the attributes or values represent. We would like to use these values for collection membership and Windows 11 Upgrade task sequence deployment, but want to fully understand what they represent. Note: We have compared these to what is shown in Endpoint Analytics for Windows 11 readiness status. While green has matched Capable and red has matched Not Capable, we're seeing a mix of Capable and Unknown for both yellow and orange. Thank you.
