There are a number of reasons why the ConfigMgr client fails to install… permissions, WMI, environment variables, certificate errors etc. So this post is going to be a collection of the random installation errors that I have come across in my time and how they were resolved. As news ones are identified I will add to this post.
Symptom:

IF EXIST%windir% ccmsetup ccmsetup.exe GOTO DEL12 IF EXIST%windir% SMSCFG.INI GOTO DELINI GOTO END:DEL12 echo Found SCCM client v 2012. Removing.%windir% ccmsetup ccmsetup.exe /uninstall RD /S /Q%windir% ccmsetup RD /S /Q%windir% ccm RD /S /Q%windir% ccmcache echo SCCM Client 2012 removed. IF EXIST%windir% SMSCFG.INI GOTO DELINI. Ccmsetup 11: (0x087C) After its done copying over the setup file and installed the prerequisites, it launces the msiexec with the parameters and you can head over the other log file client.msi (This is a huge log, and not always very informative ) Most likely if the setup fails you can see this in the ccmsetup.log. This script is tested on these platforms by the author. It is likely to work on other platforms as well. If you try it and find that it works on another platform, please add a note to the script discussion to let others know. The next time that CCMSetup runs, the clients find an updated management point or distribution point, and they reinstall the client software. This upgrades the clients to Configuration Manager. These continual upgrades occur outside the normal upgrade process that is configured by the administrator.

• Client installs successfully (%WinDir%ccmsetupLogsccmsetup.log)
• Software Center is blank (Client reinstall)
• On a new client install the logs directory (%WinDir%CCMLogs) is mostly empty
• Errors can be found in both the CertificateMaintenance.log and ClientIDManagerStartup.log

Ccmsetup Missing

• On the client open the Services MMC snap-in and stop the SMS Agent Host service
• Navigate to C:ProgramDataMicrosoftCryptoRSAMachineKeys
• Locate the crypto file starting with “19c5cf”
• Backup the file to a temporary directory and then delete it
• Restart the SMS Agent Host service
• The client should recreate the crypto file starting with “19c5cf” and the go through the registration process

• Client install fails with error code 0x80004004 (%WinDir%ccmsetupLogsccmsetup.log)
• MSI error code 1789 referenced in the client.msi.log (%WinDir%ccmsetupLogsclient.msi.log)

• On the client open the Services MMC snap-in and ensure that the Netlogon service is set to Automatic and it is running
• Open regedit and navigate to HKLMSoftwareMicrosoft
• Delete the ccmsetup key
• Reboot the machine
• Reinstall the client

Download Ccmsetup Exe 2012 Full

• Client fails to install with the Couldn’t find an MP source through AD. Error 0x80004005 (%WinDir%ccmsetupLogsccmsetup.log)

• Ensure that your boundaries and boundary groups in ConfigMgr are setup appropriately
• On the client ensure that the Netlogon service is running and set to Automatic
• Ensure the client is communicating with the domain properly
• Reinstall the client

• Client installation fails with error code 1603 (%WinDir%ccmsetupLogsccmsetup.log)

• Open regedit and navigate to HKEY_USERSS-1-5-18SoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders
• Change the value for %APPDATA% to %USERPROFILE%AppDataRoaming
• Reinstall the client (Reboot may be required)

• The client installs successfully however it will not report into it’s management point
• Registration errors can be found in the ClientIDManagerStartup.log
• Client does not show up as having an active client installed in the ConfigMgr client

• Backup all files in the C:ProgramDataMicrosoftCryptoRSAMachineKeys folder for Windows 7 or C:Documents and SettingsAll UsersApplication DataMicrosoftCryptoRSAMachineKeys folder for Server 2003
• Remove the (19c5cf9c7b5dc9de3e548adb70398402_ac168ff2-23d3-4a00-bd1d-dd27ff040362) folder
• Restart the SMS Agent Host Service to recreate these certificates
• Client should now register and start pulling down policies

• Client fails to install with error code 80041002 (%WinDir%ccmsetupLogsccmsetup.log)

• Open an administrative CMD prompt
• Navigate to C:Program FilesMicrosoft Policy Platform
• run the following command mofcomp ExtendedStatus.mof
• Reinstall the client