File replication (NTFRS) staging space free in kilobytes
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.
A low disk space condition can be due to many different things. Some possibilities are:
•Resolution
One possible solution is to increase the amount of space allowed for file staging.
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.
2 Use the Active Directory® Sites and Services snap-in to confirm that replication schedules allow replication partners to communicate.
GC response too slow
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
This error can occur if any of the following occurs:
• Active Directory® on the domain controller has failed in some way.Resolution
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.
• |
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. |
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.
Hard disk drive
Indicates that issues have been detected for the hard disk drive on the domain controller.
Data collector
• Category: General
• Name: Hard drive failed
• Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
• Not supported on: Virtual computers
• Required permissions: When monitored locally, 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.Description
The Active Directory Health agent monitors the Hard drive failed data collector on the domain controller. When the hard disk drive of the selected domain controller has a status other than OK for a period of time equal to or longer than the configured threshold, this alert is raised.
Resolution
Review the device configuration and contact your hardware vendor if required.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center