How the Client works.

How the Client works....

Once the Setup program is complete, the SCCM Advanced Client obtains a site assignment, sends the heartbeat discovery information to the SCCM site server, and then contacts the default management point to retrieve the SCCM Advanced Client policy.

During the pre-installation phase, SCCM discovers the client computer and then generates a client configuration request Client Configuration Request file. The CCR file contains the client computer name and additional information.)

The SCCM Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.

The Client Configuration Manager connects to the client registry and gathers information about the client. This process is displayed as a log entry in the Ccm.log as connecting to IPC$.

The SCCM core component files, MobileClient.tcf and Ccmsetup.exe, are located in the SMS\bin\I386\ folder. These files are downloaded to the %windir%\System32\ccmsetup folder on the client computer.

The Client Configuration Manager verifies that the Ccmsetup service started successfully before disconnecting. The CCR file is added to the SMS\Inboxes\Ccrretry.box folder for verification that the installation succeeded on the server. On a second verification pass, SCCM determines that the SMS Agent Host is running, and then deletes the CCR file.

If the Client Configuration Manager encounters any errors during this process, the CCR file is renamed to the name of the target client computer and is put in the SMS\Inboxes\Ccrretry.box folder. The Client Configuration Manager checks for files in this inbox folder every 60 minutes and tries to reprocess them 168 times (7 days) before they are discarded. This information is logged in the Ccm.log.