SNMP v3 on Windows 2008 R2 SP1


We are looking to use SNMP version 3 for monitoring our Windows 2008 R2 SP1 servers, however it looks like Windows 2008 R2 doesn't support version 3.  We are looking to take advantage of the enhanced security with v3, and as a result I have had a bit of a look at the following third party software.

It does seem to get a bit expensive though when we are looking to monitor more than 25 machines.  I don't mind paying if the product is worth it, so was wondering if anyone had feedback on this product.  Alternatively if someone has used another product that is cost effective, reliable, and secure I'd appreciate the heads up.

Any feedback would be greatly appreciated.

Who is Participating?
Rich RumbleConnect With a Mentor Security SamuraiCommented: (prices are all over the place..) (people report that it works for some but not all windows hosts, openssl version might affect the success) - it's free though.

I don't know anyone using SNMP for windows any more, it's all powershell or WMI, both can integrate with AD better than SNMP ever has/will. PS and WMI also support secured/encrypted connections.
I whole-heartily agree with richrumble.  Yes, SNMP is there and if your application can only do SNMP, then you're stuck aren't you.  However it is very limited compared to the more robust WMI/Powershell.  I would give a look at PS if I were you.  It's quite good.

BTW, don't accept this is part of a solution.  Personally, I just don't like "stealing" points with what are effectively "ditto" comments.  Just wanted to lend more credence that richrumble is correct in case you were hesitant about his answer.
biggles70Author Commented:
Thanks for the responses - totally agree about the SNMP and WMI monitoring etc...  The suggested links were the only ones I was able to locate...

Problem is that the monitoring software we have only supports encryption with SNMP v3 and no encryption with WMI.  To add to this further the software support promotes SNMP monitors over WMI because of Windows performance issues with WMI

Anyway thanks for the info, and might be time for a new monitoring platform.

Rich RumbleSecurity SamuraiCommented:
Might consider writing to the vendor for a patch that add's something like

The "authenticationLevel=ypktPrivacy" should do the trick. It doesn't hurt any connections or other settings, and some namespaces require the setting.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.