• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 180
  • Last Modified:

Active directory upgrade to DFSR

There looks to be something wrong here.  I have a domain across 3 sites with 5 DCs. 3 of the DCs are 2008 R2 or Ent., the other 2 DCs are 2012 R2.  There do  not appear to be any problems with AD replication or DNS at this time. However, when I start the tool to migrate from FRS to DFS I see in the status that only 4 of the DCs are listed in the state results.  NLtest shows me all 5 DCs.  Here are the pastes.

C:\Windows\system32>nltest /dclist:grid.loc
Get list of DCs in domain 'grid.loc' from '\\CHEF.grid.loc'.
        CHEF.grid.loc [PDC]  [DS] Site: PPG-EDMS-Office
       Wendy.grid.loc        [DS] Site: SMSD
        Bebe.grid.loc        [DS] Site: SMSD
       Kenny.grid.loc        [DS] Site: SMTX
    MrHankey.grid.loc        [DS] Site: PPG-EDMS-Office

The command completed successfully

******************************************************************

PS C:\Users\administrator.GRID> dfsrmig /getmigrationstate

Unable to create DFSR Migration log file. Error 1307
The following Domain Controllers are not in sync with Global state ('Prepared'):

Domain Controller (Local Migration State) - DC Type
===================================================

WENDY ('Start') - Writable DC
BEBE ('Start') - Writable DC
KENNY ('Start') - Writable DC
MRHANKEY ('Waiting For Initial Sync') - Writable DC

Migration has not yet reached a consistent state on all Domain Controllers.
State information might be stale due to AD latency.

**********************************************************************
Anyone know why this is happening or what to fix?
0
billherde
Asked:
billherde
  • 2
  • 2
1 Solution
 
footechCommented:
I don't think it lists DCs that have reached the target state.

Also you should run from an elevated prompt to avoid "Unable to create DFSR Migration log file. Error 1307".
0
 
billherdeAuthor Commented:
The command was being run from CHEF, so that could be viable.  Anyone able to confirm?
0
 
billherdeAuthor Commented:
Well the migration continues through the steps and DCdiag /c /e tells me everything is healthy.  So I suppose it is good enough!  If it ain't broke.....
0
 
footechCommented:
I don't really see the point in using Chef for this, since it's an automation tool meant for repeated actions.  You wouldn't have to do this more than once in an environment.

All you really want to do is re-run dfsrmig /getmigrationstate until all the DCs show they're in the same state.  You don't even have to run it, it's just a safety check.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now