Windows disk health monitoring with smartmontoolsl/NSClient++?

[Anthony Montibello]

If using NC_Net
look at the commands in chec_nc_net.c (nc_net's customized check_nt
compatible client)
check_nc_net --help=WMICAT_NEW
check_nc_net --help=WMICHECK
check_nc_net --help=WMICAT
check_nc_net --help=WMICOUNTER
WMICOunter can use -w and -c

each of these commands need the WMI Query as input and may give the results
back in a format that is easier to manipulate in a wrapper script instead of
a VB script (it depends on expertise and deployment strategy )

example of a input to WMI check/counter for NC_NEt:

check_nc_net -v WMICHECK -l "cimv2^freespace,name^win32_logicaldisk^name=
'c:'' -c 5000000000 -w 10000000000

Tony
(Author of NC_Net)

On Fri, Jan 23, 2009 at 5:04 AM, 44kbps <44kbps at gmail.com> wrote:

> Hi Anthony, I'm working now to get something like this.
> I want to monitor the CPU temperature, fan velocity, and other hardware
> info from a Windows Machine.
> I'm having a look to WMI's Microsoft database.
>
> You can read about it in:
> http://www.microsoft.com/technet/scriptcenter/scripts/default.mspx?mfr=true
>
> Now I'm work to get work with NSCLient++ or NC_NET.
>
> See you!
>
> Anthony Montibello escribió:
>
>> USe WMI:
>> the path to the smart data:
>> root/Cimv2/Win32_DiskDrive/
>> [Instance] --> Status
>>  Hope this helps
>> Tony (Author of NC_Net)
>> On Tue, Jan 13, 2009 at 10:49 PM, Eric Pearce <epearce at amberpoint.com<mailto:
>> epearce at amberpoint.com>> wrote:
>>
>>    I'd like to get SMART disk health status for Windows machines.  It
>>    looks like smartctl would work fine on Windows - has someone got
>>    it working with NSClient++?
>>    I've found some people asking about this in the list archives, but
>>    haven't found any concrete examples.
>>    All I'm looking for is a basic "OK" or "something bad is going to
>>    happen soon" alert from Nagios.
>>    Thanks
>>    -e
>>
>>
>>  ------------------------------------------------------------------------------
>>    This SF.net email is sponsored by:
>>    SourcForge Community
>>    SourceForge wants to tell your story.
>>    http://p.sf.net/sfu/sf-spreadtheword
>>    _______________________________________________
>>    Nagios-users mailing list
>>    Nagios-users at lists.sourceforge.net
>>    <mailto: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
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090123/6852a657/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
-------------- 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