Client unable to register with the CM site

Ahmed MS 21 Reputation points
2021-07-23T10:29:40.903+00:00

Hello all,

I've seen some issues recently related to multiple devices that are connected to the network (LAN or VPN) but the client status is showing "Inactive", I've uninstalled the client and installed it from scratch manually. The client now is installed but it fails to be registered with the MP, I have the following error message in ClientIDStartupManager.log:

[RegTask] - Client is not registered. Sending registration request for GUID:4E13F2E2-4FD2-40AA-A5F3-817F8FA6DB4A
RegTask: Failed to send registration request message. Error: 0x87d00231

LocationServices.log is showing that the MP is correctly assigned, ClientLocation seems OK too.

Command used to install the CM Client: ccmsetup.exe /mp:siteserver.domain.local SMSSITECODE=CM1 FSP=siteserver.domain.local /AllowMetered

ccmsetup.log showing "CcmSetup is exiting with return code 0" in the end.

CM Site version: 5.0.9040.1019
Client OS version: Windows 10 20H2 Enterprise

117360-client-not-resitred.png

Could you please help me to fix this issue?

Best regards,

Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Youssef Saad 3,406 Reputation points
    2021-09-11T10:47:07.94+00:00

    Hi @Ahmed MS ,

    I've seen this error before, it was related to the metered connection that was enabled in the network card settings. Check if this option is enabled, disable it and check again the CcmMessaging.log and ClientIDManagerStartup.log files.

    If the issue persists, uninstall the client and install it again without "/AllowMetered" option.

    Regards,


    Youssef Saad | Blog: https://youssef-saad.blogspot.com
    Please remember to ** “Accept answer” ** or upvote for useful answers, thank you!

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Amandayou-MSFT 11,056 Reputation points
    2021-07-26T06:22:46.17+00:00

    Hi @Ahmed MS ,

    0x87d00231 = "transient error"

    This is typical of a network related issue between the two endpoints (the client and MP in this case).

    Have we validated the network path between this client and the MP? Kindly use this following ways to check if it is normal.
    https://www.manishbangia.com/how-to-verify-sccm-mp-health/
    Note: Non-Microsoft link, just for the reference.

    Besides, please try the steps:

    1. Uncheck the check box of Clients check the CRL for site systems from Site Properties.
    2. Reinstalled client with /NoCRLCheck CCMHOSTNAME=InternetFQDN with SMSSite code switches.

    For the reference:
    https://social.technet.microsoft.com/Forums/en-US/907fe750-3282-4f9e-b75a-f6e29696c30c/regtask-failed-to-send-registration-request-message-error-0x87d00231?forum=configmanagerdeployment


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

  2. Ahmed MS 21 Reputation points
    2021-07-26T14:22:30.323+00:00

    I've noticed that I've multiple warnings in the MP component, like the following:

    117920-mp-warnings.png

    Regards,


  3. Clifton Hughes 0 Reputation points
    2024-07-24T22:38:31.2133333+00:00

    Saw this where the site was enabled/checked for the setting to Use PKI when available for client authentication, and when the customer refreshed their PKI infrastructure, the clients started using PKI certificates that were either not valid before or now they are valid longer than the self signed certificates, and we had to turn off this setting to allow the clients to get registered with the site and to be able to successfully download content from DP's. Newly installed or imaged clients could not register, and existing clients were having trouble either failing to download content or taking a really long time to download content, once we unchecked the Use PKI certificate when available on the Site Properties on Configuration Manager Current branch, it all started working again.

    0 comments No comments