Answered by:
SNMP OID to get DHCP scopes from 2012 Server

Question
-
I searched internet to get SNMP OID to obtain DHCP scopes from 'Win 2012 Server'. Unable to find anywhere.
I did search microsoft documentation for 'Win 2012 server' also. I found that SNMP is deprecated in Win 2012 Server.
Does the DHCP server in 'Win 2012 Server' support SNMP? What is the OID to get DHCP scopes?
Wednesday, March 27, 2013 1:14 PM
Answers
All replies
-
Friday, March 29, 2013 10:02 AM
-
Jeremy, Microsoft,
Thank you for the speedy response.
Arul Jose.
Friday, March 29, 2013 2:19 PM -
Hi,
this seems not to be completely true. We also have problems with dhcp-snmp.
Our setting: domain integrated dhcp-servers with snmp service enabled. We use snmp to get lease statistics for different scopes and visualize them with mrtg.
We have installed dhcp configured it and then installed the snmp service and configured it in the services tabs. We use the enterprises.311.... Oids to query the dhcp server. Everything seems to be OK. But after the first patchday requiring a reboot of the server snmp queries against dhcp didn't work anymore.
We have done some investigations:
1. After a fresh install of snmp service, queries against dhcp server Oid are answered correct.
2. One can start and stop the service as often one likes, queries are still successful
3. After a reboot queries against Oid enterprises.311... (dhcp) failed, while other queries against enterprises.77... still work correct.
It seems that after a reboot msv1_0.dll and cryptdll.dll are not loaded by the snmp service (we use tasklist /m)
This behavior is not "deprecation" its simply a fault!!!
Our decision to use MS server products as network servers (dhcp, dns, radius/nps) in a heterogeneous environment like a big german university is based on vendor independent standards - i.e. protocols like snmp for monitoring tasks.
From this point of view you surely understand our demand of a working snmp service - in our opinion (and german law) its a guaranteed quality. MS stated this on http://technet.microsoft.com/de-de/library/ff716193.aspx "Betrifft: Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012, Windows Vista"
It is self evident that a component that is delivered to customers as a part of windows server 2012 should work without a fault in a deterministic way.
Regards Heinrich
- Proposed as answer by alupigus Wednesday, August 10, 2016 10:50 AM
Tuesday, April 2, 2013 9:56 AM -
Good work and great reply. Agree wholeheartedly.Monday, July 22, 2013 9:38 AM
-
Very much agree! SNMP is the standard for systems monitoring. It makes no sense to remove support from Server 2012. Please bring this back.
We have DHCP scopes on our Server 2012 that we need to monitor for free addresses. Not having an SNMP interface for this information takes away our ability to monitor this critical service.
Unacceptable!
- Proposed as answer by Michal Klos Tuesday, August 25, 2015 9:42 AM
- Unproposed as answer by Michal Klos Tuesday, August 25, 2015 9:42 AM
Tuesday, July 29, 2014 3:31 PM -
We are seeing the same behavior. SNMP monitors DHCP correctly until the server is restarted. Jeremy Wu - if SNMP is not supported in Server 2012, what method do you recommend for monitoring Windows DHCP scopes? We're specifically looking for some way of being alerted when a scope is low on addresses.
Tuesday, October 28, 2014 2:25 PM -
We were able to confirm the two DLLs that are missing in the task list upon reboot. Is it possible to script loading those modules after reboot? Like call regsvr32 for msv1_0.dll and cryptdll.dll. I'm curious there is any risk to manually doing this? Thoughts?
BTW, a workaround is to remove the SNMP service, reboot, and reconfigure it. It doesn't take too long to do and we don't reboot our DHCP servers until patch time.
One other thing we tried was setting the SNMP service to a delayed start to see if it is a timing issue and that did not work either. Thanks!
Friday, October 31, 2014 9:05 PM -
We now see the exact same issue with the two dll's that don't load after a reboot. Has anyone found a way to load these dll files manually? Since it works after installing the snmp feature there must be a way to fix/achieve this so it survives a reboot. This is a ridiculous bug.Monday, November 3, 2014 1:28 PM
-
then what is an alternative? do you suggest that milions of people who track their dhcp-lease usage with popular monitoring tools may now throw them away to the bin and start checking the status manually?Tuesday, August 25, 2015 9:40 AM
-
Will Microsoft be able to fix this issue ever? this is affecting lots of administrators all over the world.
SNMP is very useful protocol and cannot be ignored by Microsoft.
Thanks.
Friday, March 25, 2016 10:58 AM -
The missing question is: how do we get our SNMP-based monitoring system up to speak with our Server 2012 R2 DHCP Server?Tuesday, April 12, 2016 8:35 AM
-
I'm with bernt here.
I too need to monitor my 2012 DHCP Server with my SNMP-based monitoring system...
Anyone found a fix for / a way around this already?
Wednesday, December 7, 2016 12:35 PM -
Someone else found a workaround for this, and I thought I'd share:
On the DHCP server,:
Disable the SNMP service.
Create a Scheduled Task, set it to run at startup of the server, use SYSTEM (not a domain user), start snmp.exe
After doing this, I'm able to monitor my DHCP scopes via SNMP...
Friday, December 9, 2016 9:19 AM -
Hello Van,
I am new to windows server. However i have been assigned an task to monitor dhcp. I face the same situation as you. Can you share the execute steps which fixed the dhcp scope monitor issue.
Thanks
Thursday, February 23, 2017 9:03 AM