Verification of replica failed server 2022

Question

I am currently working on migrating from Windows Server 2012 R2 as the Domain Controller to Windows Server 2019. Both Windows Server OS running on VMware ESXi 7.0. When I try to add the Windows Server 2019 as domain controller, below error message display:

Verification of replica failed. The forest functional level is not supported. To install a Windows Server 2019 domain or domain controller, the forest functional level must be Windows Server 2008 or higher.

Verification of replica failed server 2022

I have executed the command Get-ADForest on the Windows Server 2012 R2 domain controller, and the output for ForestMode is Windows2003Forest.

I have inserted the Windows Server 2012 R2 ISO into the virtual drive to execute ADprep /forestprep command, but I got a message:

Forest-wide information has already been updated
Adprep did not attempt to rerun this operation.

Verification of replica failed server 2022

How do I force the Forest Prep to rerun?

Solution

If you have a Windows Server 2012 R2 Domain Controller, then the Forest Prep and Domain Prep have already been done for Windows Server 2012 R2. If you have no Windows Server 2003 domain controllers, you can raise the domain and forest functional levels.

Step 1: Update the forest and domain functional levels as high as it will let you.

Step 2: Migrate SYSVOL replication from FRS to DFSR.

Step 3: Add a Windows Server 2019 DC as a domain controller.

Reference

Windows Server > Storage at Microsoft > Streamlined Migration of FRS to DFSR SYSVOL

  • Home
  • Windows
  • Windows Server

Posted by discoveranother2

Hi all,

Have a Windows 2012R2 Server and getting ready to transfer FSMO roles to a new Windows 2019 server.

Have completed successfully the FRS to DFSR on the 2012R2 and both the Domain and Forest Functional Levels show as Windows 2012R2.

However, when trying to add the Windows 2019 domain controller to the existing domain, get the following error :-

Verification of replica failed server 2022

Any help much appreciated.

4 Replies

  • Verification of replica failed server 2022

    thai pepper

    Windows Server Expert

    • check 15 Best Answers
    • thumb_up 60 Helpful Votes

    That error usually means that switches from FRS to DFS-R has not been completed.  What does it say if you running the following command -- is the state 'Eliminated'?

    Batchfile

    dfsrmig /getmigrationstate
    

    Was this post helpful? thumb_up thumb_down

  • Verification of replica failed server 2022

    Da_Schmoo

    Verification of replica failed server 2022

    This person is a verified professional.

    Verify your account to enable IT peers to see that you are a professional.

    mace

    Windows Server Expert

    • check 151 Best Answers
    • thumb_up 707 Helpful Votes

    Are you really sure your forest level is at 2008 or higher?  Forest level is a different setting than domain function level.  Both have to be 2008 or higher.

    Powershell:

    get-adforest | fl Name,ForestMode

    Was this post helpful? thumb_up thumb_down

  • Verification of replica failed server 2022

    Da_Schmoo wrote:

    Are you really sure your forest level is at 2008 or higher?  Forest level is a different setting than domain function level.  Both have to be 2008 or higher.

    Powershell:

    get-adforest | fl Name,ForestMode

    Thanks for the reply. I did actually discover the error shortly afterwards but not what I expected, but awaited any replies in the meantime.

    The Forest and Domain levels were both Windows 2012R2 after confirming. I downgraded both to Windows 2008 and it worked !!!

    0 of 1 found this helpful thumb_up thumb_down

  • Verification of replica failed server 2022

    EminentX

    Verification of replica failed server 2022

    This person is a verified professional.

    Verify your account to enable IT peers to see that you are a professional.

    habanero

    Windows Server Expert

    • check 29 Best Answers
    • thumb_up 110 Helpful Votes

    discoveranother2 wrote:

    Da_Schmoo wrote:

    Are you really sure your forest level is at 2008 or higher?  Forest level is a different setting than domain function level.  Both have to be 2008 or higher.

    Powershell:

    get-adforest | fl Name,ForestMode

    Thanks for the reply. I did actually discover the error shortly afterwards but not what I expected, but awaited any replies in the meantime.

    The Forest and Domain levels were both Windows 2012R2 after confirming. I downgraded both to Windows 2008 and it worked !!!

    You should not have downgraded FFL/DFL to 2008. Keep FFL/DFL higher as much as you can. As noted, You should be made sure FRS is migrated to DFSR successfully. 

    Was this post helpful? thumb_up thumb_down

How do I fix Active Directory replication issues?

If AD DS cannot be removed normally while the server is connected to the network, use one of the following methods to resolve the problem: Force AD DS removal in Directory Services Restore Mode (DSRM), clean up server metadata, and then reinstall AD DS. Reinstall the operating system, and rebuild the domain controller.

How do I know if I have FRS or DFS?

How to verify the SYSVOL replication state (FRS or DFSR).
Logon to TMDC01 as Administrator..
Open an Administrative Command Prompt..
Type Dcdiag /e /test:sysvolcheck /test:advertising >c:\sysvolcheck..

When was FRS deprecated?

Since then, Microsoft released the Distributed File System Replication (DFSR) and deprecated FRS. This change occurred between Windows Server 2003 to 2008 and a lot of people missed this step of the upgrade process.

How do I force a server to replicate?

Using a graphical user interface Open the Active Directory Sites and Services snap-in. Browse to the NTDS Setting object for the domain controller you want to replicate to. In the right pane, right-click on the connection object to the domain controller you want to replicate from and select Replicate Now.