No these are workstations. We run local virtual machines, and the versions change often. So they want to generate a list of the different versions we have out in the wild. Basically it is to let them know who is out of date and needs to be upgraded with the newest version of the virtual machine.
From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, November 11, 2013 3:25 PM To: '[email protected]' Subject: [mssms] RE: file extension not working for software inventory Are you running that on servers? Software inventory has a timeout value that tends to get exceeded on servers. ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Monday, November 11, 2013 2:24 PM To: '[email protected]' 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 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
