Share This Post

Even in App-V, WMI can be, ahem, problematic

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:

Overcoming WMI Deployment Conflicts in Microsoft Server App-V

This talks about having to be extra careful with WMI conflicts during App-V package delivery. <groan>

Share This Post

A community professional, keynoter, and evangelist who has driven social media and marketing strategies, editorial successes, delivered customer successes and built some of the largest and longest-running online communities. Rod has created, managed and grown small, medium, and mega-sized conferences; run entire editorial teams to deliver record traffic and market leadership; as product manager, directed the success of hundreds of product releases; supported sales and marketing to ensure customer success; developed, run and sold businesses; written thousands of technical articles, white papers, case studies, and technical documentation; hosted and delivered hundreds of attendance shattering webinars and virtual tradeshows; and delivered keynote speeches and sessions at a wide variety of events including conferences, webinars, events, and user groups.

Leave a Reply