My buddy Jamie recently posted a great write-up on how to review and analyze log files quickly and easily. It's a great post and if you ever have to troubleshoot any part of SMS 2003 or ConfigMgr 2007, or any System Center product for that matter, you need to check this out:
How do you parse log files today?
Do you routinely troubleshoot issues with SMS clients? Issues such as WMI not functioning, CCMEXEC not running, Bits issues, etc. The place I always start my troubleshooting is with the client log files (C:\Windows\System32\ccm\logs) as they contain a wealth of information and usually quickly lead you down the road to problem resolution.
In the past I've used simple scripts to parse the log files and that has worked fairly well, I've also fallen victim to manually opening log files one by one (by relevance to the problem I am working on) and looking/searching for keywords like 'failed' or 'error' or searching for a particular PackageID and it's associated entries. Although this works fine, it is very time consuming and tedious.
An easier way to get the same results:
To continue reading see http://blogs.msdn.com/jamoyer/archive/2008/01/28/analyzing-sms-sccm-log-files-the-easy-way.aspx
J.C. Hornbeck | Manageability Knowledge Engineer