How to Add Windows Host to Nagios Monitoring Server

This article describes how to monitor Windows machines “private” services such as CPU load, Disk usage, Memory usage, Services, etc. For this, we required to install an NSClient++ addon on the Windows machine. The addon acts a proxy between the Windows machine and Nagios and monitors actual services by communicating with the check_nt plugin. The check_nt plugin already installed on the Nagios Monitoring Server, if you followed our Nagios installation guide.

We assume that you’ve already installed and configured Nagios server according to our following guides.

  1. How to Install Nagios 4.0.1 on RHEL/CentOS 6.x/5.x and Fedora 19/18/17
  2. Add Linux Host to Nagios Monitoring Server

To monitor Windows Machines you will need to follow several steps and they are:

  1. Install NSClient++ addon on the Windows Machine.
  2. Configure Nagios Server for monitoring Windows Machine.
  3. Add new host and service definitions for Windows machine monitoring.
  4. Restart the Nagios Service.

To make this guide simple and easier, a few of configuration already done for you in the Nagios installation.

  1. A check_nt command definition already added to the command.cfg file. This definition command is used by check_nt plugin to monitor Windows services.
  2. A windows-server host template already created in the templates.cfg file. This template allows you to add new Windows host definitions.

The above two files “command.cfg” and “templates.cfg” files can be found at /usr/local/nagios/etc/objects/ directory. You can modify and add your own definitions that suits your requirement. But, I’d recommend you to follow the instructions described in this article and you will be successfully monitoring your windows host in less than 20 minutes.

Step 1: Installing NSClient++ Agent on Windows Machine

Please use the below instructions to install NSClient++ Agent on the Remote Windows Host. First download the latest stable version NSClient++ 0.3.1 addon source files, which can be found at below link.

  1. http://sourceforge.net/projects/nscplus/

Once you’ve downloaded latest stable version, unzip the NSClient++ files into a new C:\NSClient++ directory.

Now open a MS-DOS command prompt from the Start Screen –> Run –> type ‘cmd‘ and press enter and change to the C:\NSClient++ directory.

C:\NSClient++

Next, register the NSClient++ service on the system with the following command.

nsclient++ /install

Finally, install the NSClient++ systray with the following command.

nsclient++ SysTray

Open the Windows Services Manager and right click on NSClient go to Properties and then ‘Log On‘ tab and click the check box that says “Allow service to interact with the desktop“. If it isn’t already allowed, please check the box to allow it to.

Install NSClient++

Install NSClient++

Open NSC.INI file located at C:\NSClient++ directory and uncomment all the modules defined in the “modules” section, except for CheckWMI.dll and RemoteConfiguration.dll.

[modules]
;# NSCLIENT++ MODULES
;# A list with DLLs to load at startup.
;  You will need to enable some of these for NSClient++ to work.
; ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
; *                                                               *
; * N O T I C E ! ! ! - Y O U   H A V E   T O   E D I T   T H I S *
; *                                                               *
; ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
FileLogger.dll
CheckSystem.dll
CheckDisk.dll
NSClientListener.dll
NRPEListener.dll
SysTray.dll
CheckEventLog.dll
CheckHelpers.dll
;CheckWMI.dll
;
; RemoteConfiguration IS AN EXTREM EARLY IDEA SO DONT USE FOR PRODUCTION ENVIROMNEMTS!
;RemoteConfiguration.dll
; NSCA Agent is a new beta module use with care!
;NSCAAgent.dll
; LUA script module used to write your own "check deamon" (sort of) early beta.
;LUAScript.dll
; Script to check external scripts and/or internal aliases, early beta.
;CheckExternalScripts.dll
; Check other hosts through NRPE extreme beta and probably a bit dangerous! :)
;NRPEClient.dll

Uncomment the “allowed_hosts” in the “Settings” section and define the IP address of your Nagios Monitoring Server or leave it blank to allow any hosts to connect.

[Settings]
;# ALLOWED HOST ADDRESSES
;  This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
;  If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
;  The syntax is host or ip/mask so 192.168.0.0/24 will allow anyone on that subnet access
allowed_hosts=172.16.27.41

Uncomment the “port” in the “NSClient” section and set to default port ‘12489‘. Make sure to open ‘12489‘ port on Windows Firewall.

[NSClient]
;# NSCLIENT PORT NUMBER
;  This is the port the NSClientListener.dll will listen to.
port=12489

Finally start the NSClient++ service with the following command.

nsclient++ /start

If your properly installed and configured, you should see a new icon in the system tray in yellow circle with a black ‘M‘ inside.

Step 2: Configuring Nagios Server and Add Windows Hosts

Now Login into Nagios Server and add some object definitions in Nagios configuration files to monitor new Windows machine. Open windows.cfg file for editing with Vi editor.

[[email protected]]# vi /usr/local/nagios/etc/objects/windows.cfg

A sample Windows host definition already defined for the Windows machine, you can simply change the host definition like host_name, alias, and address fields to appropriate values of your Windows machine.

###############################################################################
###############################################################################
#
# HOST DEFINITIONS
#
###############################################################################
###############################################################################

# Define a host for the Windows machine we'll be monitoring
# Change the host_name, alias, and address to fit your situation

define host{
        use             windows-server  ; Inherit default values from a template
        host_name       winserver       ; The name we're giving to this host
        alias           My Windows Server       ; A longer name associated with the host
        address         172.31.41.53    ; IP address of the host
        }

Following services are already added and enabled in windows.cfg file. If you wish to add some more other service definitions that needs to be monitored, you can simple add those definitions to same configuration file. Make sure to change the host_name for these all services with host_name defined in the above step.

define service{
	use			generic-service
	host_name		winserver
	service_description	NSClient++ Version
	check_command		check_nt!CLIENTVERSION
	}

Add the following service definition to monitor the uptime of the Windows server.

define service{
	use			generic-service
	host_name		winserver
	service_description	Uptime
	check_command		check_nt!UPTIME
	}

Add the following service definition to monitor the CPU utilization on the Windows server and generate a CRITICAL alert if the 5-minute CPU load is 90% or more or a WARNING alert if the 5-minute load is 80% or greater.

define service{
	use			generic-service
	host_name		winserver
	service_description	CPU Load
	check_command		check_nt!CPULOAD!-l 5,80,90
	}

Add the following service definition to monitor memory usage on the Windows server and generate a CRITICAL alert if memory usage is 90% or more or a WARNING alert if memory usage is 80% or greater.

define service{
	use			generic-service
	host_name		winserver
	service_description	Memory Usage
	check_command		check_nt!MEMUSE!-w 80 -c 90
	}

Add the following service definition to monitor usage of the C:\ drive on the Windows server and generate a CRITICAL alert if disk usage is 90% or more or a WARNING alert if disk usage is 80% or greater.

define service{
	use			generic-service
	host_name		winserver
	service_description	C:\ Drive Space
	check_command		check_nt!USEDDISKSPACE!-l c -w 80 -c 90
	}

Add the following service definition to monitor the W3SVC service state on the Windows machine and generate a CRITICAL alert if the service is stopped.

define service{
	use			generic-service
	host_name		winserver
	service_description	W3SVC
	check_command		check_nt!SERVICESTATE!-d SHOWALL -l W3SVC
	}

Add the following service definition to monitor the Explorer.exe process on the Windows machine and generate a CRITICAL alert if the process is not running.

define service{
	use			generic-service
	host_name		winserver
	service_description	Explorer
	check_command		check_nt!PROCSTATE!-d SHOWALL -l Explorer.exe
	}

Lastly, uncomment the windows.cfg file in /usr/local/nagios/etc/nagios.cfg.

[[email protected]]# vi /usr/local/nagios/etc/nagios.cfg
# Definitions for monitoring a Windows machine
cfg_file=/usr/local/nagios/etc/objects/windows.cfg

Finally, verify the Nagios configuration files for any erros.

[[email protected]]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
Total Warnings: 0
Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check

If the verification process throws any error messages, fix those errors until the verification process completes without any error messages. Once’ you fix those errors, restart the Nagios service.

[[email protected]]# service nagios restart

Running configuration check...done.
Stopping nagios: done.
Starting nagios: done.

That’s it. Now go to Nagios Monitoring Web interface at “http://Your-server-IP-address/nagios” or “http://FQDN/nagios” and Provide the username “nagiosadmin” and password. Check that the Remote Windows Host was added and is being monitored.

Nagios Monitor Windows Host

Nagios Monitor Windows Host

That’s it! for now, in my up-coming article I will show you how to add Printer and Switches to Nagios Monitoring Server. If you’re having any difficulties while adding Windows host to Nagios. Please do comment your queries via comment section, till then stay tuned to Tecmint.com for more such kind of valuable articles.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

Support Us

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. A Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

103 Responses

  1. Vikram says:

    Hello,

    Could you please guide me how do i add multiple windows servers on nagios?

    Regards,
    Vikram

    • Ravi Saive says:

      @Vikram,
      I think same instructions will work with minor changes..I mean you can create separate file like windows.cfg, here you can define all your Windows machines IP address with proper settings and in services.cfg file define check commands for services..

  2. sanjay says:

    Hi Ravi,
    I would like to monitor the tomcat based application so please suggest how to install tomcat plugins on centos through command line

  3. Sam Smith says:

    Hello Ravi Saive,

    I add Window host “Window Server 2008″. when run isn’t working and alert status information “add alert message could not fetch information from server”. Can you give me the way how to fix it, please?

    Thanks you in advance,
    Sam Smith

  4. shoeb says:

    Hi Ravi ,

    I’m using nagios 4 and need to monitor remote window hosts as well local hosts, nagios fetching local hosts data perfectly but could not fetch for remote,could you please let me know what should be checked at nagios server and lInux firewall .Nagios server is behind shorewall firewall .
    Thanks

    • Ravi Saive says:

      @Shoeb,
      Have you opened port 5666 on remote host firewall? is you added Nagios Monitoring IP in remote hosts nrpe.cfg file under xinetd?

  5. Hi Ravi,

    How to remove hosts from Nagios server. Please help me.

    Regards,
    V Venkateswarlu

    • Ravi Saive says:

      @Venkat,
      Just remove the whatever entries you’ve added for the host in hosts.cfg and services.cfg file, and restart the nagios to take new changes..

  6. Steve says:

    Hello Ravi,
    I have added host “Window Server 2008R2”. After “add alert message could not fetch information from server”. So, please help to solve this…
    Thanks in Advance,

  7. Jonus Joseph says:

    Hello Ravi,

    I am monitoring 20,000 windows server using NSclint++ 3.x in Nagios but usually on most of the windows servers i am getting this kind of alerts (“No data was received from host!”) for CPU and Memory service check , some time this alert will recover automatically and some time it is not, I guess this is false alert.

    Will you please advice me the best method/solution to fix this issue and alert ?

    Thanks is advance.

    Regards,
    Jonus Joseph

    • Ravi Saive says:

      @Jonus,
      It seems something related to network issue..the Nagios server didn’t received any data from host..

      • Jonus Joseph says:

        Hello Ravi,

        I got the solution for this issue on same day
        we need to increase the timout value in check_nt. command,
        I have done the same and issue is resolved now.

        -Jonus Joseph

  8. Asriel Rusdyawan says:

    I think you forgot to create a configuration to windows template so then the host can refer to the template to execute some commands. CMIIW.

  9. Steve says:

    Hi,
    after i configure this, i have found issue below. How to fix it? Please help to support this. thanks

    Drive Space
    CRITICAL 11-22-2014 22:01:40 0d 11h 49m 8s 3/3 (Return code of 127 is out of bounds – plugin may be missing)

    CPU Load
    CRITICAL 11-22-2014 22:02:41 0d 11h 48m 9s 3/3 (Return code of 127 is out of bounds – plugin may be missing)

    Explorer
    CRITICAL 11-22-2014 22:03:38 0d 11h 47m 11s3/3 (Return code of 127 is out of bounds – plugin may be missing)

    Memory Usage
    CRITICAL 11-22-2014 22:04:36 0d 11h 46m 12s3/3 (Return code of 127 is out of bounds – plugin may be missing)

    NSClient++ Version
    CRITICAL 11-22-2014 22:05:36 0d 11h 45m 13s 3/3 (Return code of 127 is out of bounds – plugin may be missing)

    Uptime
    CRITICAL 11-22-2014 22:06:33 0d 11h 44m 15s 3/3 (Return code of 127 is out of bounds – plugin may be missing)

    W3SVC
    CRITICAL 11-22-2014 21:57:33 0d 11h 43m 16s 3/3 (Return code of 127 is out of bounds – plugin may be missing)

    • Ravi Saive says:

      @Steve,
      Most likely due to file permissions, make sure your plugin directory “/usr/local/nagios/libexec” owned by Nagios user and have proper permissions to execute.

      • Steve says:

        @Ravi Saive,

        The first I, wanna to say thanks you for your reply… and the second I have follow your guide step by step but when I check in “/usr/local/nagios/libexec” show below:

        [[email protected] libexec]# ll
        total 6988
        -rwxr-xr-x. 1 nagios nagios 179258 Nov 21 18:19 check_apt
        -rwxr-xr-x. 1 nagios nagios 2252 Nov 21 18:19 check_breeze
        -rwxr-xr-x. 1 nagios nagios 179683 Nov 21 18:19 check_by_ssh
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_clamd -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 137005 Nov 21 18:19 check_cluster
        -r-sr-xr-x. 1 root nagios 175282 Nov 21 18:19 check_dhcp
        -rwxr-xr-x. 1 nagios nagios 174413 Nov 21 18:19 check_dig
        -rwxr-xr-x. 1 nagios nagios 193388 Nov 21 18:19 check_disk
        -rwxr-xr-x. 1 nagios nagios 9290 Nov 21 18:19 check_disk_smb
        -rwxr-xr-x. 1 nagios nagios 189067 Nov 21 18:19 check_dns
        -rwxr-xr-x. 1 nagios nagios 85051 Nov 21 18:19 check_dummy
        -rwxr-xr-x. 1 nagios nagios 3350 Nov 21 18:19 check_file_age
        -rwxr-xr-x. 1 nagios nagios 6316 Nov 21 18:19 check_flexlm
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_ftp -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 175384 Nov 21 18:19 check_hpjd
        -rwxr-xr-x. 1 nagios nagios 335868 Nov 21 18:19 check_http
        -r-sr-xr-x. 1 root nagios 181947 Nov 21 18:19 check_icmp
        -rwxr-xr-x. 1 nagios nagios 146131 Nov 21 18:19 check_ide_smart
        -rwxr-xr-x. 1 nagios nagios 15124 Nov 21 18:19 check_ifoperstatus
        -rwxr-xr-x. 1 nagios nagios 12601 Nov 21 18:19 check_ifstatus
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_imap -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 6888 Nov 21 18:19 check_ircd
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_jabber -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 157666 Nov 21 18:19 check_ldap
        lrwxrwxrwx. 1 root root 10 Nov 21 18:19 check_ldaps -> check_ldap
        -rwxr-xr-x. 1 nagios nagios 158068 Nov 21 18:19 check_load
        -rwxr-xr-x. 1 nagios nagios 5989 Nov 21 18:19 check_log
        -rwxr-xr-x. 1 nagios nagios 21481 Nov 21 18:19 check_mailq
        -rwxr-xr-x. 1 nagios nagios 144237 Nov 21 18:19 check_mrtg
        -rwxr-xr-x. 1 nagios nagios 145290 Nov 21 18:19 check_mrtgtraf
        -rwxr-xr-x. 1 nagios nagios 190840 Nov 21 18:19 check_mysql
        -rwxr-xr-x. 1 nagios nagios 175310 Nov 21 18:19 check_mysql_query
        -rwxr-xr-x. 1 nagios nagios 157374 Nov 21 18:19 check_nagios
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_nntp -> check_tcp
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_nntps -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 179778 Nov 21 18:19 check_nt
        -rwxr-xr-x. 1 nagios nagios 184113 Nov 21 18:19 check_ntp
        -rwxr-xr-x. 1 nagios nagios 173118 Nov 21 18:19 check_ntp_peer
        -rwxr-xr-x. 1 nagios nagios 171363 Nov 21 18:19 check_ntp_time
        -rwxr-xr-x. 1 nagios nagios 212335 Nov 21 18:19 check_nwstat
        -rwxr-xr-x. 1 nagios nagios 8779 Nov 21 18:19 check_oracle
        -rwxr-xr-x. 1 nagios nagios 160109 Nov 21 18:19 check_overcr
        -rwxr-xr-x. 1 nagios nagios 164211 Nov 21 18:19 check_pgsql
        -rwxr-xr-x. 1 nagios nagios 183658 Nov 21 18:19 check_ping
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_pop -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 186937 Nov 21 18:19 check_procs
        -rwxr-xr-x. 1 nagios nagios 157567 Nov 21 18:19 check_real
        -rwxr-xr-x. 1 nagios nagios 9582 Nov 21 18:19 check_rpc
        -rwxr-xr-x. 1 nagios nagios 1453 Nov 21 18:19 check_sensors
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_simap -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 247834 Nov 21 18:19 check_smtp
        -rwxr-xr-x. 1 nagios nagios 251233 Nov 21 18:19 check_snmp
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_spop -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 155395 Nov 21 18:19 check_ssh
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_ssmtp -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 141073 Nov 21 18:19 check_swap
        -rwxr-xr-x. 1 nagios nagios 230757 Nov 21 18:19 check_tcp
        -rwxr-xr-x. 1 nagios nagios 156545 Nov 21 18:19 check_time
        lrwxrwxrwx. 1 root root 9 Nov 21 18:19 check_udp -> check_tcp
        -rwxr-xr-x. 1 nagios nagios 168557 Nov 21 18:19 check_ups
        -rwxr-xr-x. 1 nagios nagios 137947 Nov 21 18:19 check_uptime
        -rwxr-xr-x. 1 nagios nagios 136097 Nov 21 18:19 check_users
        -rwxr-xr-x. 1 nagios nagios 2937 Nov 21 18:19 check_wave
        -rwxr-xr-x. 1 nagios nagios 131526 Nov 21 18:19 negate
        -rwxr-xr-x. 1 nagios nagios 125772 Nov 21 18:19 urlize
        -rwxr-xr-x. 1 nagios nagios 1895 Nov 21 18:19 utils.pm
        -rwxr-xr-x. 1 nagios nagios 2791 Nov 21 18:19 utils.sh
        [[email protected] libexec]#

        So, How to check plugin directory and permission of user allow or not?
        Please help me to solve it. Thanks you!

        • Ravi Saive says:

          @Steve,
          I see the in the plugin directory “/usr/local/nagios/libexec” some of the files are owned by root user. so that means that the nagios user don’t have proper permissions to execute those files, better assign those files to nagios using following command.

          chown -R nagios:nagios /usr/local/nagios/libexec
          
  10. Rohit says:

    Windows client has been added but all services in services tab shows critical

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.