Remote windows monitoring

[gds]

This has probably been asked, and i've tried searching...

Just after some advice on how to complete the following.

We are just testing the trial version.

At present we would like to monitor a remote windows server in another office, which we have working by opening ports 5666 12489 etc no issue.
Question from here we would like to then monitor 15 windows workstations, roaming laptops.

What is the best way to achieve this? do we setup the windows server client as a poller so all internal devices report back to it then send to our nagios server, or passive checks on the workstations which then log back to port 5666?

I guess we are trying to do what labtech etc does with probes

[slansing]

Well you could set up a relay like that by pushing results from the systems to a central server which has NSClient++ on it in with the server module enabled, then push that to Nagios. You could also set up an XI or core server in that environment, then have it forward results up to the main XI server, that is another common way this is done. If you choose one of those, or would like to do neither, let us know, and we can get you more details.

[gds]

Well you could set up a relay like that by pushing results from the systems to a central server which has NSClient++ on it in with the server module enabled, then push that to Nagios.

Thanks for your reply, i guess this is what we would be looking at.

Guessing we change the NSclient on the workstations to reference the NSclient IP instead of nagios server. Lets say one of the workstations leaves the office is there a way we can have it poll back to the nagios server which is remote?


If you could provide links to some guides would be great.

Or should we be looking at NCPA for example to do this?
http://assets.nagios.com/downloads/ncpa ... g_NCPA.pdf

[slansing]

I'm currently looking through the NSclient++ documentation trying to piece together a guide for you, what I have found so far is:

http://docs.nsclient.org/reference/NRPE ... gs/default
http://docs.nsclient.org/reference/NSCl ... gs/default

Which is what I was mentioning, giving you the ability to set up a main nsclient++ server, then clients below it in a sort of proxy like setup. It seems to be barely documented though, so it may take some digging around.