Sure, just let me add a few comments and clean them up a little. I’ll post them later this morning.
Thanks, Ken … From: [email protected] [mailto:[email protected]] On Behalf Of Gary Ossewaarde Sent: Tuesday, August 13, 2013 7:03 AM To: [email protected] Subject: RE: [mssms] BADMIFS - dataldr.box Any interest in sharing any or all parts of said script? I’m just getting into CM12 and have found some bad mifs that I’d like to check into. Gary From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lutz, Ken Sent: Tuesday, August 13, 2013 9:52 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] BADMIFS - dataldr.box Hi Sherry, That’s what I have done. I created a PowerShell script to walk through the bad mif folders and send a full inventory command to the offending machines. Thanks, Ken … From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Monday, August 12, 2013 6:04 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] BADMIFS - dataldr.box Yes, I'd start with forcing a full hinv to clean up hopefully most of them "Lutz, Ken" <[email protected]<mailto:[email protected]>> wrote: 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. [content://com.fsck.k9.attachmentprovider/b6ae8a1e-bc1a-4c90-ab1e-3a5a0dcc0286/8188/RAW] Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260
