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.

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. Especially when you’re used to one specific editor, switching to another one might not be as easy as you’d like.

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: