-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WMIObject deprication #208
Comments
Do you possess an official statement or link confirming the deprecation of WMIObject with PowerShell 5 ?! |
Not in so many words just yet, but the writing is on the wall. https://twitter.com/jarwidmark/status/1751002076379803898 Best to start now updating to CIM than having to rush when it needs to happen. |
WMIC is a Command-Line Tools ... it has nothing to do with WMIObjects vs CIMInstance. Client Center does not depend on WMIC. |
I have not been able to find an infomation to confirm that however. Even though the command such as Get-WMIObject still exists in 5.1, documention for that command says depricated in Powershell 3.0 and the use Get-CIMInstance instead. |
So to verify that Get-WmiObject no longer works you can test this by removing the WMIC optional feature in the latest version of Windows 11
As such we can confirm any application that still calls Get-WmiObject is dependent on WMIC Optional Feature installed. |
If Get-WmiObject really depends on the WMIC Optional Feature then things will get hectic in support as many scripts depend on Get-WMIObject... But to make is short, there are no plans to refacture ClientCenter.... In worst case it will die with Get-WMIObject .... |
Have noticed that many of the commadlets use WMIObject instead of CIMInstace.
Considering WMI is getting closer to deprecation it would be worth overhauling all the query commands to CIM
The text was updated successfully, but these errors were encountered: