Check a workstation you expect "should" report that it has some *.vmdk files.
1) check it's inventoryagent.log. Any errors? Timeouts? Do you even see a line about select Name, Path... From FileSystemFile where Name ... '*.vmdk' ... Does that line succeed on the client? or is the next line an error or timeout? 2) If it looks like that *.vmdk succeeded... go run wbemtest, and connect to root\ccm\invagt (just like in the line) and do a select Name, path... exactly as listed in that line. Any results? If you don't get any results interactively, neither will CM get any results to forward. Sherry Kissinger Microsoft MVP - ConfigMgr [email protected] ________________________________ From: Kevin Johnston <[email protected]> To: "'[email protected]'" <[email protected]> Sent: Monday, November 11, 2013 2:23 PM Subject: [mssms] file extension not working for software inventory I have added a *.vmdk to my client settings so that we can find machines that have this file. I have tried it in 2 ways: I put in the actual path the files are supposed to be stored in, and I left it as All client hard disk. I have let the policy run (currently set to 2 days) then went to reports and ran computers with a specified file typed in *.vmdk and nothing, then I type in *.exe and nothing. If I run all inventoried files on a specific computers, I see all the .dll and .exe’s on that computer, but when I do a find for .vmdk it finds nothing. Am I missing something? I want to make sure that this file gets inventoried as I am asked to run reports on who has this on their machine. Any ideas where I am going wrong? Thanks, Kevin Johnston
