Forum Widgets
Latest Discussions
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
Issues to install MECM 2509 (setup could not install sql rmo, configmgr installation)
Hello Team! During the install process of MECM 2509 in a Windows Server 2019 Datacenter Edition OS, it stops by getting the following error message: When i tried to manually install msoledbsql.msi to validate what the error message is, I get the following error: Also, I've already installed a version greater than the error is stating (14.51). It, in theory should continue allowing the install. My ODBC Driver 18 version installed is: So, just for test, when I do uninstall the ODBC Driver 18 knowing that the msoledbsql.msi file will be executed by the MECM installer—thereby ensuring the installer doesn't halt at that stage but proceeds with the setup—but if an ODBC driver is not already installed on the server, the MECM installation will not start; it indicates that this component must be installed in order to proceed with the MECM setup. I'm stuck, since I've already installed sqlncli.msi, msodbcsql.msi (18.5), VC_redist.x64 (14.51) , vcredist_64.exe, SharedManagementObjects.msi, VDP48.exe but failing when MEMC Install is trying to install from the Prerequisite downloaded MECM folder the msoledbsql.msi (ODBC Driver 18) again. Installer should ignore the execution of this file since I've already installed and continue with the install. I don't know what else to do. I've reviewed other forums to try to find a solution but nothing. Someone has faced with this issue in the past who can help me or anyone has any knowledge to enlighten me? Thanks in advance, guys.SCCM Application Model: Which WMI Properties and Classes Correspond to Software Center Tab Fields?
Service: Microsoft Configuration Manager (SCCM / MECM) Scenario: I am working with the Application Model and need to identify the underlying SCCM/WMI property names and associated class names for several fields displayed on the Software Center tab of an Application. Specifically, I am looking for the properties and classes corresponding to the following fields: Selected Language Localized Application Name Display this as a featured app and highlight it in the Company Portal and Software Center Environment: Microsoft Configuration Manager (Current Branch) Application Model What I am looking for: The SCCM/WMI property name associated with each field. The SCCM class name (SMS Provider class) where each property is stored. If applicable, the related SDK object path or SQL view that exposes these values. Troubleshooting Performed: I reviewed the Configuration Manager SDK documentation and application-related classes but could not determine the exact property-to-UI mapping for these Software Center settings. Supporting Material: A screenshot of the Software Center tab highlighting the fields is attached. Could someone help identify the corresponding WMI properties and classes for these settings?
Bitlocker key requested on the boot, but I don’t have any key
My laptop (Windows 10, version 22H2, build 19045), that I have been using more than 6 years already, suddenly started asking for the BitLocker recovery key at startup, which is blocking access to the system entirely. What I've already checked/tried: - Checked account.microsoft.com/devices/recoverykey while signed in with my Microsoft account, no key appears for this device. - Contacted Microsoft Support directly, they said they can no longer assist with Windows 10 issues and suggested posting here instead. Is there any way to recover access to this drive?
Configuration Manager manifest synchronization failing since 8 July 2026
Has anyone else experienced Configuration Manager Updates and Servicing synchronization failures since 8 July 2026? We have three independent Microsoft Configuration Manager hierarchies: Test environment Production T0 environment Production T1 environment All three started showing the same SMS_DMP_DOWNLOADER error during the last three days. The affected request is sent to: https://sccm.manage.microsoft.com/SCCMConnectedService.svc/Manifest Configuration Manager builds a hierarchy-specific request containing the Tenant, Version, Ring, and Branch parameters. However, the endpoint now returns only: OK The resulting file is: ConfigMgr.Update.Manifest.cab Size: 2 bytes Hex: 4F 4B Content: OK Because this is not a valid signed CAB file, dmpdownloader.log records: manifest.cab (http response) size is 2 Error in verifying the trust of file ConfigMgr.Update.Manifest.cab' WARNING: Failed to call IsFileTrusted WARNING: Failed to download and verify the manifest.cab. We cant get info in Updates and Servicing mode.
Moving from Windows Server 2022 to 2025
And by moving I mean stand up a completely fresh Windows Server 2025 as the old server was patched for one too many times. (painfully slow and stuffy) What I figured out so far, is to install Windows Server 2025, and the exact same SQL Server 1:1 to the build # install ODBC v18 update current MECM to the latest and its OS (update other Microsoft products with windows update) go to sites / maintenance tasks and do an export robocopy the "software" folder as is Now next would be to shut down old MECM server, rename new to the old's hostname, and start the "recover site" What my concern is as always "What if" can I at this point or once I set up the new MECM up and running go back by shutting down this new server, and powering on the old (leave and rejoin domain for trust) and go back to business as usual? That if anything goes sideways, or things won't get better. By that i mean speeding up things which is the main reason of the 'move' which now I do not wish to troubleshoot. Our environment, database size is 7.9 Gb, which is far from being big. The reason must be the update over upgrade over update over 15 years or more no and never brand new OS. I can take care of the "how to" I know exactly how to recover a site 'on paper'. I just want to know there's no such thing as point of no return. (when not making a single change in the Db/console) I also understand I should not make any changes in the Db (console) while testing, which is no problem at all. All we use MECM for is staging computers. Nothing else really. Like nothing else at all. PXE. The end. Thanks for the inputs. (I hope I picked the right tags)Existing required application deployments policy is not sent to devices
I have couple hundred applications in SCCM/MCM that are set to required and whenever there is a new device is built, all these required applications automatically get installed. I am on 2503 and 5 days ago i started seeing this issue. But if modify that deployment with current date and time then the application gets deployed right away if i run Application Deployment evaluation cycle. I also tested by deleting the existing deployment and created a new required deployment and run Application Deployment evaluation cycle then the application installs right away. The problem seems like the Primary server is not sending the policy to the client for existing deployments. The application compliance that we see for every deployment under Monitoring for all the devices moved to Error with Success. Not sure why this is happening. All these changes i noticed in the last one week. A week ago all these Already Compliant and Success status device count is under Success tab. Let me know if you have any suggestions.
Updates Not Installing by Install Deadline
Hello all! We have an organization with about 12,000 Windows 11 Workstations. I'm noticing that even though install deadline is set, and updates are allowed to be installed before install deadline hits, we are noticing in Software Center that updates say "will install after _____" (deadline date). How can I change this? I want updates to install during the maintenance window as well as a reboot. What am I missing? Connor
Quick Start non appare su iPhone gestito da ABM
La funzionalità "Inizia subito" (Quick Start) di Apple non appare o non è visibile durante la configurazione di un nuovo iPhone gestito da ABM, Apple ci comunica che la causa del blocco è dovuta a Intune, come possibile che non ci sia una risoluzione a questo problema? GrazieSCCM PXE Boot Deep Dive – Backend Flow & DP Migration
SCCM PXE Boot Deep Dive – Backend Flow & DP Migration I recently worked on a Distribution Point migration and noticed PXE requests were still routing to the old DP due to DHCP/IP helper configuration. I put together a deep dive explaining: PXE flow (DHCP and TFTP sequence) Role of Distribution Points What changes during DP migration Common failure points One key takeaway: PXE issues are almost always network and routing related, not SCCM itself. Curious how others are handling PXE in large environments. Are you standardizing on IP helpers or still using DHCP options? Full article: http://SCCM%20PXE%20Boot%20Deep%20Dive%20–%20Backend%20Flow%20&%20DP%20Migration
