The CCR (Client Configuration Request) Process is one of the processes in which an SMS client machine is installed to a site server. This article will provide you with a high level overview of the CCR process.
The process first begins with the SMS site server discovering the potential client machine and when it locates it the machine name and additional information about the client is written to the CCR log file. Next the SMS Client Configuration Manager (CCM) attempts to connect to the machines Admin$ share on the machine.
If the connection is successful CCM then attempts to connect to the client machines registry where it gathers additional information about the machine that is then written to the CCM log (Ccm.Log) file connection to the Inter-Process Communication (IPC$) share.
At this point if all the processes connect as expected core SMS component files are copied to the machine. The Ccmsetup.exe and MobileClient.tcf files are first copied to the %WinDir%\System32\CcmSetup folder on the client from the site servers SMS\Bin\I386\ folder. Then the CCM process attempts to verify that the CcmSetup service has successfully started on the machine and disconnects if the service has started as expected.
Then the completed client machines CCR file is placed in the SMS\Inboxes\CcrRetry.Box inbox to be verified that the installation has been successful. After this process has been verified a second verification is launched where the Agent Host file on the client is interrogated to ensure that is it running and then the original CCR file is deleted.
It is important to note here that if any failures or errors are detected by the CCM process the originally created CCR file for the client machine is renamed to the client machines NetBIOS name as ComputerName.Ccr and moved to the SMS\Inboxes\CcrRetry.Box directory. After the fie is placed in the CcrRetry.Box the CCM process attempts to process the CCR file to resolve any detected errors every hour (Sixty Minutes) for one week (Seven days) before the CCR file is deleted and the information’s written to the Ccm.Log file on the site server.
The ComputerName.Ccr file is a text based file and you can view the file using notepad or any other text based editor and see the number of processing attempts that have been attempted. A typical ComputerName.Ccr file will look like the following:
[NT Client Configuration Request]
Machine Name=Computer001
Domain=XXX
IP Address 1=192.168.100.200
Initial Request Date=02/20/2007 10:35:19
[IP Address ]
[Resource Names ]
Resource Names 1=Computer001
[Request Processing]
Latest Processing Attempt=02/21/2007 09:37:28
Last Error Code=5
Number of Processing Attempts=99
Error Event Created=02/21/2007 10:49:35
[IDENT]
TYPE=Client Config Request File
As you will notice in the example above you can look at the Last error code in the CCR file to gather information that will allow you to troubleshoot the SMS client installation process. The error 5 in this case is an access denied error and tells you that the required permissions for the SMS client install process to compete are not met.
This VBS script will allow you to enter an Advanced client resource machine name into an input dialog