Now that I have my Lab configured and set up to accept remoting from my Client machine, I want to set up a small Hyper-V lab onto this Host.

Since my goal is to manage as much as possible through PowerShell, my current setup will run into the following problem: I can remote into my lab host, but due to single-hop remoting, it is not recommended to daisy chain sessions.

In case you DO want this, you can look at the following articles that will give you more insight on multihop remoting. A small insight on what is required:

The Problem

Today I ran into something simple….but I just wanted to get it solved through PowerShell and make the solution re-usable.

We had found a machine in Active Directory which didn’t turn up in the physical inventory check… And worse of all, the machine was active!

The Script

This script simply checks if machines with a specific name [or in a specific OU] is online at the moment. If it’s online, it will try and figure out who’s actually logged on to the machine.

The Problem

A customer required the inventory of product keys for various products on all network systems. I had used a tool which scanned all machines and nicely produced a .csv file for each machine it had scanned.

Ideally I wanted to have a single .csv file which I could then filter against, either using Excel or PowerShell.

The Function

Check the examples notes on how to use the function.

At my job I tend to have quiet and busy periods, just like everyone else.

At some times I even have very busy periods… like now. Because of that I tend to not have time or motivation to do any blogging, but that doesn’t mean I’m not doing anything productive.

Because of that I thought “why not just share the work I’m creating?”.

An idea was born….

Then it hit me..

The Problem

A frequent issue on servers is when services that are supposed to start simply haven’t started.

There’s a simple one-liner that can show you the services that meet these requirements for you:

The next part in my Lab setup now that I’ve gotten network configured is to actually no longer touch my new Lab machine…

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.