Skip to main content

useful tasks for the extended ad mp

The 3rd District Fire Rescue Task Forces, Toky...if you’ve decided to start using the extended ad mp over on, you’ve probably noticed in the user guide (cough) that in order to pick up expensive/ineffecient ldap queries, you need to change some registry values.

first of all, what’s the fire engine have to do with this post?  actually nothing.  i just saw it and thought “red”.  yeah.

anyway, if you’re going to set it manually, it shows you how right here in guide:

  1. Open the Registry Editor
  2. Locate the following Registry key – HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\15 Field Engineering and change its value to 4 or 5.
  3. Open the Operations Console, and click the Authoring button.
  4. Expand Management Pack Objects, and then click Rules.
  5. In the Rules pane, type LDAP into the Look for box, and then click Find Now.
  6. Locate the LDAP Summary Report of Expensive or Inefficient Queries and/or the An expensive or inefficient LDAP query was performed rule.
  7. Right-click the rule, click Overrides, click Override the Rule, and then click “For all objects of type: Active Directory Domain Controller Server 2003 Computer Role.
  8. Enable the Override-controlled parameter labeled Enabled and set its Override Setting to True.
  9. Target the override to a custom Management Pack and not the Default Management Pack. Click OK to save your changes.

if you’d rather create tasks, here’s the basic premise:

  1. flip over to the authoring console node.
  2. create a new task as type: agent tasks/command line.
  3. choose the destination management pack of choice as long as it is NOT the default management pack.
  4. be creative with your task name (yes, that’s sarcasm).  for example, i named mine: enable ntds field engineering diagnostics.
  5. choose the task target.  i set mine to: active directory domain controller server 2003 computer role.  i did this namely so that someone wouldn’t try to point this to a regular computer.
  6. full path to file: %windir%\system32\reg.exe
  7. parameters: ADD HLKM\System\CurrentControlSet\Services\NTDS Diagnostics /v “15 Field Engineering” /t REG_DWORD /d 0x4 /f

for the love of all things holy, please do not forget the /f.  if you do, the task will never actually complete since the value should already exist on your domain controller.

one more thing to add, i created a task to turn this off.  all you need to do is change the parameter line to this: ADD HLKM\System\CurrentControlSet\Services\NTDS Diagnostics /v “15 Field Engineering” /t REG_DWORD /d 0x0 /f

if everything worked as planned, when you execute this task, it should look just like this:



Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …