DFSR Migration Issue Server 2016

Question

So I have 2 DCs, which were both Server 2012r2.
I was able to update them 2016, but forgot to migrate to DFSR then. So I have tried the migration, but I have an empty SYSVOL_DFSR on one DC.

When I run dfsrmig /getglobalstate, they both state that they are in the elimitated state.

However, ARV_PDC at least has a populated SYSVOL_DFSR, has the following log event:

DFSR has detected that the SYSVOL migration global state is set to 'Eliminated' and the current local state is 'Waiting For Intial Sync'. DFSR has started the transition to global state 'Eliminated'. You should see an event when the transition to state 'Eliminated' is complete.

While ARV-BDC, the other DC has this events:

The DFS Replication service successfully established an inbound connection with partner ARV_PDC for replication group Domain System Volume.

...however, like I said, an empty SYSVOL_DFSR[136705-dcdiag-arv-pdc.log][1][136619-dcdiag-arv-bdc.txt][2]
Possible Solution:
Could I demote the issued DC and then promote it again?

Answer 1

ARV_PDC should have own static ip address (192.168.111.207) listed for DNS, then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

ARV-BDC should have own static ip address (192.168.111.203) listed for DNS, also remove the public DNS addresses from connection properties then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

I did not look further since these are show stoppers. If problems persist then put up a new set of files to look at.

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

Answer 2

Hello Dennis W

Unfortunately this is a common scenario when migrating DC2012 to DC2016, and the outcome of the troubleshooting may very from "very promising" to "will need to rebuild". Worth the try.

First off I would recommend yo run some DCDIAG in order to see the communication in your environment and ensure that things look ok for all sides on infrastructure level. Then install DFS Management console in one of them in order to provide you with wider set of tools and health checks.

If nothing relevant come from this analysis: Yes, the best idea is to remove the conflict DC and promote again. After the new promotion, run a Force Synchronization as in: https://learn.microsoft.com/en-US/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization

------------------------------------------------------------------------------------------------------------------------------------

Hope this helps with your query,
--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt

then put unzipped text files up on OneDrive and share a link.