Forum Discussion
DFSR DC replication using wrong DC
We have a strange issue with a domain with 2 DC. Originally the domain had 2 DC name it DC1 and DC2. DC2 has been successfully demoted.and there was only DC1 remaining. Now a new DC, DC3, has been...
The demoted DC was DC2, I don't know which was holding the FSMO roles at that time.
For sure they were moved successfully.
I found this article, sorry if it's in italian, that explain how to solve it
Changing the parameter on the new DC "moved" the problem to the active DC that now reports that it has to replicate to the new DC.
We planned to perform an authorative syncronization on the former DC and a non-authorative sync on the new one
thanks
you can run repadmin /syncall / AeDp on you primary DC to make sure that the replication is healthy with no errors.
for the link you shared, this is a fix if your SYSVOL and NETLOGON are not healthy on your new DC after promotion
for the link you shared, this is a fix if your SYSVOL and NETLOGON are not healthy on your new DC after promotion
