New Plugins for Windows systems

[Sauter, Thorsten]

Hello nagios users,

I have writte some checkripts to monitor windows systems. I think some
of these scripts could be helpful for other Nagios users too. For this
readon I have published my scripts on sourceforge.org
[http://sourceforge.net/projects/nagiosplugincol/].

All scripts are written in Python 2.5 and using the Python Win32-API or
the Microsoft WMI interface. No external commands are required /needs to
be parsed at the moment. All scripts are published under the terms of
the GPL. The download area contains precompiled binaries for Windows 32
bit systems. These binaries can simply used the NRPE, NC_Net or any
other Nagios remote client.

At the moment, the following monitoring scripts are available:

    * check_groupshield
      Checks the update status of the engine, the dat version and the
antispam engine/dat files of the McAfee GroupShield 6.x for Exchange
200x.

    * check_ipconfig
      Make sure all required ip addresses and correct subnet masks are
configured on the correct interface

    * check_mscluster
      This script can check the normal healthy status of a Microsoft(TM)
Windows cluster. It can also check the status of several resource or
groups.

    * check_netshares
      Make sure, the machine offerts all requested NetBios shares. This
script does not validate the ACL permissions yet.

    * check_onlineupdates/inspect_onlineupdates
      The inspect_onlineupdates script search for new available Windows
online updates and store them into a database. (Run this script from
task scheduler regularly). The corresponding check script evaluate the
database and alert if updates are pending or a reboot is required.

    * check_perfcounter
      To monitor performance counters on a machine this script can be
used. It query the specified performance counter and alter if a value is
too high.

    * check_printers
      Check the status of all printers on a Windows printserver. Can
alert if a printer has a non-healthy state or if the queue contains too
much print jobs.

    * check_processes
      Alerts if a process is not running, too much process, too little
processes and so on. The syntax of the tests is stolen from the Unix
test(1) command.

    * check_service
      Make sure all automatic services are running. Or if special
services are specified, this script checks if they are running.

    * check_shadowcopy
      Count the created snapshots of a volume and alters if not enough
snapshots are created; or if the last created snapshot is too old.

    * check_taskscheduler
      Reports errors if a scheduled task has not been started yet, or
the task returns wich an non-success value.

    * check_tcp
      This is a simple clone of the check_tcp script from the Nagios
plugin package which runs under windows which a compiler. Not all
options are supported yet.

    * check_uptime
      Make sure the system is not in safe-mode. Alerts if the uptime is
lower then a specified time and if the system was rebooted unexepectedly
(system log).

    * check_virusscan
      This is the counter part of the check_groupshield script, but I
checks the update status of a McAfee AntiVirus 8.5i installation:
Engine, Dat.

    * check_quota (unfinished)

Feedback, bugreports or patches are always welcome of course.

Regards,
Thorsten Sauter



Geschäftsführer/Managing Directors: Christoph Hahn-Woernle, Peter W. Hälsig, Frank Apel
HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart)
St.-Nr. 99064/06051, USt-IdNr./VAT-idNo: DE 203036780

-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null