I was checking on disk space and my backup and found that I have just over 20k files in "\SiteServer\SMSServer\inboxes\auth\dataldr.box\BADMIFS" When I look at the live folder "Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS" I only have 232 files. These 20k files are using about 13g of data, can I delete them from the backup folder? The dates go back as far as December of last year.

Yes, you can delete the files from the badmifs folder.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

See, More details http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/db2207ad-38b3-456b-947e-9133f2539af6Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

You should delete Bad files from inboxes every day by using some vbscript or batch file. have a look on your daily things to do on sccm server. Daily Maintenance Tasks http://technet.microsoft.com/en-us/library/bb632564.aspx This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I think you should investigate and fix the bad MIF problem, so you can get proper inventory data. Bad MIF files occurs in the following situations: MIF file size is too large, as I know in SMS it is limited up to 5,000,000 bytes If a NOIDMIF or an IDMIF can not be parsed successfully because syntax errors meaning simply that it is not formatted correctly. If this occurs the MIF file is marked as bad. To resolve this issue you can use the MIF checker tool. An IDMIF file can also be marked as bad if it is being used to update an existing clients record in the SQL database. This can mean either of two things: the MIF file is a delta (Changed) inventory file from a client resource that has no full inventory in the SQL database or the MIF file is a delta inventory file that conflicts in content or information from one that exist in the SQL database inventory data for the client. To fix the upon 3rd issue, you should reinstall clients for the computers who have the upon issue 3. Also paddy's suggestion to clear the bad MIF files is needed to relase the disk space. Here are some good posts about how to troubleshooting the bad MIFs: http://eskonr.com/2010/01/inventory-data-loader-issues-in-sccm-inboxes/ http://trevorsullivan.net/2011/06/13/configmgr-hardware-inventory-mif-errors/ Hope this will help. Thanks

MIF file size is too large, as I know in SMS it is limited up to 5,000,000 bytes You can edit this to make it 50 MB in size. 50 MB is the max size of any mif file. http://support.microsoft.com/kb/319167http://www.enhansoft.com/

large mif file size is almost always because you have ccm_recentlyusedapps enabled in your SMS_Def.mof. If you rarely enable new Software Metering Rules; there is almost no negative impact in editing sms_def.mof and changing TRUE to FALSE on ccm_recentlyusedapps. There's a few 3rd party applications that, if you have them, rely on the data returned from ccm_recentlyusedapps, but in general you can change that to FALSE with no issues. Also... it might be huge because of this (if you decide you need to keep ccm_recentlyusedapps set to TRUE): http://myitforum.com/cs2/blogs/skissinger/archive/2009/07/03/selectively-disable-ccm-recentlyusedapps-per-client.aspxStandardize. Simplify. Automate.