Indicates directory property updates were dropped during replication.
• |
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022 |
• |
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group. |
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.
If the alert does not clear by itself in a reasonable amount of time, contact your Microsoft® Windows® support representative.
• |
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022 |
• |
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group. |
Failures occur if any of the following occurs:
• |
Active Directory® on the domain controller has failed in some way. |
• |
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022 |
• |
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group. |
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.
• |
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center