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.
I don’t normally hawk equipment on this blog, but I have to rave a bit about Meraki network equipment. These guys are game changers, so much so that Cisco felt compelled to buy them. I just hope they don’t screw it up! This is the future of networking equipment, and the template for every device you own.
Simple script came across this week at Spiceworks. The funny thing was, the script didn’t solve the OP’s problem in the slightest! Turns out he was looking for a script to list several groups and who are members of it. Still, I think this request was interesting and wanted to write a little about it.
One of the fallouts of the outage I had this week (Read Here) was that my backups for that night were stopped. Since Veeam creates snapshots to do it’s backups those snapshots were left on the server. The next night another backup came in and created another snapshot, and the very next day…
Nothing quite like waking up in the morning and getting a notification that everything is down, and the kitchen sink is clogged too.
I’m not the most patient person in the world, nor the most trusting and this has always translated itself into my scripts by giving constant feedback on what’s going on. Write-Progress is a great mechanism for doing this within Powershell as it will provide you with a cool looking progress bar, and bonus, it’s really easy to use!
I wrote about multithreading using Runspace here, but I also wanted to talk about running them the Powershell way using jobs. I want to make sure I give credit where it’s due, because most of my work in Jobs is based on Ryan Witschger‘s work. He writes a great Powershell blog called Get-Blog.com (great site name, too). Anyway, read on for my riff on Powershell jobs and the 3 step process you need to use them.