DFSR replication broken

Question

Hi all, i have a problem on a domain environment. There are two 2019 DC's, both have one NIC, DNS is fine, replication is fine. 

DFSRMIG.EXE /GETMIGRATIONSTATE shows:

All domain controllers have migrated successfully to the Global state ('Eliminated').
Migration has reached a consistent state on all domain controllers.
Succeeded.

However, DFSR volume was not created, probably because of this:

Wmic /namespace:\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state

ReplicatedFolderName ReplicationGroupName State
SYSVOL Share         Domain System Volume 2

so it seems that i'm stuck on initial sync, which explains all the problems

Answer 1

@sharon mutzafi

If you have already a domain controller on windows 2019 , that means that you don't need to migrate from to DFSR for sysvol replication , because Windows 2019 cannot be promoted as domain controller in a domain with FRS replication for sysvol folder.

That's why The result of DFSRMIG.EXE /GETMIGRATIONSTATE is eliminated and the folder was not moved because we can't have FRS on windows 2019

Nothing to do in your side :)

Please don't forget to mark helpful answer as accepted

Answer 2

@Thameur-BOURBITA I have started by troubleshooting by reading that KB.

I was stuck because on one of the DC's, the entire "domain name system" was missing, so i had lots of problems creating it. State has changed to 4 now instead of 2. Replication is working, seeing "The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. "

So i'm fine, thanks for all the help, @Anonymous as well.