Helping a client with their 2x 2012 Domain Controllers.
Their DC1 which holds the FSMO roles had Event Error 4012, DFSR: That it had dropped replication of the SYSVOL\domain path as its been disconnected for X amount of days.
I executed KB 2218556 to make DC1 non-authoritative - ran all needed steps. I didn't get the needed Event in Event Viewer showing that replication had succeeded. However when creating user objects in AD Users and Computers they replicate to the other DC?
I looked on DC2 and found Event Warning 2213 DFSR: The DFS Replication service stopped replication on volume c: This occurs when a DFSR JET database is not shut down cleanly... Looking online a microsoft article recommended doing KB 2218556 to make DC2 authoritative because DC1's event viewer for DFS Replication was showing that it was still waiting to perform initial replication.
Did this and waited for 1 hour and never saw Event ID 4602 in the DFSR event log on DC2 indicating SYSVOL has been initialized. I then ran the WMIC command In Event 2213 to continue replication and soon after this DC2 had the error DC1 had: Event Error 4012, DFSR: That it had dropped replication of the SYSVOL\domain path as its been disconnected for X amount of days.
So I then execute KB 2218556 to perform a non-authoritative synchronization of DFSR-replicated SYSVOL. waited for another 30 mins or so. Both DCs were stuck on the DFSR event warning 4614 that the DFS Replication service initialized SYSVOL and is waiting to perform initial replication. So it seemed both were waiting for the other! No Event 4604 per the Microsoft KB.
I didn't know what to do at this point so restarted DFSR on both of them. After a number of informational DFSR messages DC1 came up with Event ID 1206 that DFS Replication service successfully contacted domain controller DC1. Nothing about DC2 (I noticed that DC1's primary DNS server was itself and DC2 was the secondary one - maybe that's why?).
DC2's DFSR event log eventually indicated Event 5014 that DFSR is stoping communication with partner DC1 for replication group Domain System Volume due to an error, the service will retry the connection periodically. Then Event ID 5004 which stated that DFS Replication service successfully established an inbound connection with partner DC1 for replication group Domain System Volume.
During this entire time, creating test AD Users in AD Users and Groups has them replicate to either DCs as they show up very rapidly in AD Users and Groups on both. Also running repadmin /showrepl and repadmin /replsummary, both show successful replication.
However, when running the DFS Management Diagnostic Report, the Propogation Test Succeeds, but the propogation report shows two tests complete and the health report for both DCs still says "This member is waiting for initial replication for replicated folder SYSVOL Share".
Checking back today 9 hours later, the Event IDs haven't changed from the above and the DFS Management Diagnostic reports are still the same as above.
So I can create users and replicate back and forth but I have the above errors. I don't know what to at this point. Thanks.