Sometimes when troubleshooting SCCM client software inventory, it is useful to retain the XML file which contains details on what the scan discovered. To do this, simply create a file named “archive_reports.sms” within C:\WINDOWS\system32\CCM\Inventory\temp\. If the scan is just reporting a delta, the file will be small. But if it is a full SINV scan, then it could be large (the biggest I’ve seen is around 75 MB)
Queue of Upcoming Posts
- Scripting XP Power Settings
- "Homegrown" Client Health Solution
- SCCM Superflows
- Creative Solution for Using Different Network Settings in Task Sequences
- Scripting the backup of VMWare Server 2 VMDKs
Categories
- How-To (9)
- Miscellaneous Ramblings (7)
- SCCM (18)
- Scripting (10)
- Troubleshooting (9)
- Uncategorized (2)
Pages
Useful Utilities
Top 10 Most Viewed Posts
- My SCCM 2007 SP2 Upgrade Path
- Script to Prompt for System Name in SCCM OSD
- Post SCCM 2007 SP2 Upgrade Tasks
- Duplicate SCCM Client GUIDs
- SCCM Task Sequence Error Codes & Fixes
- SCCM 2007 SP2 Upgrade - Prereq Checker
- Issues of Post-SP2 Upgrade for SCCM 2007
- Fix for SCCM Remote Tools
- Scripting Windows Live 2009
- HTA BackEnd Script for OSD
Top 10 Blog Clicks
Blog Stats
- 13,594
Recent Comments
| Nicolas Moseley on My SCCM 2007 SP2 Upgrade … | |
| Reuvy on My SCCM 2007 SP2 Upgrade … | |
| Nicolas Moseley on Scripting Windows Live 20… | |
| K.G on Scripting Windows Live 20… | |
| Jay Connor on My SCCM 2007 SP2 Upgrade … |


No comments yet
Comments feed for this article