beddoMemberJun 23, 2017 at 9:52 am #167084
So I had a server blow up AD last night, it lost some registry keys that I was able to recreate then let it repair.
This server is now inconsistent in its FRS to DFRS migration state. The network was migrations years ago.Quote:dfsrmig /getglobalstate
Current DFSR global state: ‘Eliminated’
The following Domain Controllers are not in sync with Global state (‘Eliminated’):
Domain Controller (Local Migration State) – DC Type
****** (‘Preparing’) – Primary DC
Migration has not yet reached a consistent state on all Domain Controllers.
State information might be stale due to AD latency.
If I run the same on the second domain controller I get:Quote:C:Usersdolphinict>dfsrmig /getmigrationstate
Unable to create DFSR Migration log file. Error 1307
Unable to connect to the PDC emulator. Make sure that the
PDC is reachable and retry the command later.
I’m assuming this is going to cause problems – if one DC is using an ancient copy of FRS and the other the current DFRS then nothing good can come of it. I don’t want to roll back the migration and re-run it incase it over-writes the current DFRS with an old FRS. Anyone got easy steps to knock the out of sync DC back into the state it should be in?
The FRS service has been stopped since May 2014 and dcdiag is throwing errors about FRS information missing and indeed there is only SYSVOL_DFRS so effectively I just need to tell the server to use DFRS without going through the migration process…
You must be logged in to reply to this topic.