Monitoring windows servers

[Matthew Macdonald-Wallace]

On Tue, 4 Mar 2008 10:54:44 +0000
"Alex Dehaini" <alexdehaini at gmail.com> wrote:

> Hi Guys,
> 
> We have a couple of windows servers. We are monitoring services they
> are running i.e. IMAP, POP, SMTP, PING. I want to monitor CPU, memory,
> Disk-space and any other low level service. What is the best approach?
> 
> Should I install snmp on the windows servers or is there something
> else that I can use.
> 

Hi Alex,

There is a nagios client for windows that we have used very successfully
in the past.

Download the client zip file from http://nsclient.ready2run.nl/ and
extract to a suitable directory.

Copy the Win_2k_XP_bin folder to C:\nagiosAgent

Change to C:\nagiosAgent\ and execute the following to install the
service:

pNSClient.exe /install
net start nsagent

Be aware that if the server is running windows server 2003, you may
need to do the following:

Go to Control Panel -> System -> Advanced -> Settings (the first one
under Performance)

Click on the Data Execution Prevention tab and add pNSclient.exe as a
valid executable (by clicking Add and browsing to it).

Once this is done, point your Nagios config at the client, ensure that
firewalls etc aren't blocking it and have fun!

There's more details on the ready2run site about configuring the system.

Cheers,

M.
-- 
|Matthew Macdonald-Wallace
|Tiger Computing Ltd
|"The Linux Specialists"
|
|Tel: 0845 373 3579
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address: Wyastone Business Park,
| Wyastone Leys, Monmouth, NP25 3SR

-------------------------------------------------------------------------
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/
_______________________________________________
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