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:

I’ve noticed over the last week that I’ve been doing various remoting commands through Invoke-Command to the same machines, which require additional credentials to access.

Why re-type something when you can automate it 🙂

Before

I used to have to do the following:

$SCCMServers = 'CM01.contoso.com','CM02.contoso.com','CM03.contoso.com','CM04.contoso.com'

$cred_SCCM = Import-CliXml $CredStore\contoso.xml

Invoke-Command -ComputerName $SCCMServers -Credential $cred_SCCM -Scriptblock {whatever needed to be done}

Where my SCCM servers are in another forest as my management machine and $CredStore is my personal Credential folder which contains credentials for various systems/domains, as I use these regularly and I’m lazy

As I had mentioned in my previous post, I gave a presentation last week at the Dutch PowerShell UserGroup [DuPSUG] about PowerShell Remoting.

It was my first time presenting in front of a crowd [approximately 55] which weren’t my colleagues [and even there at max like 10-15 people] or a handful of customers, so to say the least I was quite anxious.

Thanks to some great tips by Jeff Wouters and Ben Gelens I made it through and when clicking to the second slide I went into automatic pilot mode 🙂

Along with  Mark van de Waarsenburg,  Erik Heeres, Erik van der Plas and Danny den Braver we’ll be trying to spread the gospel of PowerShell amongst the interested people 🙂

My seminar will be focused on PowerShell Remoting - Practice & Theory and will feature a few labs along the way. I expect to post a few of the components, along with slide deck and scripts used on the site

While that might sound strange at first, the reason for this is simple. My Lab should be a headless server, stuffed in a cabinet somewhere with power and a network connection and I should be able to do ALL my management tasks remotely.

This should be a simple task you’d say, but for the sake of clarity [and to learn this process better myself] I have decided to write down all the steps required to do this.

I’m loving the way Microsoft is currently pushing PowerShell as THE go-to tool required to manage all your solutions.

I’m at a loss however at why they aren’t providing out of the box solutions so that you can manage all of your workstations/servers through PowerShell. Sure, you can head over to every machine and configure PowerShell using

Enable-PSRemoting

However I can understand that people have better things to do with their time [I sure do!]