MECM Site Migration - Client not connecting to new MP

Question

Hi. I've built a new MECM server (currently 2207, running on Windows Server 2022), and have so far successfully migrated around 65 endpoints over from the old site to the new site. FYI, it's a single server, with a single site, and the management and distro points are installed on the same box.

Here's the problem: I have one endpoint which successfully installs the new client, but will not connect to the new management point. Well, sort of. The client sees the correct MP and it populates in the config manager properties in control panel (screenshot with red scribble), but it does not enable communications with the server, so the MECM console does not show the device as active.

FYI the site tab shows the correct site code for the new MECM server. I've tried completely uninstalling the client from this box, and reinstalling from the console. I've tried installing directly from the MECM server. Boundaries are wide open with the appropriate site assignment settings on the boundary groups, so there's no conflict there. As I said, I've successfully migrated 65 boxes. This one is the outlier. Any thoughts on causes or solutions? This endpoint is a server itself, so I'd rather not reimage if possible.
Thanks, y'all.

Answer 1

The error is very similar to the thread below, the link for your reference:
client-certificate-none-in-config-manager-properties

Problem/Symptom:
Client not connecting to new MP or Client Certificate = None In Config Manager Properties

Reason:
Missing client certificate

Solution/Workaround:
In the SCCM Console -> Administration -> Site Configuration -> Sites. Right click on your site(s) and edit the properties. In the Client Computer Communication tab if you have "Use PKI client certificate (client authentication capability) when available" selected then you can modify the client certificate selection criteria. However, please note that the article says that the modification did not take effect immediately, but waited for a period of time.

It's appreciated that you could click "Accept Answer" to the reply.

Answer 2

Hi @Max S ,

1, What status does the client display on the MECM console? Please check the ccmsetup.log to see if there are any errors during the installation.
Navigate to Client>C:\Windows\ccmsetup\logs\ccmsetup.log

> CCM Notification Agent ---Disabled

2, Please check the CcmNotificationAgent.log and LocationServices.log to see if there are any errors.
Navigate to Client>C:\Windows\CCM\logs...

Note: Notification agent is a client component hosted in CCMEXEC.exe. As a part of client initialization, it will establish a persistent connection with notification server. For those clients that communicate via a secondary site, they will establish connection with the notification server on the proxy management point. It will try TCP(port 10123) mode first, then fallback to HTTP(port 80) mode if it fails (due to firewalls or Internet proxies that do not allow TCP traffic). If the connection is dropped (e.g. because of a network issue), notification agent will attempt to reconnect.

This link for your reference:
https://techcommunity.microsoft.com/t5/configuration-manager-archive/fast-channel-for-system-management-client-notification-in-system/ba-p/273157
Note: Microsoft provides third-party contact information to help you understand the problem. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Looking forward to your feedback.

Best regards,
Cherry