Active Administrator 8.6.3 - Web Console User Guide

Inter-site replication manager

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

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.

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.

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.

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.

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: