DFSR replication broken

sharon mutzafi 21

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

Accepted answer

Thameur-BOURBITA 32,641 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
Please sign in to rate this answer.
sharon mutzafi 21 Reputation points

2023-01-31T07:21:59.27+00:00

On the 2nd domain controller I see: The DFS Replication service failed to replicate the replicated folder at local path because the local path is not the fully qualified path name of an existing, accessible local folder.

Additional Information:

Replicated Folder Name: SYSVOL Share

Replicated Folder ID: 9AF4632E-67C4-49E1-A798-427B79F81753

Replication Group Name: Domain System Volume

Replication Group ID: 8490DD0F-98AD-4D86-942B-80CFC257F583

Member ID: A8FCA6CB-C360-427E-AC13-8E29B86F1B97

Furthermore, replication is not working properly, state is stuck on 2, please see the diagnostics on my first post.
Sign in to comment

5 additional answers

Thameur-BOURBITA 32,641 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
Please sign in to rate this answer.

1 person found this answer helpful.
sharon mutzafi 21 Reputation points

2023-01-31T12:57:55.29+00:00

@Thameur-BOURBITA I read this Kb. on the msDFSR-RootPath it shows C:\Windows\SYSVOL\domain

is it ok? this is on the main DC (the one that holds the FSMO)

Thameur-BOURBITA 32,641 Reputation points

2023-01-31T13:03:25.1+00:00

@sharon mutzafi

on the msDFSR-RootPath it shows C:\Windows\SYSVOL\domain

Yes it's ok . This is the default path of sysvol folder.

I have the same value in my domain controllers.

Please don't forget to mark helpful answer
Sign in to comment

Thameur-BOURBITA 32,641

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

sharon mutzafi 21


Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   Home Server = *****2018

   * Identified AD Forest. 
   Done gathering initial info.


Doing initial required tests

   
   Testing server: Default-First-Site-Name\*****2018

      Starting test: Connectivity

         ......................... *****2018 passed test Connectivity



Doing primary tests

   
   Testing server: Default-First-Site-Name\*****2018

      Starting test: Advertising

         ......................... *****2018 passed test Advertising

      Starting test: FrsEvent

         ......................... *****2018 passed test FrsEvent

      Starting test: DFSREvent

         ......................... *****2018 passed test DFSREvent

      Starting test: SysVolCheck

         ......................... *****2018 passed test SysVolCheck

      Starting test: KccEvent

         ......................... *****2018 passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... *****2018 passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... *****2018 passed test MachineAccount

      Starting test: NCSecDesc

         ......................... *****2018 passed test NCSecDesc

      Starting test: NetLogons

         ......................... *****2018 passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... *****2018 passed test ObjectsReplicated

      Starting test: Replications

         ......................... *****2018 passed test Replications

      Starting test: RidManager

         ......................... *****2018 passed test RidManager

      Starting test: Services

         ......................... *****2018 passed test Services

      Starting test: SystemLog

         ......................... *****2018 passed test SystemLog

      Starting test: VerifyReferences

         ......................... *****2018 passed test VerifyReferences

   
   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : Schema

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

   
   Running partition tests on : Configuration

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

   
   Running partition tests on : ti****

      Starting test: CheckSDRefDom

         ......................... tikono passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... tikono passed test CrossRefValidation

   
   Running enterprise tests on : ti*****

      Starting test: LocatorCheck

         ......................... ti***** passed test LocatorCheck

      Starting test: Intersite

         ......................... ti***** passed test Intersite

sharon mutzafi 21 Reputation points

2023-01-30T22:00:15.83+00:00

two dc's.

one domain.
sharon mutzafi 21 Reputation points

2023-01-30T22:33:46.2233333+00:00

I'm just trying to get DFRS to work, i'm currently stuck on stage 2, and the replication occurs on the old FRS sysvol.
Thameur-BOURBITA 32,641 Reputation points

2023-01-30T22:51:21.8133333+00:00

the DC health seems ok.

I don't understand why you talk about volume creation?

Can you give us what action you did in domain controllers ?

Do you want move sysvol to another volume or folder?
sharon mutzafi 21 Reputation points

2023-01-30T22:51:54.05+00:00

If i delete the sysvol share, it shares it back instead of sharing the one under c:\windows\dfsr, as like the migration is still pending. there are no errors on the event viewer.
Thameur-BOURBITA 32,641 Reputation points

2023-01-30T22:52:21.5833333+00:00

@sharon mutzafi

How many domain controllers you have in your domain ?

And how many domain impacted by this issue?

Please don't forget to mark helpful answer as accepted
Thameur-BOURBITA 32,641 Reputation points

2023-01-30T22:52:49.2266667+00:00

Can you share with us the result of the command dcdiag ?

Anonymous

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--
Please sign in to rate this answer.
sharon mutzafi 21 Reputation points

2023-01-31T07:22:08.4633333+00:00

No they are not missing they are just working on FRS mode instead of DFRS. Thank you for answering.
Sign in to comment
Anonymous

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--
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

DFSR replication broken

5 additional answers