Welcome to TechNet Blogs Sign in | Join | Help

New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

The MP catalog:  http://www.microsoft.com/technet/prodtechnol/scp/opsmgr07.aspx?SCPProdID=3  has new management packs.... Native DNS and DHCP MP's have been published.

These add Windows 2008 server support, and many changes to the old MP's.

DHCP:

The new version is 6.0.6383.0

A note on these new MP's.... there is a base library, and then MP's for each OS.... 2000, 2003, and 2008.  Only import the OS versions that you need to support in a DHCP role in your network.

*** You MUST DELETE any previous version of the DHCP management pack you were running FIRST.  The old DHCP MP was a conversion MP from MOM 2005, and this new MP is a native rewrite.  Therefore - it will NOT upgrade your old MP and you need to delete it.  You will also need to delete any override MP's you had for the old DHCP MP.  Document what these were, and evaluate if you want to re-apply them toward the new MP.  Best to start fresh when a MP is completely re-written.

To import the Server 2008 DHCP MP - you must first import the Server 2008 Base OS MP's.

DNS:

The new version is 6.0.6278.27

A note on these new MP's.... there is a base library, and then MP's for each OS.... 2000, 2003, and 2008.  Only import the OS versions that you need to support in a DNS role in your network.

*** You MUST DELETE any previous version of the DNS management pack you were running FIRST.  These new native MP's will NOT upgrade any previous versions, and running an older version alongside these new versions is NOT supported.  You will also need to delete any override MP's you had for the old DNS MP.  Document what these were, and evaluate if you want to re-apply them toward the new MP.  Best to start fresh when a MP is completely re-written.

To import the Server 2008 DNS MP - you must first import the Server 2008 Base OS MP's.

READ THE GUIDES.  There are several optional steps that should be given a sincere review.... including enabling and tuning many performance threshold monitors that are disabled out of the box, security requirements, objects that must be created for advanced monitoring, etc..

 

 

*****  NOTE - the DNS MP is reported to cause some high CPU utilization.  Recommend you test this MP in a dev environment, and then limited production to look at the impact.  This is known and being investigated.

 

***** NOTE - The DHCP MP has a known issue logging an event about not being able to read the event log - for the workaround - see:  http://blogs.msdn.com/steverac/archive/2008/08/27/updated-dhcp-management-pack-issue.aspx

Published Monday, August 18, 2008 6:30 AM by kevinhol
Filed under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

Tuesday, August 26, 2008 12:14 PM by John Collins

Just a note that I've seen some weirdness with the DNS pack and ESX.

It seems the new DNS monitors like to spawn a ton of nslookup jobs on windows hosts, as well as more than usual cscript.exe instances.  This caused our ESX servers to max out CPU.

I didn't see it until 24 hours after installing the new mp.   Any thoughts/suggestions/ideas?

# re: New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

Tuesday, August 26, 2008 12:22 PM by kevinhol

Yes - this is being investigated - and an updated MP will likely be released to address some of these high-CPU issues seen in specific environments.  In some cases - the CPU utilization can be quite significant.  

# re: New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

Monday, November 03, 2008 4:37 PM by Tom Brady

Is there any workarounds for the DNS issue yet?  Is it recommended to override that rule that is issuing the NSLookups?

# re: DNS MP consuming CPU

Monday, November 03, 2008 5:15 PM by kevinhol

I dont know of any good workarounds.... some have discussed extending out the monitors that run these scripts, to space out the frequency, and that helping.  The updated MP is expected out very soon.

# re: DNS MP consuming CPU

Thursday, November 13, 2008 11:20 AM by Richard Gerrits

In our case, the high CPU is caused by the fact that the nslookup command generates more than 4k of output. (we have about 60 dns-servers)

Because of this, the wshShell.Exec() is hanging in an endless loop.

(while (objExec.Status == 0) {})

Only workaround I can think of, is using a modified nslookup.exe, which limits the output to 4k.

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker