OpsMgr: DHCP management pack for Windows Server 2012 is available


You can download it here:



This article is based on version 6.0.7033.0 of the MP.


What's new?

  • All workflows are implemented using PowerShell to improve overall functionality for this Management Pack.
  • Failover Relationships are now a supported configuration that is being discovered and monitored by the new 2012 Management Pack.
  • Discovery and Monitoring of a DHCP Cluster installation.
  • Scopes, super scopes utilization is being monitored based on events that provide 80% and 100% usage.
  • Utilization of scopes based on policies, client packet drop and residual IP addresses range monitoring.


The guide is very simple and straightforward.  It also lists out the rules and monitors, and discoveries in the MP with a good description of each.


What's in the MP?

This MP targets the Windows Server version 2012 DHCP servers ONLY (Microsoft.Windows.DHCPServer.2012.mp).  It does not replace the previous MP versions… so you will have to consider multiple MP’s if you run DHCP on multiple OS versions.  With all the huge improvements and benefits of DHCP on Windows Server 2012, it would make sense to rapidly shift all DHCP to WS2012 servers in your environment.


There are 20 monitors in the DHCP 2012 MP.  The bummer is that a LOT of these are manual reset monitors.  Manual reset monitors have to be reset, well, manually and my experience has been that the majority of customers do not like these as they do not live in the OpsMgr console.  In the past, whenever we shipped a management pack with manual reset monitors, we would include disabled rules that used the same data source, however this MP does not include those.  Keep this in mind as you deploy this MP.


There are only 4 rules in this MP.  All 4 are performance collection to show scope address utilization.

In the Library MP Microsoft.Windows.DHCPServer.Library.mp, there are many rules and monitors, however, most of these are carry-overs from an older MP version.  That said – they still do focus on the health monitoring of the DHCP server, such as the DHCP service, DHCP database, and many DHCP events.  The event monitors again are mostly manual reset monitors, so keep that in mind.


Key Monitoring Scenarios:




DHCP Server Health

  • This server-centric view monitors the health, availability, security, and configuration of all DHCP components. This view also rolls up status through the use of aggregate monitors.  
  • Is this DHCP server functioning? 
  • Do all DHCP scopes have sufficient remaining
  • IP addresses to hand out?

DHCP Service Health

  • This service-wide view monitors the health, availability, security, and configuration of all DHCP components and rolls up status through the use of aggregate monitors. 
  • Are all my DHCP servers currently healthy across the enterprise?

DHCP Core Component Health

  • Is DHCP ready to serve clients? 
  • The DHCP service is running. 
  • It is bound to all defined network cards. 
  • It is authorized properly in the Active Directory service.

DHCP Database Health

  • Are the DHCP databases healthy? 
  • Able to load all scope and Super scopes. 
  • Enough disk space available for database use. 
  • Database is not corrupted.

DHCP Security Health (Windows Server 2012)

  • Are any security-related issues occurring?
  • Is the DHCP service performing secure updates to the Domain Name System (DNS)?
  • Does the DHCP server detects any rogue servers?

DHCP Performance Health

  • Are the DHCP server queues healthy?
  • Are the DHCP servers responding to all queries in a timely manner?

DHCP Configuration Changes

  • Detects any configuration changes. Optional ability to alert on changes.
  • Configuration reports show any inconsistent settings across the enterprise so that users can correlate those inconsistencies to service-related issues.

DHCP Performance Counter Collection

  • Provides the ability to chart and report on historical performance.

DHCP Policies

  • Are the defined policies for Scopes healthy?

DHCP Cluster and Failover Server Relationships

  • Are the partner server communication is up?
  • Are the clustered nodes are running healthy?



Known issues:

There are some challenges with this MP.  For instance – all scopes are discovered and monitored as a single object.  If a scope fills up – this will turn the monitor to an unhealthy state, and generate an alert.  If a subsequent scope fills up – you will NOT get another alert as the monitor is already unhealthy, and since it is a manual reset monitor… it is highly likely it will stay in this state unless someone resets it after resolving the issue.

One option for this – is to rebuild these scope-full monitors as rules – and simply allow them to create a new alert for each event, so you wont miss any scopes that are full.  The downside is you will see multiple events/alerts as the DHCP service logs these events on a regular basis (once per hour)

Comments (14)

  1. Matthew Brown says:

    Hi Kevin,

    Thanks for the detail on the various SCOM management packs, the information is most helpful.

    I encountered an issue with the Windows Server 2012 DHCP MP 6.0.7033.0 – the discovery script in “Workflow: Microsoft.Windows.DHCPServer.2012.Server.Discovery” fails in some environments.

    Currently engaged with Microsoft Support, three other customers have reported the same issue. No resolution yet, but here is the error so others are apprised as it appears to be a known issue.

    Workflow name: Microsoft.Windows.DHCPServer.2012.Server.Discovery

    Script Name: DiscoverDHCPServer2012

    Operations Manager Log generates Event ID Error 22406.

    The PowerShell script failed with below exception:

    System.Management.Automation.CommandNotFoundException: The term 'Get-WindowsFeature' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    At line:61 char:27


  2. Pavel says:

    Just my two cents on the MP…

    If you have DHCP 2008 and 2012 in your environment and have both MPs installed, the 2008 DHCP MP will discover your 2012 DHCP server. I don't think anyone would want that. I personally disabled the discovery for my 2012 DHCP server and deleted discovered data by 2008 MP running command in Ops Manager powerhsell: Remove-SCOMDisabledClassInstance

    Hope this helps someone…

  3. Asgeir says:

    Having trouble with this:

    EVENT 22406 – Health Service Modules

    The PowerShell script failed with below exception

    System.Management.Automation.CommandNotFoundException: The term 'Get-WindowsFeature' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    At line:61 char:27

    + $DHCP = Get-WindowsFeature <<<<  DHCP

      at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandOrigin commandOrigin)

      at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)

    Any tips?

    Thanx! 🙂


  4. tony says:

    Yes, I have his same issue.  Trying to modify the DHCP management pack as I have read that it may need to have the "import-module servermanager" run in order to recognize the get-windowsfeature cmdlet.  Having issues modifying the DHCP mp due to a dependency on an older Cluster mp.  Waiting on Microsoft support as well.

  5. Zyliday Zhang says:

    I have seen your bolg and find so many system center articles, I want to learn something from you , do you have an e-mail address so that I can contact you ?

  6. Zyliday Zhang says:

    Could you please send an e-mail to me ? Mine is zyliday@163.com
    looking forward to your e-mail .

  7. Josef says:

    Hello Kevin, thank you very much for your excellent tips. Some users report about discovery problems of DHCP 2012 servers. I have the same problem. It is September 2016, but the reported problems are from the year 2013. Do you have any advice about the problem solution?
    Thx a lot

    1. Kevin Holman says:

      I’d need to know specifically what are the discovery problems?

      1. Michael says:

        Hi Kevin,

        I am seeing the same issue with Event ID 22406. Is there a known fix for this?

        The PowerShell script failed with below exception

        System.Management.Automation.RuntimeException: Method invocation failed because [System.String[]] doesn’t contain a method named ‘Item’.
        At line:65 char:20
        + $OS = $CurrVer.Item <<<< (0) + "." + $CurrVer.Item(1)
        at System.Management.Automation.ParserOps.CallMethod(Token token, Object target, String methodName, Object[] paramArray, Boolean callStatic, Object valueToSet)
        at System.Management.Automation.MethodCallNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
        at System.Management.Automation.ExpressionNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
        at System.Management.Automation.AssignmentStatementNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
        at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)

        Script Name: DiscoverDHCPClusterServer2012R2

        One or more workflows were affected by this.

        Workflow name: Microsoft.Windows.DHCPServer.2012.R2.ClusterServer.Discovery
        Instance name: CLUSter
        Instance ID: {blah blah blah}
        Management group: MGMT_Group_Name

  8. GMB says:

    I have found that of two failover relationships, only one is showing.

    We have 3 DHCP servers, one is the failover server for the others via 2 separate relationships. One relationship is defined via the failover server’s IP the other via it’s DNS name. The DNS name is the one that shows under ‘Failover Server Relationship Health’, the relationship created via IP is not showing.

    Is this a known SCOM quirk as the DHCP failover itself seems to be configured correctly.

  9. Morning, could use some advise on what is going wroing here.
    SCOM 2012R2,UR12, 2 DHCP servers, Windows Server DHCP 2012R2, component health I see only entries for servername-DHCP 2012 Database, no other info. I see no info under Scope Health or Super Scope Health. Server health shows green. No info under any of the other sections for DHCP. In the state views there is no info under the columns for DHCP IPv4 Runtime or DHCP IPv4 Scope (circles are white with green outline, no green check mark)
    I see no errors in eventvwr logs on either the dhcp server or scom server.
    Mgmt Packs: MS Windows Server DHCP 2012 and 2012R2, v6.0.7302.0//MS Windows Server DHCP Library v10.0.8.0.
    Thank you for any pointers, suggestions!

  10. Morning, I could really use some assistance with this one. Probably going to be something simple that I have overlooked!

    SCOM 2012R2,UR12, 2 DHCP servers OS 2012R2

    Mgmt Packs: MS Windows Server DHCP 2012,2012R2-v6.0.7302.0//MS Windows Server DHCP Library-v10.0.8.0.

    Server/OS health green, however SCOM is not showing any info related to scopes, DHCP IPv4 Runtime,DHCP IPv4 Scope.

    I see no errors in event logs for OpsMgr on either DHCP server or scom server. I am at a loss as to what else to check. I know not allot of info but I am not sure what other info I could provide to assist.

    Thanks in advance for any and all assistance, pointers…


    1. Update- I was going to attach some screen shots showing what is working in my lab vs what is not working in my Test (pre-production environment)…If you can assist I would be glad to send you the zip file so you can see what I am seeing.
      Thanks again!

  11. Erik says:


    We have a few superscopes each containing 2 subscopes. One of the subscopes is 100% in use, the second subscope in the same superscope has only used 11%. This means there are plenty of addresses available so I don’t need to be alarmed. However, as soon as the total address utilization of the entire superscope reaches 90% I need to be notified.

    Is it possible to override alerts on the individual subscopes, and still be notified when the superscope fills up?

Skip to main content