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 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. The replicated folder will remain in the initial synchronization state until it has replicated with its partner. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL_DFSR\domain and is waiting to perform initial replication. So, the main items to focus on are errors 4612, 5002, and 5012. I don't see the warning 5014 as symptomatic, as I read it can simply show in there from backups processing. So, the DFS Replication event logs show DFSR event ID errors 4612, 5002, 5012 as well as warning 5014. That's what I need help fixing, if someone would be so kind. Well, after looking in Group Policy Management and switching between the different domain controllers, I can see they're not in sync, which means SYSVOL (DFSR) isn't replicating right. Anyhow, I saw the change getting picked up by some domain computers and not others, and flip flopping back and forth essentially. Recently, I made a GPO change, which I don't do too often. Everything authenticates fine, AD items replicate fine, dcdiag comes up clean (other than a few event log items I'd expect), and repadmin shows everything is replicating fine.
I really didn't think much of it because (most) everything is working as it was. A week and a half ago, in a panic, I did a Veeam restore of my domain controllers. I'll spare you the full backstory, but the gist of what is going on is this. Looking for an AD guru to help me out here.
0 kommentar(er)
