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 opsmanjam.com, 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:

image

Labels:

Comments

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

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.   DETECTION status messages take 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 m
3 comments
more »