Home Dashboard Directory Help
Search

DCR - CIM cmdlets not returning WMI metadata by Trevor Sullivan


Status: 

Active


25
1
Sign in
to vote
Type: Bug
ID: 782064
Opened: 3/25/2013 11:24:15 AM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description


When using the Get-WmiObject cmdlet, lots of WMI metadata is included with the resulting objects including:

1. WMI qualifier names/values (and qualifier metadata: IsAmended, IsLocal, PropagatesToInstance, PropagatesToSubclass, IsOverriable)
2. System properties
3. WMI class path (eg. \\servername\root\cimv2:Win32_ComputerSystem.Name="servername")
4. WMI instance path (eg. \\servername\root\cimv2:Win32_ComputerSystem)
5. ManagementScope options via "Scope" property
6. WMI class-level information: __DERIVATION, __DYNASTY, __SUPERCLASS, _SERVER, __NAMESPACE, __PATH, __GENUS, __RELPATH, et al.
7. ... and probably others I'm missing

This information is absolutely vital to effectively developing automation scripts leveraging the Windows Management Instrumentation (WMI) service.

Unfortunately, the CIM cmdlets module does not return the same information as Get-WmiObject does. Please modify the CIM cmdlets to include this vital WMI metadata. In some cases, the data format may differ somewhat: eg. WMI object paths may be express using WS-Management lingo, instead of WMI monikers.
Details
Sign in to post a comment.
Sign in to post a workaround.