Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

DNS MP update ships – support for DNS on Windows Server 2008 R2 and many fixes

DNS MP update ships – support for DNS on Windows Server 2008 R2 and many fixes

  • Comments 11
  • Likes

The DNS Management pack has been updated.  The current version as of this article is 6.0.7000.0

 

Get it from the download center:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=633B718F-5FE8-47D5-A395-8203F8EC354F

 

 

This is a GREAT update.  Here are some key changes in this version:

 

  • Added support for Windows Server® 2008 R2 DNS server.

That’s pretty self explanatory.  This version now fully supports the DNS services running on Server 2008 R2 OS.

  • Changes in how “PrimaryServer” and “SerialNumber” properties are updated

This is HUGE!  The DNS MP was one of the primary causes of Config Churn which I wrote about here:  http://blogs.technet.com/b/kevinholman/archive/2009/10/05/what-is-config-churn.aspx   With this update – that churn is now resolved.  The properties of PrimaryServer and SerialNumber no longer change on a frequent basis.  This is a big improvement and the biggest reason to get this update in place ASAP.

  • Enhancements to Forwarder Availability Monitor

Several changes were made here:  Internal > Public, Error > Warning, Interval 900 > 913, NSLookUp uses the timeout parameter

  • New views defined:
    • Forwarder state view
    • Zone state view

These views were not present before – now you can spot-check the health of individual zones and forwarders quickly.

  • Scripts-Timeout changed from 30 to 300

This enhancement will allow scripts longer to complete on busy DNS servers or DNS servers with large numbers of components.  The change really wasn’t from 30 > 300 on all workflows – rather – all workflows, regardless of their previous timeout, have been set to 300 seconds, or more.

  • All monitors changed from “Internal” to “Public”

This allows you to be able to create and add recoveries and diagnostics on any monitor.  When flagged as “internal” they cannot be referenced in an unsealed MP.

  • All classes made “Public”

This allows you to create custom scoped views for any class in the MP – referencing them in another custom MP of your choice.

  • New rules defined for all monitors with manual reset

There are 4 new rules added which are disabled out of the box.  These can be used to quickly replace the included (matching names) manual reset monitors if your organization cannot use Manual Reset monitors due to lack of console use (enterprise connectors as the primary ticketing and notification system)

Microsoft.Windows.DNSServer.2008.EventCollection.RootHintsConfiguration.ConfigureRootHints

Microsoft.Windows.DNSServer.2008.EventCollection.RootHintsConfiguration.ConfigureRootHints.Warning

Microsoft.Windows.DNSServer.2008.EventCollection.RPCProtocolInitialization.RestartRPCService

Microsoft.Windows.DNSServer.2008.EventCollection.WINSNetbiosInitialization.ConfigureWINSRSettings

 

Some other changes were also made, in addition to what's in the guide.  Most were setting a handful of monitors from Error to Warning (State and Alert) and changing the frequency of many workflows from 900 seconds to 913 seconds… this was likely done to keep multiple workflows from running at the same time and creating false alerts due to server load when multiple workflows trigger on the same frequency.  Views were renamed to reflect the 2008 R2 support.

Comments
  • Finally! :)

  • Are you just too enthusiastic or did I miss a download link somewhere :)

  • Here's the download link:

    www.microsoft.com/.../details.aspx

  • Thanks Petar,

    My mistake, I was looking at the pinpoint site.

    You probably heard about that one, it is the official management pack catalog site from Microsoft.

    I don't know why I tried it in the first place, I must have an off day :)

  • How do you check if the actual files are updated? I've installed CU4 so the version changed to 6.1.7221.0. Now after the upgrade is  down to 6.0.7000.0.

    Thanks,

  • In the documentation, they recommend to delete the previous version 6.0.6480.0 . There are some dependencies on other MP (Active Directory MP) so it could not be deleted. Does the installation update the version 6.0.6480.0 ???    

    Thanks

  • @Bob -

    The guide does *not* recommend you delete the previous version of the MP.  Here is the text - and this is the only place I am aware of that we talk about the previous MP:

    -------------------

    When you upgrade the Windows Server DNS Management Pack from version 6.0.6480.0 to version 6.0.7000.0, you will see the alert, ‘Scheduler DataSource Module Failed Alert’ generated from every DNS server. This alert will not appear if version 6.0.6480.0 is deleted prior to importing version 6.0.7000.0.

    Note:  This alert is for information only, no action is required.

    -------------------

    This is simply a one-time alert from each DNS server and can be ignored and closed.  I absolutely would not delete the previous MP's - as that can be painful because you would also have to remove any MP's that referenced the DNS MP.

  • Still funny thing.. If they made a good MP they still got something wrong...

    Check the year :)

      "2/22/2010 - Updated release, version 6.0.7000.0. Added Windows Server 2008 R2 DNS server support " :)

  • @Adrian -

    Date fixed.  Next?  :-)

  • No.. nothing else.. but still searching!

  • Hi Kevin,

    we have MS DNS 2008 Server MP (6.0.6278.27)  quite old one which is failing to discover the Domain Controllers ( which have a DNS role ) Can you please help out on this one ? It was successfully able to discover DNS Servers . After looking at the logs it seems the vb sript for discovery is failing .

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs