ThePowerShellGuy.com

Back again with another comparison between .NET and WMI performance. While WMI can be very useful and often the only way to accomplish some remote oriented tasks, you will rarely hear anyone that has worked with WMI classes for long brag about its performance. Whenever possible I try to discover alternatives to WMI and I’ve found what I think is ...

WMI seems to get recommended for most ''remote'' queries in powershell. This is due in large part because the get-wmiobject cmdlet includes built in support for querying remote machines. However, I've found that WMI can be slow and whenever I find a dotnet alternative, I like to compare the speed of each method. One of my scripts remotely queries ...