ConfigMgr Client Registration Flow

When a client installation is completed it must register the device in order for the computer object to be created and approved in ConfigMgr. Until that validation has taken place the ConfigMgr client will only have two actions visible on the actions tab; Machine Policy Retrieval & Evaluation Cycle, User Policy Retrieval & Evaluation Cycle.

If the registration is not successful then there are a few log files both on the client side and on the server side which needs to be investigated, starting with the logs on the client and then move on to the Management Point logs and Site Server logs.

Client:

1. Once ConfigMgr client is installed, ClientIDManagerStartup.log creates and maintains the client SMS GUID and identifies tasks performed during client registration and assignment.
2. Client Registration request send to MP. You can find MP communication in ccmmessaging.log on client machine.

Server:

1. MP_RegistrationManager (MP_RegistrationManager.log, in the folder ..\SMS_CCM\Logs on the Management Point server) process the registration request from client and complete the validation.
2. MP_RegistrationManager writes the *.rdr file for client under “[ConfigMgr installDir]\inboxes\auth\ddm.box\regreq\” on the Site Server.
3. SMS_Discovery_DATA_MANAGER (ddm.log) process the *.rdr file and update into Primary database.

This post is inspired by a longer blog post about client push installations by https://karthickjokirathinam.com/