#Paste into uxterm ubuntu license#
#Paste into uxterm ubuntu free#

However, I doubt Microsoft would be jumping through any hoops to support a CentOS guest running Nagios either, so I donвЂ™t think this is a major concern.

Ubuntu is based on Debian, and Debian is not on the official supported distribution list for Hyper-V, so I suppose thereвЂ™s a bit of caveat emptor here. 12.10 might be workable, but 12.04 will have support from Canonical until 2017 (thatвЂ™s what LTS means), so you can count on regular security updates, etc. Also, power commands donвЂ™t work correctly shut down and restart both leave it at a black screen and you need to force it off. The video performance is unbearable and the tweaks IвЂ™ve found havenвЂ™t helped enough in my opinion. 13.04 runs perfectly miserably as a Hyper-V Server 2012 guest. There are two newer versions, 12.10 and 13.04. I have chosen the desktop version of CanonicalвЂ™s Ubuntu 12.04 LTS (long-term support) for my Nagios system. If you have Linux knowledge and prefer to use another distribution, go ahead and get it set up and skip down to the Nagios setup directions later in this article. Installing Ubuntu 12.04 LTS as a Hyper-V Virtual Machine This post will illustrate Ubuntu 12.04 LTS, whose hardware requirements are very slim. Hardware requirements are minimal, depending on the distribution that you choose.

#Paste into uxterm ubuntu free#

If youвЂ™re going to be using a Linux distribution, feel free to use any hardware youвЂ™ve got available, even an old desktop that was planned for the recyclers. The instructions in this post will cover doing so and will make it easy even for non-Linux people to do. Instead, I recommend using a Linux distribution.

#Paste into uxterm ubuntu license#

Nagios should be the only thing on its system and thereвЂ™s really no call to soak up a Windows license for what it does.

I have no idea how up-to-date it is in comparison to the main branch and I donвЂ™t recommend that it be used. Nagios Core has been forked into a Windows version.

If youвЂ™ve only got one system running Hyper-V, I would recommend that you use one virtual installation and one physical installation. Since my test lab has three physical systems, two running Hyper-V Server and one running Windows Server, I can have two virtualized Nagios installations. Personally, I prefer to have Nagios run inside a virtual machine for a variety of reasons. Preferably, youвЂ™ll have at least two Nagios systems one to monitor your systems and one to monitor the other Nagios server. This blog post will walk you through setting up Nagios Core and configuring basic monitoring to monitor Hyper-V. Therein lies the rub with the free version: itвЂ™s not the easiest thing in the world to set up. It does come in a commercial version which adds a lot features, mostly in the user-friendliness department. It is easily one of the most powerful systems you can get your hands on, and you just canвЂ™t beat the price (free). There are a huge number of monitoring tools that work with Hyper-V on the market today. System monitoring is one of the more important things we can do for our datacenters, as it helps to spot problems in the onset phase where they can be dealt with gracefully instead of waiting for an obvious failure that requires downtime.