NSClient++ vs. Check_WMI_Plus

[ZachW]

What is the general consensus on using NSClient++ vs Check_WMI_Plus to monitor Windows machines? I'm evaluating Nagios and don't like the idea of having an agent so I'm leaning towards using Check_WMI_Plus. However, I'm wondering if anyone has experience using both and has pros and cons of each? Are there advantages to having the agent over the check_wmi_plug plugin?

Thanks.

[yancy]

ZachW,

The largest advantage to using an agent such as NSCLinet vs Check_WMI_Plus is the ability to use custom scripts in your environment. For example, if your company has some 3rd party application that has no WMI namespace, you could write a VBS or PS1 script, and NSClient would run it and return the results. Other then that, I agree that check_wmi_plus is more agreeable.


-Yancy

[ZachW]

That's a good point. I guess I can have the default be using check_wmi_plus and then deploy NSClient when I need more access. Thanks for the feedback.

[sreinhardt]

*Shameless plug* You might also take a look at ncpa, it covers just about everything nsclient does, and uses the same config layout for linux and mac installations as well. But if you're set on nsclient, I'm not going to blame you for it.

[ZachW]

I'm not set on anything. I'm still learning and trying to figure out the best way to monitor Windows boxes. Being new I'm trying to make sure there aren't any gotchas to using something like check_wmi_plus over NSClient (or ncpa) like performance or resources. I'll take a look at ncpa as well.

Thanks

[slansing]

Well sounds good! Let us know if you need help along the way. You may want to open a new thread though once you decide on a solution.