<html> <head> <style></style> </head> <body class='hmmessage'><div dir='ltr'> With NSClient++, you can easily copy the INI file around. for NRPE and NSClient++ config files I always put in 3 generic names as "allowed hosts" ... nagios1.domain.local, nagios2.domain.local, nagios3.domain.local. Those 3 are CNAMEs to my actual nagios systems so I don't have to worry about updating config files if I'm testing a new plugin on a test Nagios box, migrating, etc. Only downside is that it does require good DNS and you have the normally trivial overhead of that DNS lookup. -- Mat W. <div>> From: mark.elsen@gmail.com > Date: Fri, 5 Aug 2011 07:48:11 +0200 > To: mrsbonus1@yahoo.com; nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] What the best way to monitor Windows? > > > Ok, so it sounds like there might be 3 "best" ways to monitor Windows in > > general. > > I will have to check them out in detail before deciding which way to go. I > > do note that the following though from reading about them - > > > > 1. Checkwmiplus > > > > > > - I switched from NSclient++ to checkwmiplus, because agent less > monitoring gives me a more > flexible nagios environment : - not needing a remote agent makes > migration NAGIOS to another server easier, because > usually because of security reasons, you will be configuring the agent > to allow connections from a particular (NAGIOS) > server only. > - an agent needs to be extra > installed on the windows server; that may seem 'easy' ; but it > isn't if you are in a large IT group where people carry different > heads, and things like 'convincing debates' and 'overal installation > procedures' come into place. > > - there are disadvantages > too : checkwmiplus has increased the cpu load on my nagios server > dramatically because of the combined use of wmic and the perl-based > checkwmiplus script. And multiple instances are running > all the time for a large number of servers. I think I will have to > migrate to a speedier nagios server in the future > > - checkwmiplus is still under > very active development which has pros and cons; pros because of the > active interest of the developer, cons because active installation > components are still being changed, making upgrading and followup > on versions a little bit more cumbersome and time intensive , then for > nsclient++ , which ,already, much more stabilized. > > M. > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Nagios-users mailing list > Nagios-users@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 </div> </div></body> </html>