立即与支持人员聊天
与支持团队交流

Active Administrator 8.6.2 - 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 Purging Health Check History Health check tests
Forest tests Domain tests Domain controller tests Site tests
Active Directory Topology Reports Network Operations Center

Inter-site replication manager

Inter-site replication manager

Indicates if a domain controller, other than the preferred bridgehead server(s), is actively replicating outside of its current state.

Requirements
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Description

Active Directory® allows administrators to configure preferred bridgehead servers for each site. Sometimes connection objects are created manually to solve a quick problem, but they are never removed. If these manually-created links are actively replicating, undesirable results may occur.

Resolution

It is possible that this is a transient issue caused by Active Directory replication delays associated with updating File Replication service (FRS) configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross-site Active Directory replication is required, you must manually reset the preferred bridgehead server.

Inter-site replication topology generation disabled

Indicates if the inter-site replication topology generation functionality of the Knowledge Consistency Checker (KCC) has been explicitly disabled. While disabling the KCC is a valid administrator action, it can result in poorly-tuned replication topologies.

Requirements
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Resolution

Clear the fifth bit (16) of the <Root Domain>\Configuration\Sites\<Site name>\NTDS Site Settings\options value to re-enable inter-site topology generation.

Intra-site replication topology generation disabled

Indicates if the intra-site replication topology generation functionality of the Knowledge Consistency Checker (KCC) has been explicitly disabled. While disabling the KCC is a valid administrator action, it can result in poorly-tuned replication topologies.

Requirements
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Resolution

Clear the first bit (1) of the <Root Domain>\Configuration\Sites\<Site name>\NTDS Site Settings\options value to re-enable inter-site topology generation.

Morphed directories exist in site

Indicates if morphed directories are found in a replica tree.

Requirements
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Description

All files and folders that File Replication Service (FRS) manages are uniquely identified internally by a special file identifier. FRS uses these identifiers as the canonical identifiers of files and folders that are being replicated. If FRS receives a change order to create a folder that already exists, which by definition has a different file identifier than the duplicate folder, FRS protects the conflicting change by leaving the original directory structure intact, and renaming the conflicting directory to a unique name so that underlying files and folders can be preserved. The conflicting folder is given a new name in the following format: <FolderName>_NTFRS_<GUID>, where <FolderName> is the original name of the folder and <GUID> is a unique character string, such as 001a84b2.

Common causes of this condition are:

•
A folder is created on multiple machines in the replica set before the folder has been able to replicate. This could be due to the administrator or application duplicating folders of the same name on multiple FRS members.
•
You initiated an authoritative restore on one server and did not stop the service on all other members of the re-initialized replica set before restarting FRS after the authoritative restore.
•
You initiated an authoritative restore on one server and did not set the D2 registry key for the authoritative restore on all other members of the re-initialized replica set before a server replicated outbound changes to re-initialized members of the replica set.
•
You initiated an authoritative restore on one server and manually copied directories with names identical to those being replicated by FRS to computers in the replica set.
Resolution
•
Move the morphed directories out of the replica tree and back in. This method works well for small amounts of data on a small number of targets. However, if you miss end-to-end replication of the move-out, this method can cause morphed directories. This method also requires all members to re-replicate data.
•
Rename the morphed directories. This method does not require re-replication of data, however, it can cause a denial-of-service condition by giving an invalid path when the originating path is renamed.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级