Configuration Manager: Update to CB2203 and install a hotfix before July 27, 2022

Windows[German]Do yo use the Microsoft Endpoint Manager Admin Center (formerly SCCM and Intune) to manage clients? Then you should make sure that the MEMCM infrastructure (MEMCM=Microsoft Endpoint Manager Configuration Manager) is updated to CB2203 via hotfix before July 27, 2022. Otherwise, there will be errors because certificate informations have not been renewed.


I still have to get used to the new names, as for me it is still System Center  Configuration Manager (SCCM)that is used to manage clients. But at Ignite 2019, Microsoft had introduced a new product called Microsoft Endpoint Manager (MEM). Basically, SCCM along with its ConfigMgr were just renamed and merged with Intune. The goal was to give users a flexible path to cloud management with Endpoint Manager (and integrated Intune features).

Update MEMCM

The days I came across the above tweet where Juerg Koller points out that the Microsoft Endpoint Manager Configuration Manager infrastructure (MEMCM) has to be updated to version CB2203 and needs also a hotfix before July 27, 2022. The background is described by Microsoft in the support article Mismatch certificate subject name error when running client action for Configuration Manager device dated July 8, 2022.

There is a scenario where client actions that an administrator tries to run in the Microsoft Endpoint Manager Administration Center fail. Configuration Manager components are unable to connect to the backend cloud service and the following error is displayed:

Failed to verify and load the service signing certificate. System.ArgumentException: Mismatching certificate subject name.

This issue is said to occur with Configuration Manager version 2203 on July 27, 2022, when a Configuration Manager version 2203 hotfix rollup has not yet been installed. The background: On July 27, 2022, there will be a change to the public certificates. This will remove OU=Microsoft Corporation from the subject name of the public certificate. But the configuration manager database still contains the old subject name, which leads to a load check error. Installing the hotfix should fix this problem – which should be done before July 27, 2022. Those who use the CM before version 2203 must update to this version and then install the hotfix to avoid the problem.


Cookies helps to fund this blog: Cookie settings

This entry was posted in Cloud, Windows and tagged , , , . Bookmark the permalink.

2 Responses to Configuration Manager: Update to CB2203 and install a hotfix before July 27, 2022

  1. B. says:


    Is this scenario applicable in case 3rd party certificate is in use like DigiCert or Sectigo
    There's very limited information in the article.

    Thank You

Leave a Reply

Your email address will not be published. Required fields are marked *