Forum Discussion

-D31-'s avatar
-D31-
Copper Contributor
May 12, 2022

MECM 2203 Update and Client Registration issues

Ran the 2203 update on our platform last weekend, and found yesterday that a fair number of our clients have installed the new client but can’t re-register with the platform. After tracking the registration requests for the affected clients, it appears that the RDR files forwarded to the clients Primary server are missing the hex value corresponding to the AD SID of the client and the registration request is therefore being rejected.

 

Reinstalling the old client version fixes the issue. Various tests we’ve done have pointed to the 2203 client having a problem.

 

Has anyone come up against this before? Does anyone have any ideas on how to get the client to properly pass the required client identity info in its registration request?

 

Yes…we have a premier ticket open…

  • -D31-'s avatar
    -D31-
    Copper Contributor

    https://docs.microsoft.com/en-us/mem/configmgr/hotfix/2203/14480034

    So, MS released a hotfix to deal with this issue, which replaces a dll in the server install which essentially tells the Primary servers to ignore the fact that the registration requests are incomplete. I expect to see another hotfix shortly which fixes the 2203 client behaviour that broke things in the first place.

     

    It’s resulted in a lot of duplicated machine records, and subsequently, owing to the old records going inactive and being removed, the loss of a fair bit of historical data. We’ll survive, but it’s not ideal.

     

    just thought I’d post the resolution…

Resources