Chat now with support
지원 담당자와 채팅

Active Administrator 8.3 - Web Console User Guide

Active Administrator Web Console Overview Active Directory Health Alerts Notifications Active Directory Health Check
Using the Health Check landing page Creating a Health Check Setting options for Health Check tests Health check tests
Forest tests Domain tests Domain controller tests Site tests
Active Directory Topology Reports Network Operations Center

DFSRS USN records accepted

Detects that there is heavy file replication traffic.

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
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 DFSR USN records accepted performance counter on a domain controller to see if the value of this performance counter goes above the configured threshold for a period exceeding the configured duration.

Replication is triggered by entries to the NTFS update sequence number (USN) change journal. A high value on this counter, such as one every five seconds, indicates heavy replication traffic and may result in replication latency.

None.

DFSRS working set

Indicates that the working set allocated to the DFS Replication service is too high.

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
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 DFSRS working set performance counter on the domain controller for the DFSR service to see if the value in the performance counter goes above the configured threshold for a period exceeding the configured duration.

Review the system configuration and tune the environment to optimize DFSRS performance as described in these references:

Domain controller relative identifier (RID)

Indicates that the available pool of relative identifiers (RIDs) on the selected domain controller is less than or equal to the configured threshold.

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Required permissions: When monitored locally and remotely, only domain user privilege is required.

Tests the RID pool assigned to the domain controller to see if the number of RIDs available to the server goes below the threshold.

All security principals in the Windows® NT Security Architecture are assigned a unique security ID (SID). The SID is made up of a domain identifier and a RID. RIDs are sequential numbers issued by the domain each time a new security principal (for instance a user object) is created in that domain.

Because each domain controller can create security principals, Active Directory® breaks the available range of RIDs into allocation pools that it assigns to each domain controller. Active Directory assigns one domain controller in each domain to be responsible for allocating RID pools to all of the other domain controllers in the domain; this is the RID Operations Master. When a domain controller uses up its allocation, it requests a new range from the RID Operations Master.

If a domain controller has a problem contacting the RID Operations Master, the domain controller can actually use up its entire allocation of RIDs, and be unable to create new security principals, which can result in failures when adding new users, services, and domain controllers to the domain.

Contact your Microsoft® Windows® support representative.

Domain controller responsive

Indicates if the domain controller is responsive.

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Required permissions: Domain user privilege required.

If Active Administrator® Data Service (ADS) can connect to TCP port 135, the domain controller is reponsive.

If the domain controller is unresponsive, one or more of the following may be the reason:

Active Directory® on the domain controller has failed in some way.

If the domain controller is also a global catalog, you may need to add another global catalog to the site.

관련 문서