MECM- SCCM Client Installation Workflow

In this article, we will discuss:

1. The workflow involved in the SCCM client installation (Manual or automatic)
2. Background process to complete the installation of the SCCM client.

Image credit: pei.com

Client installation method:

1. Client push installation
2. Automatic client push
3. Manual client installation
4. Group Policy installation.
5. Logon script installation
6. Microsoft Intune MDM installation
7. Software update point installation

Server Side:

1. On the server-side SMSProvider creates a *.ccr file under “C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box” which is the very first step in SCCM client installation (Both case either Manual client installation or automatic client installation)
2. SMS_CLIENT_CONFIG_MANAGER will read the *.ccr file and will start the SCCM client installation.
3. Check ccm.log on the server-side, if we have initiated the client installation from the SCCM console, and in case of command-line installation, we should always refer to the client-side installation logs.
4. The first activity, you will find in ccm.log is to connect the administration share with the help of the account which you have given for the client push.
5. Once the share is connected it will copy the setup/installation file on the client-side (\\CLIENTNAME\admin$\ccmsetup) folder.
6. MobileClient.tcf and cmsetup.exe are two important files that are being copied to the client from (C:\Program Files\Microsoft Configuration Manager\bin\I386\ )on the site server.

Client-Side:

1. On the client-side ccmsetup service gets created which leads to the next step of the client installation.
2. Clients look for the AD for MP details and MP provides the DP (distribution point) location based on the client boundary is mapped.
3. Clients copy the installation files from the DP and start the process of client installation.
4. We should always look for the below logs to check the SCCM client installation record.

Image Credit: Microsoft Documentation

Client Registration

We have installed the client. Now the client will start communicating with the main site server for policies and deployment. Here are a few points that will explain the communication steps after the client gets installed.

Client:

1. Once the client is installed, ClientIDManagerstartup.log creates and manages the client SMS GUID and where all the tasks are recorded which is being performed for client assignment and registration.
2. The client sends the registration request to the management point, which is recorded in the ccmmessaging.log

Server:

1. MP_RegistrationManager (MP_RegistrationManager.log, C:\Program Files\SMS_CCM\Logs) will start the process of registration of the client and complete it after validation and it also writes the *.rdr file for a client at “C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\regreq\” on the main primary site server.
2. SMS_Discovery_DATA_MANAGER (ddm.log) process the *.rdr file and inject it into the database of the site server, which will be eventually updated, and you will be able to see the client status as active in the console.