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

Primary DNS resolver not responding

Indicates one or more of the configured primary DNS resolver for a domain controller is not responding.

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. When monitored remotely, the target server must have WMI remote access enabled and the user must be a member of the Distributed COM Users group.

The test for responsiveness is done by timing the lookup of critical DNS service records from each resolver.

Check to make sure that the identified resolver is actually available and responsive.

Secondary DNS resolver not responding

Indicates one or more of the configured secondary DNS resolver for a domain controller is not responding.

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. When monitored remotely, the target server must have WMI remote access enabled and the user must be a member of the Distributed COM Users group.

The test for responsiveness is done by timing the lookup of critical DNS service records from each resolver.

Check to make sure that the identified resolver is actually available and responsive.

Server sessions

Indicates the number of Server Message Block (SMB) connections in use on the domain controller equals or exceeds the configured threshold.

Name: 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 Server\Server Sessions 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.

System Message Block (SMB) is the protocol Windows 2000 uses for file and print access. Whenever a client workstation accesses files or directories on a server, or whenever the workstation prints a document to a network printer, the client uses an SMB connection.

The number of SMB connections in use on a server is a rough indication of the number of client workstations that are accessing the servers. An unusually high number of SMB connections indicates a large number of clients accessing the server.

A large number of SMB connections will use some amount of memory on the server, though this is generally not a big problem. However, the inordinate number of clients accessing the server can have a negative effect on overall server performance and consequently a negative effect on directory performance as well.

Determine if the increased number of SMB connections is degrading the overall performance of the server. If the performance is being affected, run other tests, including LDAP response time, CPU processor time, Cache copy read hits, and Memory page faults a second.

SysVol details

Information only. Displays the device total size, amount of free space, and percent used; the size of SysVol and the percent of device used; and the path to SysVol.

관련 문서