Microsoft Knowledge Base Article 910202 contains the following summary and introduction:
SUMMARY
This article contains information to help you troubleshoot an operations master that does not finish initial synchronization because of a replication failure. This article discusses the following topics:
| • | Error messages that can indicate the operations master did not finish initial synchronization because of a replication failure |
| • | Scenarios that describe some possible causes of incoming replication failure on an operations master |
| • | How to use the Repadmin.exe utility to troubleshoot initial synchronization problems |
| • | Partitions that must be replicated before the operations master roles can function |
| • | Changes in initial synchronization requirements in Windows Server 2003 with Service Pack 1 (SP1) |
| • | Effects of downtime on the operations master roles |
INTRODUCTION
Because all domain controllers work together in a domain, most object updates in the Active Directory directory service can be made on any domain controller by using multimaster replication. However, certain operations can only be safely performed by single domain controllers that are called the operations masters. The operations that each operations master routinely performs are called operations master roles. These roles are also known as flexible single master operations (FSMO) roles. To prevent an operations master role from being assigned to more than one domain controller, role holders must successfully inbound replicate-specific partitions from at least one partner domain controller. This process is referred to as initial synchronization. Initial synchronization must occur before operations that depend on an operations master role can be performed.
0 comments
Hide comments
