Active Administrator 8.6 - Web Console User Guide

NTDS DRA inbound properties filtered a second

Indicates directory property updates were dropped during replication.

Tests the NTDS\DRA Inbound Properties Filtered\second performance counter on the domain controller to see if the value of the performance counter goes above the configured threshold for a period exceeding the configured duration.

During the replication process, Directory Service Agent (DSA) checks each incoming attribute and determines if it was modified subsequent to the version the DSA already has. If the incoming version is later than what the DSA has, the DSA will store the attribute in the directory. If the attribute is the same version or earlier than what the DSA already has, the DSA will drop the attribute, ignoring it for the purposes of replication. This is called a dropped property.

An occasional dropped property is not cause for concern, but a consistent rate of dropped properties may indicate a problem with the replication topology or with the behavior of the domain controllers. A domain controller that is consistently dropping properties during replication is wasting network bandwidth and processing time checking replicated properties that it cannot use.

If the alert does not clear by itself in a reasonable amount of time, contact your Microsoft® Windows® support representative.

NTDS LDAP searches a second

Indicates that the response time of the servers that host the replica of the Global Catalog (GC) equals or exceeds the configured threshold value.

This test issues a query against a well-known object in the GC and records the time that it takes to receive a response.

Failures occur if any of the following occurs:

NTDS LDAP writes a second

Indicates that the amount of Lightweight Directory Access Protocol (LDAP) traffic serviced by the domain controller equals or exceeds the configured threshold.

Tests the NTDS LDAP writes a second performance counter on the domain controller to see if the value goes above the configured threshold for a period exceeding the configured duration.

Active Directory® clients use LDAP to communicate with the Directory Service Agent (DSA). A high LDAP load indicates that a lot of clients are making many requests of the DSA. Increased LDAP load can reduce the throughput of the DSA, and can cause important directory transactions, such as login and authentication, to fail.

Identify the source of the LDAP traffic by using a network traffic analyzer. Note that a traffic analyzer will not detect the traffic generated by a process running on the domain controller itself.

If the traffic is due to many different workstations, the problem may be that there are not enough functioning domain controllers or global catalogs in the site.

Operating system details

Information only. For each selected domain controller, displays the names of the forest, domain, and site; the operating system, version number, installed service pack, and installation date; if the domain controller is a global catalog server or a read-only domain controller; the system time, time stamp for the last boot, and how long the system has been up; the system drive, system directory, Windows directory, boot device, system device, and amount of system memory.