Server 2012 to Server 2019 Active Directory Failure - FRS is deprecated

Before promoting 2019 to a DC you have to migrate from FRS to DFSR.
https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405

Yes - thank you. This is the problem. If you review the "migration-state.txt" it shows where the process has stopped. Originally I had all three sitting in the ('Waiting For Initial Sync'). It has been here for several hours. Everything appears and looks to test fine. Thoughts?

--> It has been here for several hours
You have to wait till all DCs reach the same state.

And if I have left it for more than 24 hours? Mid sized company. I can't see any errors. Is there any additional logs of the progress that I can monitor other than what I have included above?

What OS are all of the DCs? It looks like DC2 is still waiting for sunc. Is it Windows 2019? If it is, demote it. Then the FRS to DFSR migration should proceed.

If DC2 is <= 2016 build 1603, then there are other issues. It might be best to demote it anyway.

Thank you. Looks like I have some issues to deal with. Just wondering what the best course of action here would be given these errors. Should I be deleting the NTDS connections and restoring from the primary domain controller to overwrite/rebuild to the other DC's?

......................... DC2 failed test FrsEvent
......................... DC2 failed test SystemLog
......................... DC2 failed test VerifyEnterpriseReferences
......................... DC4 failed test FrsEvent
......................... DC4 failed test VerifyEnterpriseReferences
......................... DC16 failed test FrsEvent
......................... DC16 failed test VerifyEnterpriseReferences

      Starting test: FrsEvent

         * The File Replication Service Event log test 
         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems. 
         An error event occurred.  EventID: 0xC00034F0

            Time Generated: 03/28/2020   00:40:34

            Event String:

            The File Replication Service is unable to add this computer to the following replica set: 

                "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" 

             

            This could be caused by a number of problems such as: 

              --  an invalid root path, 

              --  a missing directory, 

              --  a missing disk volume, 

              --  a file system on the volume that does not support NTFS 5.0 

             

            The information below may help to resolve the problem: 

            Computer DNS name is "DC2.domain.ca" 

            Replica set member name is "DC2" 

            Replica set root path is "c:\windows\sysvol\domain" 

            Replica staging directory path is "c:\windows\sysvol\staging\domain" 

            Replica working directory path is "c:\windows\ntfrs\jet" 

            Windows error status code is  

            FRS error status code is FrsErrorMismatchedJournalId 

             

            Other event log messages may also help determine the problem.  Correct the problem and the service will attempt to restart replication automatically at a later time.

         An error event occurred.  EventID: 0xC00034F3

            Time Generated: 03/28/2020   00:40:34

            Event String:

            The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed: 

             

             Recovery Steps: 

             

             [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window: 

             

                net stop ntfrs 

                net start ntfrs 

             

            If this fails to clear up the problem then proceed as follows. 

             

             [2] For Active Directory Domain Services Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled: 

             

            If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. 

             

            If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary. 

             

            If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative. 

             

             

             [3] For Active Directory Domain Services Domain Controllers that host DFS alternates or other replica sets with replication enabled: 

             

             (3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location. 

             (3-b) If this server is the only Active Directory Domain Services Domain Controller for this domain then, before going to (3-c),  make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for 

            Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS. 

             (3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. 

             (3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published. 

             

             

             [4] For other Windows servers: 

             

             (4-a)  If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location. 

             (4-b)  net stop ntfrs 

             (4-c)  rd /s /q  c:\windows\ntfrs\jet 

             (4-d)  net start ntfrs 

             (4-e)  Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time). 

             

            Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members.

         ......................... DC2 failed test FrsEvent

Select allOpen in new window

      Starting test: SystemLog

         * The System Event log test
         An error event occurred.  EventID: 0x0000272C

            Time Generated: 03/28/2020   15:08:38

            Event String:

            DCOM was unable to communicate with the computer 1.0.0.1 using any of the configured protocols; requested by PID     21d4 (C:\Windows\system32\dcdiag.exe).

         An error event occurred.  EventID: 0x0000272C

            Time Generated: 03/28/2020   15:08:38

            Event String:

            DCOM was unable to communicate with the computer 1.1.1.1 using any of the configured protocols; requested by PID     21d4 (C:\Windows\system32\dcdiag.exe).

         An error event occurred.  EventID: 0x0000272C

            Time Generated: 03/28/2020   15:08:39

            Event String:

            DCOM was unable to communicate with the computer 199.166.6.2 using any of the configured protocols; requested by PID     21d4 (C:\Windows\system32\dcdiag.exe).

         An error event occurred.  EventID: 0x0000272C

            Time Generated: 03/28/2020   15:09:00

            Event String:

            DCOM was unable to communicate with the computer 209.239.11.98 using any of the configured protocols; requested by PID     21d4 (C:\Windows\system32\dcdiag.exe).

         ......................... DC2 failed test SystemLog

Select allOpen in new window

kevinhsieh: All DCs are Server 2012 R2. Trying to introduce the first Server 2019 gave the error.

If DC2 is 2012 R2
Please check this
https://community.spiceworks.com/topic/1138813-dfsr-migration-stuck

What OS is DC2? It is having problems migrating.

@MAS: I came across this one in my search as well. I do not have an empty directory.

Well I have migrated successfully to DFRS. To the best of my knowledge I believe that there was some stale objects that I identified in DFS Management. Once these cleared out and a bunch of other stuff that I don't think corrected it (forcing replication, stepping stages back and forth, etc.).

Glad to know you sorted outed and thanks for sharing what you did. :))