Script Dumpster

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..

Why not make quick and simple posts containing a short description of the problem I was facing at the time, followed by the solution [be it a one-liner, script, function etc.].

So there we have it…

I will try and keep this a bit more up-to-date and will just post snippets or sometimes even work-in-progress, perhaps it’s interesting and it can help you with your own projects.

If anything, it will stimulate me to document my work better 🙂

Without further ado

Here’s the link to my first quick Script Dumpster post, with hopefully more to follow!

Happy scripting! 🙂

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Script dumpster: Get-AutoStartService

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:

Want to directly start up these services? Not a problem!

The Function

I prefer to make my solutions re-usable because well.. I’m lazy.

In case you have the same feeling, here’s the function I’ve created for this with some added functionality.

 

If you have any questions about the function, pieces of code used or perhaps tips [if you have any, please do share!!], let me know and leave a comment.

Happy scripting! 🙂

 

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Lab: Connect to your ServerCore using remoting – step by step

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.

What is the goal and what is required

I think it helps to first define your goals before you start tinkering with a solution, as you might be easily distracted and not reach the goal you had set for yourself.
According to your goals, you note down what steps are required to reach those goals.
Don’t get me wrong, not the immediate script, just the simple text version of what you think you need to do to achieve the goal.

This is especially helpful for me, as I tend to get distracted a LOT!
Think Hammy from Over the Hedge or Dug from UP!

My goal in this case are as follows:

  • Connect to ServerCore using the computername through PSRemoting.

What is required:

  • Add the ServerCore’s computer name to my client’s hosts file
  • Add the ServerCore’s computername to my client’s Trusted Clients settings under WSMAN
  • Connect to ServerCore WSMAN
  • Add the client’s IP address to the ServerCore’s Trusted Clients settings under WSMAN

The code

Client machine Hosts file

Please note: these steps require PowerShell to be run as Administrator.

First of all we want to define some variable which we want to use later on

Of course we want to automate the addition of the ServerCore’s computername to the local hosts file, but in case we’ve already done this, we need to build in a check

To explain: I’m reading the contents of the current Hosts file, located here:  C:\Windows\System32\drivers\etc\hosts .
Just in case you’ve installed Windows in another folder, the script automatically gets the correct location.
It will then check if the Hosts file already contains a line with the ServerCore’s IP address and Name.
If this is not there, it will automatically add this line to the $Hosts variable.
Once this is done it will write the contents of this variable back to the actual file and force it.

Client machine Trusted Hosts

Please note: these steps require PowerShell to be run as Administrator.

Now that you’ve changed the Hosts file, we need to add the ServerCore machine to our WSMAN Trusted Clients.

This will first read out the currently configured Trusted Hosts on your client machine and will then add the ServerCore to this list.
In case you DON’T have any Trusted Hosts configured on your client machine yet it will only add the ServerCore machine.

To check that everything is configured properly [or to check if you have any Trusted Hosts configured on your machine], you can run the following command:

Connect to ServerCore WSMAN

Please note: these steps require PowerShell to be run as Administrator.

While PSRemoting is enabled on Windows Server 2012 R2, it isn’t configured to allow connections from your Client machine.
WSMAN on the other hand is 🙂 .

We can simply create a connection to the machine by using the following commands:

ServerCore machine Trusted Hosts

Please note: these steps require PowerShell to be run as Administrator.

Now comes the tricky part:
We want to automatically get our Client machine’s IP Address and add this to the ServerCore’s Trusted Hosts list.

First we get our Client’s IP Address [requires PowerShell v4 and Windows 8+]:

Now that we have the Client machine’s IP Address, we can add this to the ServerCore’s Trusted Hosts:

Once again we want to check if everything’s properly configured:

The result

Once this is done, you should be able to do the following

Tada!! 🙂

 

Facebooktwittergoogle_plusredditpinterestlinkedinmail