Had an interesting thread come through on Spiceworks the other day that required some detective work with WMI. In the past, when I did WMI calls with vbScript I usually had to Google it and find someone else who’d done what I wanted to do and modify their script. But with Powershell you don’t have to dig through different blogs, or try to slog through the MSDN documentation, now you can just inspect the data and do it directly. Here’s what I did.
In the IT world, Administrators love to debate which technology is better. Mac vs. PC, Android vs iOS, you name it we’ve argued over it. One that I’ve been seeing a lot of over the last few years is vbScript vs Powershell. As you probably know, I stayed in the vbScript world for quite a while because it was a safe, known haven that suited me. But then I came to Powershell, and learned how you can discover what’s going on in Powershell so easily. This started with using a great Integrated Scripting Environment (ISE) like PowerGUI or PowerShellPlus, but then I discovered a few other commands that helped me discover information about the objects I was working with. Specifically Get-Member. Read on to see how I recently used Get-Member to solve a problem.