Converse agora com nosso suporte
Chat com o suporte

Active Administrator 8.6.2 - User Guide

Active Administrator Overview User Provisioning Certificates Security & Delegation  Active Directory Health
Switching to Active Directory Health Using the Active Directory Health landing page Installing Active Directory Health Analyzer agents Using the Active Directory Health Analyzer agent configuration utility Excluding domain controllers Managing the Remediation Library Analyzing Active Directory health Analyzing Azure Active Directory Managing Active Directory Health Analyzer alerts Managing alert notifications Pushing alerts to System Center Operations Manager and SNMP managers Managing monitored domain controllers Managing data collectors Active Directory Health Templates Managing Active Directory Health Analyzer agents Using the Troubleshooter Recovering Active Directory Health data
Auditing & Alerting Group Policy Active Directory Recovery Active Directory Infrastructure DC Management DNS Management Configuration
Using the Configuration landing page Managing tasks Defining role-based access Setting email server options Configuring SCOM and SNMP Settings Setting notification options Setting Active Template options Setting agent installation options Setting recovery options Setting GPO history options Setting certificate configuration Setting service monitoring policy Managing archive databases Migrating data to another database Setting a preferred domain controller Setting up workstation logon auditing Managing configuration settings Setting user options Managing the Active Directory server
Diagnostic Console Alerts Appendix
Domain controller alerts
Active Directory Certificate Services service is not running Active Directory Domain Services is not running Active Directory Web Services service is not running Consecutive replication failures DC cache hits DC DIT disk space DC DIT log file disk space DC LDAP load DC LDAP response too slow DC Memory Usage DC properties dropped DC RID pool low DC SMB connections DC SYSVOL disk space DC time sync lost Detected NO_CLIENT_SITE record DFS Replication service not running DFS service is not running DFSR conflict area disk space DFSR conflict files generated DFSR RDC not enabled DFSR sharing violation DFSR staged file age DFSR staging area disk space DFSR USN records accepted DFSRS CPU load DFSRS unresponsive DFSRS virtual memory DFSRS working set DNS Client Service is not running Domain controller CPU load Domain controller page faults Domain controller unresponsive File Replication Service is not running File replication (NTFRS) staging space free in kilobytes GC response too slow Group policy object inconsistent Hard disk drive Intersite Messaging Service is not running Invalid primary DNS domain controller address Invalid secondary DNS domain controller address KDC service is not running LSASS CPU load LSASS virtual memory LSASS working set Missing SRV DNS record for either the primary or secondary DNS server NETLOGON not shared NetLogon service is not running Orphaned group policy objects exist Physical memory Power supply Primary DNS resolver is not responding Secondary DNS resolver is not responding Security Accounts Manager Service is not running SRV record is not registered in DNS SYSVOL not shared W32Time service is not running Workstation Service is not running
Domain alerts Site alerts Forest alerts Azure Active Directory Connect alerts
Event Definitions PowerShell cmdlets

File Replication Service is not running

Previous Next


Alerts Appendix > Domain controller alerts > File Replication Service is not running

File Replication Service is not running

Indicates the File Replication Service is currently not running on the domain controller.

Data collector
•
Category: Windows Services
•
Name: File Replication Service
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: When monitored locally or remotely, domain administrator privilege is required.
Description

The Directory Analyzer agent periodically checks to ensure the File Replication Service is running.

Resolution

Use the Services MCC snap-in or another SCP application to restart the File Replication Service.

File replication (NTFRS) staging space free in kilobytes

Previous Next


Alerts Appendix > Domain controller alerts > File replication (NTFRS) staging space free in kilobytes

File replication (NTFRS) staging space free in kilobytes

Indicates that the amount of disk space allocated for staging files during replication is less than or equal to the specified threshold.

Data collector
•
Category: Performance Counters
•
Name: File replication staging space free in kilobytes
•
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.
Description

The Directory Analyzer agent monitors the FileReplicaSet\KB of Staging Space Free performance counter on the domain controller. If the value of the performance counter drops below the configured threshold for a period exceeding the configured duration, the agent will set this alert condition.

If the File Replication Service (FRS) runs out of staging disk space, replication will stop. The size of the contents of the staging areas for all active replication sets are subtracted from the user controlled size.

A low disk space condition can be due to many different things. Some possibilities are:

•
The size of the data to be replicated is larger than the staging area
•
There are too many replica sets active at once
•
There are files destined for one or more out-bound partners that have not been connected for a while
Resolution

One possible solution is to increase the amount of space allowed for file staging.

1
Determine that the number and size of the files that need replicating will fit in the amount of space allocated. The staging areas can be found by searching the registry.

The HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\ReplicaSet registry key contains one or more sub-keys using a GUID as the key name for each active replica set. Each replica set contains both a Replica Set Root and Replica Set Stage value.

▪
The Replica Set Root value describes the file system folder that will be replicated.
▪
The Replica Set Stage value describes the folder that is used for the staging area. The staging areas can be inspected to determine which one(s) are consuming disk space.
2
Check the amount of space allocated by viewing the Staging Space Limit in KB value under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs registry key. This value defines the maximum amount of disk space that can be consumed by all staging areas at any one time.
3
If you determine that the staging areas need more disk space, increase the value of the Staging Space Limit in KB.

If the problem cannot be resolved by adjusting the amount of space needed and allowed, turn your attention towards replication schedules and the connectivity between computers. The SYSVOL share is replicated between all domain controllers in the same domain. Other replication partners can be found using the Distributed File System (DFS) console.

1
Check that the server has good connectivity with each of its replication partners. Ping the replication partners from the domain controller that issued this alert to determine if there is connectivity. The problem may be that DNS has the incorrect address or that the IP stack for the domain controller or the Directory Analyzer agent is misconfigured.
2
Use the Active Directory® Sites and Services snap-in to confirm that replication schedules allow replication partners to communicate.

GC response too slow

Previous Next


Alerts Appendix > Domain controller alerts > GC response too slow

GC response too slow

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

Data collector
•
Category: Performance Counters
•
Name: NTDS LDAP searches a second
•
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.
Description

The Directory Analyzer agent periodically issues a query against a well-known object in the GC and records the time that it takes to receive a response. If the time taken exceeds the configured threshold for a period exceeding the configured duration, the agent will set this alert condition.

This error can occur if any of the following occurs:

•
The indicated domain controller does not exist.
•
The server might not host the replica of the Global Catalog.
•
The domain controller no longer has connectivity to the network.
•
The DNS records for the domain controller are incorrect; e.g., the IP address for the domain controller is not what is published in DNS as viewed by the Directory Analyzer agent.
•
Active Directory® on the domain controller has failed in some way.
•
Active Directory on the domain controller is overloaded and is taking too long to respond.
•
The domain controller is not running.
Resolution

Make sure the indicated domain controller actually exists. If it is not, run NTDSUTIL and select the metadata cleanup option to clean up the erroneous objects in the directory.

Make sure the domain controller is running. If the domain controller is not running, start it.

Make sure the domain controller hosts a replica of the Global Catalog.

Ping the domain controller to see if there is connectivity. If there is not, fix that problem. The problem may be that DNS has the incorrect address or that the IP stack for the domain controller or the Directory Analyzer agent is misconfigured.

Check the LDAP response time for the domain controller on the Active Directory Health Analyzer Summary tab for the domain controller. If the LDAP response time is too high, you may need to add another domain controller for the same domain in the same site.

If this is the only server that hosts a replica of global catalog, you may need to add another global catalog to the site.

Group policy object inconsistent

Previous Next


•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Permission requirements: When monitored locally and remotely, only domain user privilege is required.
Description

The Directory Analyzer agent periodically compares the directory representation of GPOs in a domain to their representation on the local SYSVOL. This alert is active when the version number stored in SYSVOL differs from the version number expected in the local directory. This situation typically arises from high replication latency or duplicated NTDS Connection Objects.

Resolution

A Group Policy Object on <server-name> is represented inconsistently between the local directory and the local file system. This problem can be remedied by forcing NTFRS and Active Directory® to refresh.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação