You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a fabulous tool! It's helped us many times.
Are you willing to go to the trouble of changing how it works, by changing references to WimObject to CimInstance (and doing the associated syntax adjustments)?
This is a fabulous tool! It's helped us many times.
Are you willing to go to the trouble of changing how it works, by changing references to WimObject to CimInstance (and doing the associated syntax adjustments)?
I'm seeing Microsoft push us to use CIM in preference to WMI (deprecated, no longer supported in powershell core), eg:
https://devblogs.microsoft.com/scripting/should-i-use-cim-or-wmi-with-windows-powershell/
and
https://www.petri.com/what-is-the-difference-between-wmi-and-cim
For backward compatibility you could keep the existing capability, and have a preference item to choose output in CIM or WMI mode?
A benefit may be keeping WMI Explorer compatible with other platforms. Might need a name change... CIM Explorer or MI Explorer or something else?
https://powershell.org/2015/04/management-information-the-omicimwmimidmtf-dictionary/
For your consideration, thank you.
The text was updated successfully, but these errors were encountered: