Hmm, you just describe the exact method I used. It let me set up a 2019 server and add it to a 2003 forest, now I have to start from scratch.
Sysvol replication error 6408 on server 2019
I keep getting an error 6408 on my domain controllers. I have tried multiple ways of disabling the file replication services and forcing it to replicate through authoritative and non-authoritative means. when I have everything disabled and I run repadmin it comes back with no errors but as soon as I start the service back up I get error 6408 again.
ERROR:
The DFS Replication service failed to initialize replicated folder C:\Windows\SYSVOL because the service detected that one of its private folders overlaps with an existing replicated folder. This is an unsupported configuration.
Additional Information:
Overlapped Folder 1: C:\Windows\SYSVOL\staging areas\morrismfg.local
Replicated Folder 1: C:\Windows\SYSVOL
Replicated Folder 1 Name: SYSVOL Share
Replicated Folder 1 ID: 43B28239-B9C8-46C4-8708-78E4DB6E3A17
Replication Group 1 Name: Domain System Volume
Replication Group 1 ID: 9AC17A3E-FD82-4BCC-B2E8-037A6FD4A0B0
Member1 ID: 330F0D83-6AB5-4EFB-882A-CB62A80DF17A
Overlapped Folder 2: C:\Windows\SYSVOL
Replicated Folder 2: C:\Windows\SYSVOL
Replicated Folder 2 Name: SYSVOL Share
Replicated Folder 2 ID: 43B28239-B9C8-46C4-8708-78E4DB6E3A17
Replication Group 2 Name: Domain System Volume
Replication Group 2 ID: 9AC17A3E-FD82-4BCC-B2E8-037A6FD4A0B0
Member2 ID: 330F0D83-6AB5-4EFB-882A-CB62A80DF17A
14 answers
Sort by: Most helpful
-
-
Anonymous
Jun 21, 2022, 5:09 PM As mentioned, that should not have been possible but regardless it sounds like your only hope is to restore from a backup, do the prerequisites and try again.
--please don't forget to
upvote
andAccept as answer
if the reply is helpful-- -
Jeff Rowe 96 Reputation points
Jun 21, 2022, 6:03 PM Restore a backup of a corrupted system, not much point. If I can't get what I have working then it's start all over from scratch and build it right.
-
Anonymous
Jun 21, 2022, 6:06 PM We've no idea, but if it was corrupt before the 2019 domain controllers were added then this just adds complication. Please don't forget to close up the thread by