Hi,
I have 2 questions :
What is the best windows clients
nsclient++ or winnrpe
IMHO : winnrpe is more easier than nsclient++ (for configuration part)
In found this webpage: https://support.nagios.com/kb/article.php?id=519
But is this article can be used for a winnrpe client ?
Best regards
SSL certificat and nsclient++ vs winnrpe
Re: SSL certificat and nsclient++ vs winnrpe
NSClient++ hasn't received a release in ~3 years, but is by far the more popular solution:cormansa wrote:I have 2 questions :
What is the best windows clients
nsclient++ or winnrpe
https://nsclient.org/
You can configure the NSClient++ NRPEServer with a SSL certificate:
https://docs.nsclient.org/reference/cli ... ertificate
I'm not sure if it'll be NRPE v3 compatible, though. Likely at lest NRPE v2 compatible.
NCPA is the windows agent that is officially maintained by the same people maintaining Nagios Core/XI:
https://www.nagios.org/ncpa/getting-started.php
That's probably a better question for the folks who maintain winrpe:cormansa wrote: In found this webpage: https://support.nagios.com/kb/article.php?id=519
But is this article can be used for a winnrpe client ?
https://itefix.net/winrpe
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/
Re: SSL certificat and nsclient++ vs winnrpe
Well, I'm back on this thread because I'm trying to use NCPA as recommended.
I have a problem, I have a windows server in french, so when I want to monitore a particular process, I gave a error :
An error occured:
'utf8' codec can't decode byte 0xe8 in position 463: invalid continuation byte
arrrg
There are some issue on github (reported in 2021) :
439 - 608 - 770
Normally, this will be fixed in version 3.0.0 but where is this version 3.0.0.
I have a problem, I have a windows server in french, so when I want to monitore a particular process, I gave a error :
An error occured:
'utf8' codec can't decode byte 0xe8 in position 463: invalid continuation byte
arrrg
There are some issue on github (reported in 2021) :
439 - 608 - 770
Normally, this will be fixed in version 3.0.0 but where is this version 3.0.0.