/images/ducttape.png

DuPSUG Basics - Deux

Today was another great day with other PowerShell enthousiasts where I got to share some tricks of the trade. During DuPSUG’s second Basics event, I was once again able to provide a session, this time about “Improving your Scripts”. I had a blast and I hope others did too and as promised I’ve made my code available on GitHub on the general DuPSUG GitHub. I’d like to thank all the people attending today’s session for your time and patience, all other speakers for sharing their time, code and tricks and of course @EJHeeres for arranging the event perfectly.

Microsofts Community Leader Zone

Are you a speaker at events? Or perhaps you are a [co-]founder of a local User Group? Microsoft’s setting up a new tool/community to connect other speakers and to provide early access to events and such. Early Access signups are now available here. Curious to see what this means for you? Don’t wait up, sign up!

Using Visual Studio Code for PowerShell - Settings

Like many others, I’m giving Microsoft’s free code editor Visual Studio Code a try. Perhaps a bit late to the party, I know, but I’ve been a big fan of Microsoft’s built in PowerShell ISE editor, especially when combined with Dr. Tobias Weltner’s ISESteroids. So what’s this post about? Nothing special for now, just wanted to share my default Visual Studio Code settings.json file [Ctrl + , ]. This file sets your personal preferences within the editor, making the look and feel just a bit smoother to my liking.

Finding remote registry entries with Remoting disabled…

I had run into a situation where I quickly needed to check registry entries for various machines, but PowerShell remoting had not properly been enabled for all of the machines [and was not allowed to be set up on short notice]. Since I needed to quickly obtain the information for various keys, I turned to Google for advice. Local and Remote Firstly I’ll define the registry keys I’d like to have information about:

Script Dumpster: Find duplicate entries over multiple reports

Another day at the office.. Thanks to our friends who wrote the NotPetya worm, I received an email from our monitoring vendor to run reports to see if our machines are up-to-date on their patching. Unfortunately their reporting tool doesn’t properly distinguish between Windows Server 2008 and Windows 2008 R2, as well as Windows 2012 and Windows 2012 R2. Long story short, I had to create 4 separate reports, telling me if I had or had not installed the proper KB item on each machine.

New assignment, new challenges!

New year, new chances! First of all, I’d like to wish everyone visiting my page a happy 2017 🙂 I hope everyone had a blast and is eager to learn some more in the new year. As for myself, just before the year had ended, so did my previous assignment. Luckily a new assignment was already in the works and I literally went to job A on Tuesday and job B on Wednesday.