WMI is cool to query and script against, but when WMI becomes corrupt or enters into an unmanageable state, you may as well just go home. WMI is probably the number one issue with images, deployments, SCCM client woes, etc., etc. Why hasn’t Microsoft fixed this yet? Let’s cross our fingers and hope for the future and also hope that they don’t rename it to WMICloud or something.
Why do I bring this up now?
I just caught this post on the Microsoft blogs:
This talks about having to be extra careful with WMI conflicts during App-V package delivery. <groan>