Following a step by step from techcommunity.microsoft.co
m, which closely matches a few other step by steps guides I was reviewing at the same time for consistency.
All health checks passed on all DCs prior to initial step "dfsrmig /setGlobalState 1".
(execept 'expected' errors when running the health checks on 2012R2 DCs using FRS for sysvol replication - and yes this should have happened when we first migrated to 2012R2 DCs, but apparently that step was overlooked) I ran the following checks:
- dcdiag /e /c /d /v
- dcdiag /e /test:sysvolcheck /test:advertising
It's been 18+ Hrs since then, and all except one of the DCs moved into the global state 'prepared' as expected except one, which is still stuck at "Writeable DC".
Locally, the sysvol folders appear to have replicated properly:
SysVols> Local State = 1
I have found a few other online posts with this issue, and they all seem to refer to the same solution, but without a lot of detail, and what they've described seems to fit my situation. They refer to the following in ADSIEdit:
under CN=<servername>,OU=Domain Controllers,DC=<domain>,DC
=local with some DFSR Entrys.
They talk about deleted the "corresponding replications" for this server with the dfs administration tool.
and finally after the CN=DFSR-LocalSettingsCNF:<
was empty in ADSIEdit, they delete it. (I assume from ADSIEdit).
Here is an image showing how my situation in ADSI Edit appears similarly inconsistant:
So, my questions are:
- How do I know what is the "corresponding replications"? in DFS Management?
- Does this look like I'm on the right track or is there a better way to target this issue?