SMS 2003/ConfigMgr logging
Came across this excellent blog post for troubleshooting SMS issues, its helped me out so many times, as I can never find it, adding it so its always available and I can find it easily, some of the same techniques apply to SCCM.
The main feature of this post I use and always recommend is as follows:
The following registry value will point to the inventory temp directory:
- HKLM\Software\Microsoft\SMS\Mobile Client\Inventory ----> "Temp Directory".
- Examples:
- 1. To save off inventory reports on a client that is not also an MP, create the following file:
- %systemroot%\system32\ccm\inventory\temp\archive_reports.sms
- 2. To save off inventory reports on a client that is also an MP, create the following file:
- <x>:\sms_ccm\inventory\temp\archive_reports.sms
- The XML file will be saved in the inventory\temp folder.
Note: Delete the archive_reports.sms file when you are done trouble-shooting.
-
Open up the inventoryagent.log from %systemroot%\system32\ccm\logs
-
Perform a full hardware inventory scan via SCCM Client Centre - Client Actions drop down list - HW Inventory (full) or the Right Click Tools
-
Wait for the HINV to complete by monitoring the inventoryagent.log, if you see examples like "Collection: Class "SMS_ActiveSyncService" does not exist out. InventoryAgent" - this is fine, just means the class doesnt exist on that machine and can safely be ignored.
-
Once it completes should see along the lines of Task Completed (cant quite recall the exact words).
-
In this folder "%systemroot%\system32\ccm\inventory\temp" you should now have an xml file which you can view to see if any data is being pulled back by the clients.
It all sounds long winded but it will help to identify if the issue is with the clients or the MP.
You can read all the other logging options here, credit goes to Russ Slaten.
http://blogs.msdn.com/rslaten/archive/2006/03/14/SMS-2003-Logging.aspx