I did check for that, the largest MIF file that I saw was 599 KB. I did wait for a couple of months, but the resynchronization cycles never caught up, on 4/11 I had 2,141 BadMIFs, and on 6/17 it had cycled down to 1,292. I suspect the resynch cycles never caught up because of the large number of laptops we have in our environment.
From: [email protected] [mailto:[email protected]] On Behalf Of John Aubrey Sent: Thursday, June 26, 2014 12:12 PM To: '[email protected]' Subject: RE: [mssms] HW inventory scan schedule I use every 12 hours. We have around 500 clients. I have had some issues with BadMIF's in the past. Mine mostly are due to migrating SCCM to a new server and starting fresh and the clients reporting delta's and the system expecting fulls. This usually gets ironed out on its own after a few cycles. Could it be the size of your MIF are too big? I believe that can cause them to become bad. John Aubrey Description: Description: Description: NorwoodMED_logo_small.jpg 2122 Winners Circle Dayton, Ohio 45404 Phone: 937-228-4101 X 1179 Fax: 937-228-2754 From: [email protected] [mailto:[email protected]] On Behalf Of Art Flores Sent: Thursday, June 26, 2014 12:44 PM To: [email protected] Subject: [mssms] HW inventory scan schedule CM 2012 SP1 CU3 I had our CM client settings for hardware inventory configured to do daily scans. After seeing a large number of BadMIF files, and not being able to get rid of them by resetting the inventory to force a full scan, I opened a ticket with Microsoft. They asked me to reset the inventory on the computers causing bad scans (I didn't tell them I had already done this, I wanted to see what they did), so I wrote an updated script and ran the commands again. I got these same commands from an email on this list. WMIC /namespace:\\root\ccm\invagt path inventoryActionStatus where InventoryActionID="{00000000-0000-0000-0000-000000000001}" DELETE /NOINTERACTIVE WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}" /NOINTERACTIVE After I reported to Microsoft that the WMIC commands weren't fixing the issue, they did some more troubleshooting, and then made the following 2 changes. Changed the hardware inventory from daily scans to every 4 days, and deleted all the BadMIF files. I would like to ask the group here the following questions to compare numbers against our environment. I personally would like to do daily scans for updated data, but I don't want to have the BadMIF files issue either. 1. What is your hardware inventory scan schedule set to? Changed from daily to every 4 days. 2. How many clients are in your environment? 4,000 3. Are you still experiencing a large number of BadMIFs? No
