It’s really a quick and easy task:

Open a command line and type

Dism /Online /GetTargetEditions

You will get the current installed Windows Edition, in my case ServerStandard

You get a list with available upgrade options with:

dism /online /get-targeteditions

So, to upgrade to Enterprise you have just to type:

dism /online /set-edition:serverenterprise /productkey:<your productkey>

The key I used for the command is a KMS-Key. If you just own MAK’s you have to specify one of your Multiple Activation Key’s of course. I’ve added a link to all KMS-Keys at the end of this post.

After the reboot we can check if the upgrade worked.

Here are some useful links:

Technet Library for DISM
http://technet.microsoft.com/en-us/library/dd744380(WS.10).aspx

KMS Keys
http://technet.microsoft.com/en-us/library/ff793406.aspx

And a more detailed blog post
http://blogs.technet.com/b/server_core/archive/2009/10/14/upgrading-windows-server-2008-r2-without-media.aspx

Just a short PowerShell –Trick which will save you a lot of time

A lot of Cmdlets need the right credentials to perform a action. Especially with W2008R2 and the AD-Cmdlets or with Exchange 2010 this is handy. So you can either type your username/password every time, or just save it to a variable.

$cred = Get-Credential

After hitting Enter a Pop-Up appears where you can enter your credentials. They will be saved within the variable

The input isn’t validated. It’s just saved within the variable for later processing. And don’t worry, the password isn’t saved as clear text

You can also fill the prompt with a username by using “Get-Credential <Username>”. This is maybe helpful when using that in a script.

You can also use this Pop-Up Mechanism directly in a command.

So have fun playing around with PowerShell

May the Shell be with you J

So, let’s start.

First we’ll do the Windows-Part.

Grab a copy of NSClient++ (Thanks a lot to Michael Medin for his great work on this AddOn) at http://nsclient.org/nscp/

I prefer the ZIP-Package and a manually installation. But it doesn’t matter if you want to install the MSI. Just take care that you use the 32 or 64 Bit Version.

1. If you have the ZIP-Package as well, just unpack it and move the files to a folder you like (I use C:\Tools\NSClient++).
2. Open nsc.ini and make the following changes:
   1. Line 14: Uncomment NRPEListener.dll
   2. Line 117: allow_arguments=1
   3. Line 121: allow_nasty_meta_chars=1
   4. Line 125: use_ssl=1
   5. Line 135: allowed_hosts=<IP of your Icinga/Nagios Host>

   Explanation: You need allow_arguments and the nasty_meta_chars for Performance Counters, because we need the Backslash to specify them.
   use_ssl and allowed_hosts is just for security reasons, but I suggest to use them
   

3. Start a command prompt and navigate to the directory where you’ve unpacked your NSClient++ Files (make sure you’re running the command prompt as Administrator)
4. Test if NSClient++ is working => “NSClient++.exe” /test
   
   

   If the output looks good (if no error is displayed) exit the Test-Mode with, tada => Exit
   

   This Test-Mode is really handy if a query on the Monitoring-Host doesn’t return the result you expect. Just fire up the Test-Mode and run the query again.
   

5. Now it’s almost done. Just install the service and start it.
   1. “NSClient++.exe” –install
   2. net start nsclientpp
      
      
6. That’s it, the Windows-Part is done ?

So, now it’s time for the Linux-Tasks.

We need the check_nrpe Plugin. You can either install it with aptitude (aptitude install nagios-nrpe-plugin) or grap a copy of the NRPE source at: http://www.nagios.org/download/addons

Again, I’m a fan of compiling such stuff myself. So let’s do it.

1. Unpack the archive => tar –xzf nrpe-2.12.tar.gz
2. Run the configure-command. Just make sure to include the “—enable-command-args” option => ./configure –enable-command-args –enable-ssl
   Again, –enable-ssl isn’t necessary, but a recommendation. Futhermore maybe it’s necessary to add some other config-switches to fit your environment.
3. Compile the package => make
4. It’s not necessary to install the package, we just the the check_nrpe binary from the ./src directory.
5. Copy the check_nrpe binary to your libexec dir of Nagios or Icinga => cp src/check_nrpe /usr/local/icinga/libexec/

Last but not least, the Nagios/Icinga Config

First, we’ll create a new command for checking Performance Counters

1. Edit your commands.cfg (by default in /usr/local/icinga/etc/objects/commands.cfg) => sudo vim /usr/local/icinga/etc/objects/commands.cfg
   
   
   
   Again, this is just a recommendation. But I prefer a “generic” command and put the detailed definition into services.
2. Now add a new service (by default in /usr/local/icinga/etc/objects/services.cfg) => sudo vim /usr/local/icinga/etc/objects/services.cfg
   You must use double Backslashes for the Counters
   
   
3. How to get the name of a Performance Counter?

   Use the Windows Performance Monitor (Start -> Run -> perfmon) and add the counters you want to monitor. After that switch to the properties of your current Performance Monitor Session (Action -> Properties or Right Click to the Graphs -> Properties). At the Data-Tab you’ll find the right name. Just make sure to use double Backslashes in your Icinga/Nagios Config.
   
   

4. Save both files ( :wq ) , check the config and reload Icinga
   1. sudo /etc/init.d/icinga checkconfig
   2. sudo /etc/init.d/icinga reload
5. Look at the results of the check in the Web Interface (I’m sure you’re already running Icinga-Web, or not?
   

Some troubleshooting tips:

1. Before adding a service, run the check on the Linux command line.
   
2. Of you do not get the result you expect with the “remote run” (see above) try to run the check locally on the Windows Machine.
   1. Start NSClient++ in Test-Mode; You can do that while the service is running. You’ll get an error that no socket can be bind, but it’s ok => “NSClient++.exe” /test
   2. Run the check without double Backslashes (they are just necessary for the remote execution)

      
      

Hope this post is helpful for you. If you miss something, or if some steps are not clearly enough just let me know.

Good luck and happy monitoring ?