In our environment we have 23 DCs, 2 of which are RODC. When I run dcdiag /v /c /d /s:corpmdcp04 >c:\dcdiag.txt all test results are ok except for "VerifyEnterpriseReferences" test that fails. What's more; please note the conflicting nTDSConnection in the FRS test.

All DCs are running WinSrv2K8R2 SP1 Standard x64. All DCs are GCs.

DFL is Windows Server 2008 R2 & FFL is Windows Server 2008 R2

All the mentioned DCs in the DCDIAG output are active DCs, and non of them has been deleted.

The current DFSR global state is: Start

Should I initiate the migration using the following commands, if not, then how do I fix this?

Per your FSMO roles... If you broke them out on different boxes because your environment is huge (100+﻿ DCs), go ahead and break them out. If you have less than 100 in your forest, don't break them out. Put all your FSMO roles on one box. But make sure your other DC(s) are marked as Global Catelog. You can find that out by using LDP.exe, click on Connection, choose Connect, type in the server name, click ok. Look at the bottom for the output, you should see 1> isGlobalCatalogReady: TRUE .... If you want to leave the FSMO roles broke out, you should really have the forest roles on 1, and domain roles on 2 (both are Global Catalog because the infrastructure master needs to be on a GC, but you don't want to put it with the forest roles when they're broke out necessarily). Refer to the following article to put things into perspective with the breakout... I would start there just to make sure everything is in order before people start digging in deeper.

Thank you for your reply, but as I have mentioned that we have 23 DCs, and all of them are GCs. What's more; the FSMO roles are distributed between 2 DCs that are GCs. The current placement of the FSMO roles shouldn't be an issue since that all DCs are GCs...