Task Category: Knowledge Consistency Checker Source: Microsoft-Windows-ActiveDirectory_DomainService Hoping to get some help by pointing me to the right PatrickĪfter trying your recommendation in the test environment, it seems like I have now lost access to DC2 and getting the error below: Not sure if I can use the same domain name or how the existing computers would work without rejoining them to the new domain if ever. (I did try this before but DC2 wouldn't sync to the new DC3)Ģ) Create a new forest in a new DC and migrate the existing domain to it. Problem with this though is that all home profiles and GPOs link back to DC1. After which we can add a new DC3 running Windows Server 2016 DC and make it primary. Possible solutions I can think of and as per research:ġ) Demote DC1 and do metadata cleanup.
#Echofon pro not syncing how to#
Not sure if this would have an impact to how AD works but I did set the NIC priority manually.Ģ) DC1 is a file server and all home profiles and GPOs points back to it.ġ) How to confirm which DC is healthy and up-to-date? I assume my suspicions are correct but I'm not an expert.Ģ) How to search for clues to determine root cause and the next course of action? I create a file/folder on either side and it doesn't sync)ġ) DC1 has 2 NICs and 2 IPs on 2 different VLANs because we use it as a file server as well. I suspect that our DC1 is not syncing to our DC2 due to the reasons below:ġ) When DC2 is down or offline, no one can authenticate.Ģ) Netlogon is paused and Windows Time service stopped.ģ) Sysvol folder of DC1 and DC2 are not in sync on both sides (e.g. We have 2 VM DCs in our domain where the main is DC1 running on Windows Server 2008 R2, and our secondary DC2 running on Windows Server 2012. Primary DC1 (unhealthy) is not syncing to Secondary DC2 (healthy)
0 kommentar(er)
