Expose WMI classes as rich PowerShell commands with detailed documentation and manage local and remote systems using WMI via the wmix module for PowerShell.
The PowerShell WMI Extensions module is a project that I wish I had started as soon as PowerShell 2.0 was released in 2009. It has been in development since late 2011, after I had been working on my pspx module for many months, and it is one of the most ground-breaking modules I have ever produced. The purpose of this module is simple: to auto-generate advanced functions that look and feel like cmdlets, complete with rich parameters, help documentation, examples, remoting support, security customizability support, and everything that you would expect from top-notch PowerShell commands by harvesting the rich data that is stored inside WMI, reducing as much as possible (or ideally eliminating) the need to dig through WMI documentation or to use more complicated WMI cmdlets to manage your infrastructure.
WMI is a very broad and powerful management interface that has been exposed to PowerShell since it was first released. Unfortunately, the manner in which this rich management interface was exposed to PowerShell was through a very small set of generic commands. Figuring how to use these generic commands to manage WMI is challenging at best. None of the documentation embedded in WMI is exposed. Objects returned from the WMI cmdlets don't look or behave the same as objects returned from .NET classes. WMI management classes are not easily discoverable. WMI contains many classes that you will never need to know about or think about, and this large pool of classes makes it difficult to find what you are looking for. These opportunities, and many more, were the inspiration behind the wmix module.
http://wmix.codeplex.com/
Kirk Munro, Product Manager, Architect, and PowerShell MVP for hire
http://wmix.codeplex.com/
Kirk Munro, Product Manager, Architect, and PowerShell MVP for hire
