I love being a lurker and just consume as much information from random sources (lately a lot of Twitter for my Tech fix).

Today I found this awesome gem (thanks to DexterPosh): the Azure Citadel.

Just a quick tip for personal reference [as I keep forgetting it 🙂 ]. You can easily find out which versions of the Windows OS are available on an install.wim file [generally found within a Windows ISO file] using the following command: 1 Get-WindowsImage -ImagePath <location of the install.wim file> This will provide you both the Index number as well as the name of the version. It can come in handy when using other tools, such as [in my case] Convert-WindowsImage

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.

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!

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.

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: