I did write a PowerShell script that will pars the machine name out of the bad mif file, then send said machine a full hardware inventory command, and keep a log file of the machine name. I then created a second script that will count the number of times a machine shows up in the log file. It is showing a few machines that have produced multiple bad mif files. I guess it's time to remove and re-install the client on those machines.
Thanks, Ken ... From: [email protected] [mailto:[email protected]] On Behalf Of Eswar Koneti Sent: Monday, August 12, 2013 6:00 PM To: [email protected] Subject: RE: [mssms] BADMIFS - dataldr.box Did you try this ? http://eskonr.com/2010/01/inventory-data-loader-issues-in-sccm-inboxes/ Eswar Koneti www.eskonr.com<http://www.eskonr.com> ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Date: Mon, 12 Aug 2013 10:07:18 -0700 Subject: [mssms] BADMIFS - dataldr.box I have a question about BADMIFS in the dataldr.box folder. I have been monitoring this for a few days now and have 154 bad mifs since 08-05-13. Most of them (111) are in the NonExistentRow folder. What is the best way to deal with these bad mifs? Would a good starting point be to force a full hardware inventory on the offending machines? I'm looking into the inventoryagent.log files now, but not seeing anything that stands out. [cid:[email protected]] Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260
<<inline: image001.png>>
