Nagios Support Forum

I was planning on using the NSClient++ to monitor our Windows machines and NRPE for Linux. I stumbled upon a thread about SSL weak ciphers with the NSClient++ and wondering if this is a problem for anyone else using NSClient++. If so, how are you overcoming this? I am still running an old version of Nagios Core and using wmi with the check_wsc.pl for the check. I was looking at the check_wmi_plus but again read issues with this regarding the checks and other issues.

So, how are most users who use Nagios XI monitoring their Windows servers? I am talking about basic checks for CPU, RAM, DIsk drives, processes, services, etc I am trying to avoid administration headaches and really want to get Nagios XI implemented.

Hey,

I'm using NSClient++ from the moment I started using Nagios XI, version 0.4.1.102 and I do not have any issues at this moment. We have 90 % Windows Servers. For CPU, Memory and Disk Size, services and processes I use NSClient with nrpe checks, most of my other checks are custom Powershell plugins. Plus NSclient++ has realtime eventlog monitoring.
Everything running smooth for now. You can do almost anything with NSclient++ and Powershell combo.

I would take care with higher versions 0.4.2 and higher. Tested a few time, but had some issues there. (3-4 months ago, so maybe latest versions are more stable)

Grtz

Willem

So you are installing the NSClient++ and then using the NRPE configuration wizard? I was reading a little about that and NCPA but can't get any services to report with NCPA.

What or how do I configure NSClient++ to use NRPE?

http://assets.nagios.com/downloads/nagi ... Client.pdf

For 0.4.x

http://assets.nagios.com/downloads/nagi ... ios-XI.pdf

And in case you have issues:

http://assets.nagios.com/downloads/nagi ... utions.pdf

let us know if you can make it work..

Grtz

Willem

OP - let us know if you need further assistance.
WillemDH - Thanks kindly for the help.

WillemDH wrote:Hey,

I'm using NSClient++ from the moment I started using Nagios XI, version 0.4.1.102 and I do not have any issues at this moment. We have 90 % Windows Servers. For CPU, Memory and Disk Size, services and processes I use NSClient with nrpe checks, most of my other checks are custom Powershell plugins. Plus NSclient++ has realtime eventlog monitoring.
Everything running smooth for now. You can do almost anything with NSclient++ and Powershell combo.

I would take care with higher versions 0.4.2 and higher. Tested a few time, but had some issues there. (3-4 months ago, so maybe latest versions are more stable)

Grtz

Willem

Agreed, I would stick to NSCP-0.4.1.105.
0.4.2 was very problematic when I tested it earlier this year and not worth the headache.

rajasegar wrote:Agreed, I would stick to NSCP-0.4.1.105.
0.4.2 was very problematic when I tested it earlier this year and not worth the headache.

I also agree. I have been doing some testing with 0.4.2 and I am not very happy how lots of checks are suddenly broken.

I like NSClient, just not how the developer goes about his testing.

And using the NSClient++ with nrpe has not thrown up any red flags from your Security department?

If I use the NSClient++ with NRPE I would uncomment out the scripts directory and then you just write your own custom checks and place them in there? Are there default ones or can I take the ones from the Nagios XI server and use them for common Disk, RAM, CPU, Processes, Services, etc checks?

I was using the one that you download when selecting WIndows Server from Nagios XI. I downloaded the nscp client which looks like the nsclient++ but must be different. At least the ini file is and has some basic checks.

I'll have our security team scan this and see if this one has vulnerabilities that show up.

Hey,

You can choose the plugins from Nsclient, or use your self-written plugin or get some plugins from the Nagios Exchange. It all depends on what your expectations are.
Some things you could do to enhance security (but could limit your options to use certain plugins)
- Only enable the modules you need
- Use IP filtering, only allow the Nagios host to connect
- Make sure the user nsclient runs as has only the privilges it needs (most of my nscp services are running as local system)
- Secure the directory where nsclient is installed
- Enable UAC and firewall

It all depends how many resources you have imo. More security takes more time to implement and maintain. I would advise you to use 0.4.1.105 (http://www.nsclient.org/download/0-4-1/)

Maybe Nagios support has some other tips?

Grtz

Willem