i Found a soultion.

We had the same Problem after install the KB12896009 hotfix

After the Realease with SCCM 2203 , we installed the update immediately.

After that, the WMI error messages in the log files were gone.

Unfortunately the problem was not solved. Through intensive searching and testing, we have discovered that the devices in the SCCM Console are no longer automatically approved. After approval everything workes.

Settings to check for auto Aprove:

Administration—-Sites—Hierachy Settings—-Client Aprovall

I don’t know why this button was not on automatic anymore

Best regeards from Zurich

Same over here
Since 2111, we have the same error
Opened a case by MS and still waiting
We have the issue without the kb KB12896009, we planned to install it in hope it fixes it but reading above doesnt looks like it will help

Nobody found a fix yet ?

PS: we have no onprem AD and our client connect trought CMG only

Hi Prajwal we are getting the above errror in locationservices.log and machines are not able to register itself to MP. As a result of that they are showing greyed out in sccm console. Its happening with the newly built devices and the old devices have the same error but as they are already registered so atleast they are coming with green tick in console

We have also the same Problem since Update KB12896009 🙁

Best regards from Zurich.

Same problems. Permissions on AD were already correct. Can’t deploy anything except via task sequences, so it’s a bit frustrating! On KB12896009. Anyone made any further progress with this? See lots of threads stating the problem, but they all finish without a fix.

Thanks.

we have a similar problem. Since the update to 2111 incl. hotfix KB12896009 we do not get any new apps deployed. New apps are simply not displayed in the software center. Apps deployed before the update are still available.
Task sequences still work.
I am still waiting for an answer from MS support.

I have not yet installed the latest hotfix KB12959506.
Does anyone else have similar issues and possibly solutions?
I checked the authorization and it was OK.

OK, so we found the cause while investigating some SQL errors we found in the SCCM Server’s event log that we thought may be related:
A little additional background: At the same time as upgrading to SCCM 2111 we had upgraded our SCCM infrastructure to use PKI. We had deployed the certificates from our CA to IIS servers and Distribution points as directed.
The solution for us was to correct a misconfiguration in Active Directory.
In AD Users and Computers, navigate to \System\System Management. Right click the System Management container and select Properties. Move to the Security tab and click Advanced. Search for your site server’s Computer object – in the “Applies to” column, if it shows “this object”, change it to “This object and all descendent objects”.
I cannot warrant whether this will resolve the issue for you, but this was the only change that we recall making between when it was broken and when clients started connecting to the servers again.
I know that SCCM stores information in AD and uses AD to allow clients to discover information about how to communicate with server resources.
Having checked the attributes in my site server sub-container, the mSSMSCapabilities attribute now contains (among other things) details of the CA, the certificate, the fact that we’ve configured SCCM to require HTTPS for all communication etc. I don’t know if these values were present before the permission change, but it’s too much of a coincidence that the site server was prevented from changing values in the descendent object and clients failed to realise they should be using PKI, and when it was allowed to do so all clients just sprang to life (and so did OSD)
I hope this information makes sense to anyone reading. And I hope it helps resolve your issue Thomas

Hi Thomas – I am unable to help but would like to note that I am also seeing an identical failure, and have found plenty of articles on the likes of reddit that say the same thing.
Manually installing the agent (and re-installing) doesn’t seem to resolve the error and I’ve seen suggestions that it’s simply been broken in update KB12896009…
This reddit post links to an article that doesn’t confirm or rebuke this suggestion but since nothing I have found has explained why this happens I’m starting to agree.
I have been investigating the problem for a week now without success but if I find a solution to what has caused our OSD to fall spectacularly on its face I will post.

I have a problem with client version 5.00.9068.1012. Suddenly after this release some of my devices (about 50%) can´t get software updates and do not show in Software Center. I have never had this error before and i know it started with this version.

There is an error in LocationServices.log

Reading Location override flags from WMI LocationServices 25-02-2022 18:22:09 10364 (0x287C)

Error reading location override information from WMI. Return code: 0x80041010
LocationServices 25-02-2022 18:22:09 10364 (0x287C)

WSUSLocationRequest :
LocationServices 25-02-2022 18:22:09 10364 (0x287C)
Created and Sent Location Request ‘{E0827F0C-5438-4137-BB68-865C0C59D73F}’ for package {185188F9-65B0-4A9C-9B8B-F9EEED44C03E} LocationServices 25-02-2022 18:22:09 10364 (0x287C)

Hope someone can help.

Here is my suggestion – Upgrade to 2111 for both primary and secondary. Then install hotfixes on primary sites and do recovery for secondary sites.