So do you wanna monitor your DHCP 2008 R2 server?

Well, as you may know if you tried there’s no MP from Microsoft, yes after 18 months of GA for the latest operating system from MS still no MP for such an important service. So I took my time and gave a look at the current MP for Win Server 2008. Immo it’s plain awful, poor coding and the monitors and discoveries are almost based on netsh output positional parsing, the recipe for problems. And indeed the whole stuff doesn’t work with R2 because in the netsh output we have two more lines that where not there in 2008. I’ve really had enough of average MPs quality, but that’s another story.

So "closing my nose" I introduced the minimum changes to get on par with Win Server 2008 DHCP monitoring, it took a couple of hours including testing it in an environment with 2003, 2008 and 2008 R2 DHCP servers.  I release the code to the community, but you must be advised this is code I won’t recognize as mine, once again bare minimum mods to an awful MP to make it works with 2008 R2, that’s it.

You can find the MP here.

It replaces the following workflows:

  1. Microsoft.Windows.DHCPServer.Library.Rule.CollectPerformanceData
  2. Microsoft.Windows.DHCPServer.2008.ComponentDiscovery
  3. Microsoft.Windows.DHCPServer.2008.ComponentDiscovery.Portion1
  4. Microsoft.Windows.DHCPServer.2008.ServerDiscovery

I didn’t replace ComponentDiscovery portion 2 and 3 (disabled by default), if you have a DHCP with thousands of scopes then you might need to recode them as well.

As usual hope this help and, on the other hand, use it at your own risk.

– Daniele

This posting is provided "AS IS" with no warranties, and confers no rights.

  1. #1 by Daniele Grandini on April 12, 2011 - 6:00 pm

    Hi Sylvain,
    I can confirm the DHCP MP you’re referring to is the one that won’t work in mixed environments. It has at a minimum the following bugs:
    1. Views are missing display strings.
    2. Manual reset monitors. This is flagged by the BPA as a warning.
    3. Alert view showing all alerts.
    4. Alerts generated by non-R2 DHCP servers due to all DHCP servers discovered as they were R2.

  2. #2 by Sylvain Hamel on April 11, 2011 - 2:54 pm

    There is a DHCP management pack for R2 already. It doesn’t work ? I’m still running an early MP from the R2 TAP program….

    • #3 by Daniele Grandini on April 12, 2011 - 8:11 am

      Hi Sylvian, the MP for DHCP R2 has been released a long ago and then retired (as far as I now) due to the errors it contained, it discovered all the DHCP servers on your network as DHCP 2008 R2 servers causing all kind of mess. From the link you post it seems it has been re-released with a silent change in July. If you check from the OM Console the MP is not listed as an available update (I’m currently using 6.0.6452.0 version). I will take a look at it but I fear it’s still the same mess.

      – Daniele

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: