You can download it here:
This article is based on version 6.0.7033.0 of the MP.
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
DHCP Service Health
DHCP Core Component Health
DHCP Database Health
DHCP Security Health (Windows Server 2012)
DHCP Performance Health
DHCP Configuration Changes
DHCP Performance Counter Collection
DHCP Cluster and Failover Server Relationships
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)
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
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...
Having trouble with this:
EVENT 22406 - Health Service Modules
The PowerShell script failed with below exception
+ $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)
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.