How the SCCM deploys/installs the CCM Client to a new client/machine

When troubleshooting a failed client install it can be useful to have a basic understanding of how the client installation process actually works. The below is a rough step through of how sccm deploys a client after it discovers a new machine. The following info was mostly cribbed from the MS website but rewritten somewhat:
 

First, SCCM goes in search of new machines......

 

1] SCCM finds a new machine and generates a CCR file (Client Configuration Request). This file contains information about the machine, including the name.

2] The Client Configuration Manager then uses the info in the CCR file to establish a connection to the Admin$ share on the newly discovered machine.

3] From there the Client Configuration Manager sets up a connection to the newly discovered machine’s registry (aka IPC$). If you open up the CCM.log file on the SCCM server you should see this IPC$ connection being established

4] The core components of the client (MobileClient.tcf and CCMsetup.exe) are copied from the \\servername\SMS_[sitecode]\bin\I386 share on the SCCM server into the %windir%\System32\ccmsetup folder on the newly discovered machine.
5] The Client Configuration Manager checks that the CCMsetup service has started and then disconnects from the client machine. The CCR file is added into the \\servername\SMS_[sitecode]\Inboxes\CCRretry.box. The Client Configuration Manager then does a second check of the newly discovered machine, if the SMS Agent Host (ccmexec) is running it deletes the CCR file.

OR

If the Client Configuration Manager establishes that the SMS Agent Host isn’t running or has encountered a problem then it ill rename the CCR file to the name of the newly discovered machine and moved into the \\servername\SMS_[sitecode]\Inboxes\CCRretry.box folder. Client Configuration Manager will check all the logs in this folder every hour for 7 days before deleting them. This info can be viewed in the ccm.log file

 

Meanwhile, bak on the newly discovered machine....

 

1] CCMsetup.exe starts up and then has a look in the MobileClient.tcf file. This file contains configuration info which tells the CCMsetup.exe where to find the Client.msi on the SCCM server. The MobileClient.tcf file also provides other info such as the SMS Site Code, the name of the Management Point and the site boundary.

2] CCMsetup.exe then downloads the client.msi file from the \\servername\SMS_[sitecode]\Client\i386 shared folder on the site server (it can also get it from the Management Point if so configured). The Client.msi installer is installed based on the settings configured in the SCCM console.

 

Once the client is installed, it needs to find itself….

 

1] If the setting has been enabled on the Client Push Installation properties, the client will automatically be assigned to a site using the property SMSSITECODE=AUTO which will prompt it to consult Active Directory for its site assignment. Assuming the AD Schema has been extended, the client will used LDAP to query AD for its site assignment and management point.

OR

 

If the AD Schema has not been extended or the property has not been specified, the client will have a look for a client locator point to ask for a site assignment and directions to the relevant management point.  

2] Once the client has found its default management point, it will kick off its initial request for policies...