DFSR replication broken

sharon mutzafi 21 Reputation points
2023-01-30T20:20:57.7366667+00:00

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

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,546 questions
0 comments No comments
{count} votes

Accepted answer
  1. Thameur-BOURBITA 28,861 Reputation points
    2023-01-30T22:50:14.4766667+00:00

    @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


5 additional answers

Sort by: Most helpful
  1. Thameur-BOURBITA 28,861 Reputation points
    2023-01-31T12:54:35.5833333+00:00

    Hi @sharon mutzafi

    You can to launch non-authoritative restore or authoritative restore for DSFR-R sysvol replication to force the reset of sysvol synchronisation based on first domain controller's copy of sysvol:

    How to force authoritative and non-authoritative synchronization for DFSR-replicated sysvol replication

    You can also just demote then re-promote the second domain controller .

    Please don't forget to mark helpful answer as accepted

    1 person found this answer helpful.

  2. Thameur-BOURBITA 28,861 Reputation points
    2023-01-30T20:32:04.27+00:00

    Hi,

    What do you see if you run net share on each domain controller?

    Did you check event viewer if there is any event related to FDSR replication ?

    Please don't forget to mark helpful answer as accepted


  3. Dave Patrick 426.1K Reputation points MVP
    2023-01-30T23:12:35.06+00:00

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

    Does this mean sysvol and netlogon shares are missing? If so something here could help. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares or simply demote, reboot, promo it again. After demotion make sure the System and DFS Replication event logs are free of errors before trying again.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  4. Dave Patrick 426.1K Reputation points MVP
    2023-01-31T13:28:49.41+00:00

    No they are not missing they are just working on FRS mode instead of DFRS. Thank you for answering.

    How are you validating? FRS Replication isn't possible with Server 2019 and higher.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments