Client installation log file located on the client:

• %windir%\system32\ccmsetup\ccmsetup.log
  …or
• %windir%\ccmsetup\ccmsetup.log

Installing the SCCM client manually is a simple case of running a command directly from the SCCM site share.

\\servername\SMS_<sitecode>\Client\ccmsetup.exe

A number of command line options are available if the Active Directory Schema hasn’t been extended for Configuration Manager 2007, these options are not needed if AD has been extended and Publish this site in Active Directory Domain Services is selected in the Advanced tab of the Site Properties dialog box, then client computers will automatically search Active Directory for installation properties.

/mp:SMSMP01 – Specifies the management point SMSMP01 to download the necessary client installation files.

/logon – Specifies that the installation should stop if an existing Configuration Manager 2007 or SMS 2003 client is found on the computer.

SMSSITECODE=AUTO – Specifies that the client should determine its Configuration Manager 2007 site code by using Active Directory or the server locator point.

FSP=SMSFP01 – Specifies that the fallback status point named SMSFP01 will be used to receive state messages sent from the client computer.

For example to run in a batch file:

\\sccm_server\SMS_<sitecode>\Client\ccmsetup.exe /mp:sccm_server /logon /native SMSSITECODE=<sitecode> FSP=sccm_server

You might get an error in the log file for some older clients Windows Server 2003 or Windows XP, “The site is in Native Mode. A client reboot is required to continue installation”

This is genuinely due to BITS not being installed – Native mode has an external dependency on BITS 2.5, and hence the logging entry.  This is installed with the Configuration Manager client and requires a reboot to complete the installation.  http://technet.microsoft.com/en-us/library/bb680537.aspx When BITS is installed on client computers a restart is generally required.

More info for the entire manual installation process can be found here.