What's New in MI?
Windows 8 and Windows Server 2012 introduced new ways of creating Windows Management Infrastructure (MI) applications. This topic highlights these changes and, where appropriate, provides links for more information:
Tight alignment with standards
- Work across systems using the HTTP-based WS-Man protocol. (DCOM is still supported.)
- Align with the CIM 2.60 Infrastructure specification, including standard indications (events) and errors.
New native-code provider APIs
- No more COM coding required! Developers can now focus on developing the business logic, rather than the complex COM coding.
- New providers contain the MOF & MFL, reducing the number of items developers must install.
API support for rich PowerShell semantics
- Enables MI Provider developers to improve the IT pro experience when using PowerShell with MI.
- Provides scripts and client applications for improved user experiences.
New approach to creating PowerShell cmdlets from MI providers using XML
- Developers and advanced IT pros can use CDXML to wrap existing CIM classes, creating PowerShell cmdlets without .NET coding.
- Developers can create cmdlets in native code by implementing a MI provider and writing CDXML to go with it.
- For more details, see the CDXML section.
Compatibility with WMI
The new version of MI maintains full compatibility with the older Windows Management Instrumentation (WMI) implementation.
Both new and existing WMI providers work with the new MI client applications. Existing client applications work with new and existing WMI providers. The new Indications and CIM Errors are mapped to the older Events & WMI error structures automatically.
The new version of MI ships as a downloadable update to Windows 7, Windows Server 2008 R2, and Windows Server 2008 Standard via the Windows Management Framework 3.0.