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.
Had someone at Spiceworks ask a question about a script they were trying to use so I asked them to post the relevant code and, lo and behold, it was my Simple Server Status script! He was having a problem with authentication because the ID he was running the script under didn’t have rights and he needed to run the script with his domain level credentials. Never got an answer as to why he couldn’t just run the script with those credentials, but modifying the script to use alternative credentials should be easy enough. Of course, it never is.
Work has been pretty busy, and is likely to be for the foreseeable future! We’re remodeling our manufacturing area, adding a new lab on the 2nd floor (we never occupied the 2nd floor before!), adding 10 new wireless access points (VLANS, multiple SIDs, new wireless hardware platform, oh my!), implementing a new ERP system, planning for a new CRM system, rolling out new PC’s and laptops, new conference rooms, planning a remodel in our HQ building and a bunch of other things too! If you noticed I didn’t post anything last week, that’s why. Not to mention, nothing really interesting has come across my desk from Spiceworks or PowerGUI. Then the boss mentioned he was working on something, and the more he talked about it the more I realized I might be able to do what he wanted in Powershell, especially since this wasn’t going to be a one-off kind of thing, but something we’d have to do on a regular basis!
Time for Part 2 of talking about Network Discovery, the Powershell version. Part 1 can be found here.
My most popular script on Spiceworks, by far, is Network Discovery. I posted it over 3 years ago, and actually wrote it much earlier than that! Time to take another look at it and give it a Powershell make-over. If you’re new to a company and want to find out the basics of what is going on, or a consultant going into new places all the time you’ll want to take a look at this script!
Great little script request came across on Spiceworks last week, something I’ve been looking forward to for a long time but never really thought I’d get a chance to do. Time to unlock the power of Remoting in Powershell and dive into true Distributed Computing–not multi-threading, but Distributed Computing!
One of the things I’ve been meaning to do is create a script to telnet to my various network devices and download the configuration as a poor man’s backup. Well, recently this post came across Spiceworks and I felt it was time to take a deeper look at how to do this.
This has come up at Spiceworks a couple of times, the which should I learn discussion. vbScript or Powershell? Considering the theme of this blog I don’t think you need to ask which camp I stand in. But what about this steep learning curve? Here are my thoughts.