Yesterday while doing migration on SBS 2011 to 2019 we executed dfsrmig /setglobalstate 1 and after some time and troubleshooting of firewall on sbs it showed prepared, but today when going to dfsrmig /setglobalstate 2 we ran dfsrmig /getmigrationstate it is again showing
The following domain controllers have not reached Global state ('Prepared'):
Domain Controller (Local Migration State) - DC Type ===================================================
ULSECDOMAIN ('Start') - Writable DC
Migration has not yet reached a consistent state on all domain controllers. State information might be stale due to Active Directory Domain Services latency.
Why did it changed the status back?
Before we can actually tell why this happens you need to see if there are issues in the event logs related to FRS on any of your Domain Controllers.
In the secondary domain we have FRS error
The File Replication Service is having trouble enabling replication from ULSERVER to ULSECDOMAIN for c:\windows\sysvol\domain using the DNS name ULSERVER.ulaser.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
I think you mean 'Domain Controller' instead of 'Domain', you only have one Domain but multiple Domain Controllers.
Can you list the host names of the domain controllers and what OS is installed?
Yes we have 2 domain controllers in the same domain, the DC named Ulserver is the primary DC with SBS 2011 on it and ULSecdomain is secondary DC with OS 2016 on it.
Did you install the DC with Windows Server 2016 on it as a migration target?
No the Windows Server 2016 DC is an old secondary DC we have on our network running for quite some time.
For migration purpose we have installed a new Server 2019 machine.
OK, thank you. On both servers there is a 'File Replication Service' log, see screenshot. Save the logs at both servers, zip them and add them to your reply. In addition to this tell me what antivirus software and/or firewall you have running?
Have attached zip files for both the server.
You should have migrated NTfrs to DFS before you implemented that Windows Server 2016 Domain Controller. The logs show that there already are problems for a longer time, at least since 10/15/2019. The question is now how we solve the issue. I would roll back DFSR migration, demote the 2016 server, cleanup DNS records and restart migration of FRS to DFSR.