Hello All,
I'm in the process of moving my test environment DCs from 2016 to 2019. I have two VM domain controllers hosted on separate physical Hyper V servers. The 2016 DC's have been demoted and are gone. The issue I'm running into is that DC2 is still trying to connect to the previous PDC to replicate SYSVOL and nothing I have tired will force it to connect to the new PDC.
I have tried both non authoritative and authoritative synchronizations in that order. The authoritative reset did fix the last 2016 DC, allowing me to demote it cleanly, but not this dang 2019 DC2. I have also verified with PortQryV2 that RPC ports are open and available on both boxes as needed.
Steps I followed for sync resets - https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo
Old PDC = CDS-DC1
New PDC (OWNS ALL FSMO ROLES) = DC1
Broken DC = DC2
Current Status
c:\>For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state
DC1
ReplicatedFolderName ReplicationGroupName State
SYSVOL Share Domain System Volume 4
DC2
ReplicatedFolderName ReplicationGroupName State
SYSVOL Share Domain System Volume 2
DC2 logs the following Two events.
Event 5008, DFSR
The DFS Replication service failed to communicate with partner CDS-DC1 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: CDS-DC1.blah.blah
Optional data if available:
Partner WINS Address: CDS-DC1
Partner IP Address:
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 76EB5819-AAAB-4364-B519-281DD36FCD06
Replication Group ID: CD548712-603D-4A85-942B-A59FE9BF0884
AND
Event 4612, DFSR
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner CDS-DC1.blah.blah.
If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization
state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This
can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: C231A149-32D1-4409-BAD3-06D99FC984D4
Replication Group Name: Domain System Volume
Replication Group ID: 76EB5819-AAAB-4364-B519-281DD36FCD06
Member ID: DA048552-7291-48B2-A920-3702A6037E1D
Read-Only: 0
While the PDC logs the following
Event 5004, DFSR
The DFS Replication service successfully established an inbound connection with partner DC2 for replication group Domain System Volume.
Additional Information:
Connection Address Used: DC2.blah.blah
Connection ID: 50FC82BE-5A3D-428B-8606-811BAC3DF2EC
Replication Group ID: CD548712-603D-4A85-942B-A59FE9BF0884
AND
Event 5014, DFSR
The DFS Replication service failed to communicate with partner DC2 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: DC2.blah.blah
Optional data if available:
Partner WINS Address: DC2
Partner IP Address: blah.blah.blah.blah
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 50FC82BE-5A3D-428B-8606-811BAC3DF2EC
Replication Group ID: CD548712-603D-4A85-942B-A59FE9BF0884
AND Finally
Event 5008, DFSR
The DFS Replication service failed to communicate with partner DC2 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
Partner DNS Address: DC2.blah.blah
Optional data if available:
Partner WINS Address: DC2
Partner IP Address: blah.blah.blah.blah
The service will retry the connection periodically.
Additional Information:
Error: 1722 (The RPC server is unavailable.)
Connection ID: 50FC82BE-5A3D-428B-8606-811BAC3DF2EC
Replication Group ID: CD548712-603D-4A85-942B-A59FE9BF0884
After my third 3am bash against this I think I finally need to ask for some help. Why was CDS-DC2 fixed by the authoritative sync reset but DC2 isn't?