http://blogs.msdn.com/b/steverac/archive/2010/11/22/the-case-of-the-mif-and-wmi-repository.aspxIf you have spent much time around SCCM engineers – at least those of us from Microsoft – you will have heard us decry customers deleting the WMI repository to fix issues with WMI.&#160; True that often deleting the repository seems to fix an issue butenTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/steverac/archive/2010/11/22/the-case-of-the-mif-and-wmi-repository.aspx#10099698Thu, 02 Dec 2010 20:31:35 GMT91d46819-8472-40ad-a661-2c78acb4018c:10099698Mitch<p>Interesting article. &nbsp;I have about 150,000 clients globally. &nbsp;I am going to guess and say that there are WMI issues with about 2% and the symptoms vary. &nbsp;This still equates to about 3000 clients scattered troughout the globe. &nbsp;We don&#39;t have enough technicians with the time or the skill to do this type of in depth analysis on each potentially damaged WMI repository. Can&#39;t run WMIDiag on every system and analyze on a case-by-case basis. &nbsp;Rarely do the other suggestions of re-compiling mofs, re-registering DLLs, etc. &nbsp;solve the problem. And in your case the repository needed to be rebuilt anyway. For years I have yet to see any real solution to this problem. &nbsp;Most of our WMI problems seem to be with mobile laptop users. &nbsp;I suspect mobile systems are more likely to shut down ungracefully which may explain a larger occurrence of WMI corruption (just my opinion). &nbsp;I wish Microsoft would publish something just stating that this is a recuring problem that is acknowledged and it is doubtful you will ever be able to manage 100% of your systems successfully. &nbsp;Maybe 95% at best when you consider additional issues such as Windows Update problems.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10099698" width="1" height="1">