Nagios is an open-source program that allows you to monitor the status of a computer network. Using Nagios, you can watch the activities on your network in real time.

Bringing the power of Linux to a landscape such as Windows is a complex, but often requested, task. There are several solutions and not many of them are well suited to the task of monitoring. VMware player and Qemu are sometimes slow, while Cygwin is perhaps too limited to run all of Nagios. To solve the problem, we thought we'd bring the power of Nagios to Windows.

With this Native Windows Installer anyone can setup a usable and effective Nagios install under Windows. This installer makes use of system level drivers () and installs as a service. Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises. All other servicemarks and trademarks are the property of their respective owner. The files and information on this site are the property of their respective owner(s). Nagios Enterprises makes no claims or warranties as to the fitness of any file or information on this website, for any purpose whatsoever. In fact, we officially.

We do, however, think these community contributions are pretty damn cool. Website Copyright © 2009-2017 Nagios Enterprises, LLC.

All rights reserved.

• - Mon, Aug 26 2013 • - Mon, Sep 24 2012 • - Fri, Jul 13 2012 Nagios is one of the most popular Open Source IT infrastructure monitoring tools available. Originally developed to monitor network hosts for uptime, latency, and health, Nagios has been extended to perform a variety of functions through its plugin interface. Though it is Open Source and generally intended for the Linux crowd, the folks at IteF!x have developed a port of Nagios for Windows - or - to allow a Windows host to run the Nagios process. Nagwin - A complete Nagios implementation for Windows Installing Nagwin Nagwin uses several packages to acheive Nagios functionality on Windows, including lightweight versions of Cygwin (a Linux API for Windows), PHP, Perl, Blat (SMTP server), and Nginx (web server). Thankfully all of these are included in the download for Nagwin at SourceForge. Once you download the installer, unzip and run the resultant Nagwin_1.2.0_Installer executable to get started.

During the installation, you will be prompted for where you want to put the “ICW” folder (the cygwin root). I like to put this directly on the hard drive so it is easy to get to “C: ICW,” but this is a matter of personal taste. Next, you will be prompted to enter a service account name and password.

Accepting the defaults here is fine unless you would rather use an existing service account. The password that is prepopulated is randomly generated and if you accept defaults you should save this password somewhere safe. Click “Install” to proceed. Configuring the Nagios process Assuming you want Nagios to start automatically when your server starts, you should run the MMC console “services.msc” and scroll down to where all of the Nagwin services are. By default, these are manual startup services. If you go to Properties for each service you can configure them for an automatic startup. If they are running already, go ahead and stop them.

By default, the Nagios admin account (nagiosadmin) has the password “nagios” and that will not do, so let’s go ahead and change it. In a command prompt window, navigate to the ICW directory that you chose in the installation, then navigate to the “bin” folder. Now, run the command, replacing the italicized bit with your desired password.

Htpasswd2 -b / etc / nginx / htpasswd nagiosadmin your_password_here You can create additional accounts but that’s what we will use for now. You can also change the port that is used to access the web management interface. By default, this is port 80, but you will probably want to change it to a lesser known (and less likely to conflict) port. I chose port 81 but you can choose any TCP port that is not already in use. To do so, navigate to the folder “ etc nginx nginx.conf” under the ICW directory and find the “server” block. Now change the “listen” directive from 80 to whatever you desire.

Configuring Nagios to monitor a host Now the real work begins. Let’s assume that our Nagios server is located at 10.1.1.14 in a 10.1.1.0/24 subnet, and that we want to monitor another Windows host located at 10.1.1.10 (called “fileserver”) on the same subnet. To monitor the host we simply define a new host in the file “ etc nagios nagwin hosts.cfg” and restart (or start) the Nagios process.

First, open the hosts.cfg file in your favorite text editor (if it does not exist, create the hosts.cfg file in the “ etc nagios nagwin” directory). Using our example above, the host configuration is as follows. Hi; I've managed to add the 'jmxeval.bat' for the jmx checks.

But I am getting an exception when I run the plugin 'check_jmxeval.bat', I've copied the cmd output below. C: Nagwin_x64 plugins>check_jmxeval.bat C: Nagwin_x64 etc jmxeval-threadcount.xm l Exception in thread 'main' java.lang.ClassCastException: com.adahas.tools.jmxeva l.model.impl.Eval cannot be cast to com.adahas.tools.jmxeval.model.impl.JMXEval at com.adahas.tools.jmxeval.App.execute(App.java:50) at com.adahas.tools.jmxeval.App.main(App.java:110) If there is a better way to add the jmx checks to Nagwin please share. Thanks and regards. I allowed my laptop to update to 1709. My laptop's graphics are onboard Intel HD4000, with which I have two external LG monitors, using either Windows10 or Displayfusion to configure the settings. After the update to 1709, Windows 10 no longer allowed the Intel HD4000 drivers, and overwrote them with the generic Windows one, with the result that Windows does not recogneise the other monitors at all.

I contacted Intel, who could only refer me to the latest drivers for IntelHD4000, which still didn't work. MI contacted the manufactruere of the laptop (Proline) who advised they no longer support the machine. I tried to roll back to 1603, using the control panel etc, but the rollback failed and just sat there for 36 hours.

I had to get to the uninstall update functionality via the inistial Windows startup screen/power/advanced route, which gave me back version 1603, and my double monitor functionality. I disabled the Windows update via my registry, so I am safe from the 1709 update, but cannot update the Office updates (I am alerted to the updates, tell it to go ahead, but then nothing). So, sooner or later I will have to buy a new machine. You can still learn about the details when using VMM.

It is a common misconception that you learn more when you work on a console. Copying and pasting some commands from the web is just the same as clicking an icon in a GUI. If you don't try to understand what the command does in the background, you won't learn anything. VMM is an essential component of Microsoft's virtualization solution. If you don't know how to use VMM, you don't really know to manage server virtualization with Microsoft. Marilyn Manson Long Hard Road Out Of Hell Ebookers on this page.

It is like if you only use ESXi without vCenter, you can't really say you know VMware.