Troubleshooting SCCM 2007 R3 is pretty complex, log files are your friends.

IIS log files are used a lot in Native Mode setups – C:\inetpub\logs\LogFiles\W3SVC1

Server Log Files – %ProgramFiles(x86)%\Microsoft Configuration Manager\Logs

• ConfigMgr distribution point
• ConfigMgr management point (MPSetup.log)
• ConfigMgr reporting point (rsetup.log & SMSReportingInstall.log)
• ConfigMgr software update point (SUPSetup.log)
• onfigMgr server locator point (SMSSLPSetup.log)
• ConfigMgr fallback status point (SMSFSPSetup.log)
• ConfigMgr Reporting Services Point (SRSRPSetup.log)
• ConfigMgr state migration point (SMSSMPSetup.log)
• Ccm.log – Records client configuration manager tasks
• Fspmgr.log – Records fallback status point activities
• Hman.log – Records site configuration changes, and publishes site information in Active Directory Domain Services
• Mpcontrol.log – Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes
• Policypv.log – Records updates to the Advanced Client policies to reflect changes to client settings or advertisements
• Sitecomp.log – Records maintenance of the installed site components
• Network discovery (netdisc.log)
• Client push installation (ccm.log)

Client Log Files – %windir%\system32\CCM\Logs

• CAS.log – Content Access service. Maintains the local package cache.
• CcmExec.log – Records activities of the client and the SMS Agent Host service
• CertificateMaintenance.log – Records certificate maintenance for Active Directory Domain Services and management points
• ClientIDManagerStartup.log – Records the creation and maintenance of client GUIDS and also the registration status of the client computer
• ClientLocation.log – Records site assignment tasks
• ContentTransferManager.log – Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
• DataTransferService.log – Records Background Intelligent Transfer Service (BITS) communications for policy or package access
• Execmgr.log – Records advertisements that run
• FileBITS.log – Records all SMB package access tasks
• InternetProxy.log – Records proxy server detection status for Internet-based client management
• LocationServices.log – Records attempts to find management points and distribution points
• PolicyAgent.log – Records policy requests using the Data Transfer service
• PolicyAgentProvider.log – Records policy changes
• PolicyEvaluator.log – Records new policy settings
• Scheduler.log – Records schedule tasks for all client operations
• StatusAgent.log – Records status messages that are created by the client components

PXE Service point log files:

• %ProgramFiles(x86)%\Microsoft Configuration Manager\Logs\pxecontrol.log – PXE server status and health information
• %ProgramFiles(x86)%\SMS_CCM\Logs\smspxe.log – Client PXE requests
• %ProgramFiles(x86)%\Microsoft Configuration Manager\Logs\PXESetup.log – Setup information

Client installation log file located on the client:

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

Client installation push log file located on the server:

• %ProgramFiles(x86)%\Microsoft Configuration Manager\Logs\ccm.log

For a complete list of Log Files for SCCM 2007 R3 – http://technet.microsoft.com/en-us/library/bb892800.aspx

To make heaps easier to read log files, use SMS Trace from the System Center Configuration Manager 2007 Toolkit V2, SMS Trace doesn’t need to be installed and can be run from itself, it can be set as the default viewer of log files.

Another good tool to use on the clients is SCCMNativeModeReadiness.exe which is located %windir%\System32\CCM when run from the command prompt the data is exported to a log file of the same name located %windir%\System32\CCM\Logs. More information about this tool can be found here http://technet.microsoft.com/en-us/library/bb680986.aspx