Windows DFS initialization replication behavior and replication completion confirmation

In our daily operations, the enterprise is likely to use the Windows DFS as the file management, we in the replication process using DFS, the initial replication of each replication folder will have a primary member and one or more downstream members. When initial replication is established, the default master member's file priority is higher than the downstream member, that is, when I have A and B two servers, a as the main member, B is a downstream member, A and B if there is the same file, a file will overwrite B's file, even if the file on B is up to date, a file is old, In the process of initial replication of a as a primary member and B, the file of a will overwrite the file of B, and when the initial replication is complete, the role of the primary member is automatically canceled, all member servers are the same priority, and the files are modified or created on any member server. will be synchronized to the other member servers of the replication group.

When we establish a replication relationship between the file servers, how can we tell which one was once the primary member of the server? We can log on to each server, open the event manager, search the DFSR log for EventID 4112 to know who the primary member server for that replication group is, as

In addition, how do we confirm the initial replication is complete? There are two ways of doing this:
1. We can search the downstream server for log EventID4104, such as

2. We can view the replication status with the PowerShell command in the downstream server
Get-wmiobject-namespace "Root\microsoftdfs"-query "select * from Dfsrreplicatedfolderinfo"
You can view the value of state, the State has several states, usually after the initialization is completed, the status is 4, the state in progress is 2
0:uninitialized
1:initialized
2:initial Sync
3:auto Recovery
4:normal
5:in Error

Windows DFS initialization replication behavior and replication completion confirmation