locked
Failure to promote 2019 Core server to Domain Controller - The forest funtional level is not supported RRS feed

  • Question

  • I get the following message

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

    Very well, except my forest functional level is 2008 R2.

    I realized that one problem could be DFS sysvol replication, so I migrated that prior.

    The migration finished, and I am flummoxed.  I only have two DCs in this environment a Windows Server 2012 DC, and a 2008 R2 DC.

    ADSI edit, and investigation into Active Directory show no objects under Domain Controllers other than these.

    Any ideas?

    Thursday, May 16, 2019 9:54 PM

Answers

  • Might also check;

    Get-ADForest

     Yeah, this prompted the discovery of the ADdomain level of 2003, then I went to ADDS and found that I had not raised it there.  Once I raised it, there was no problem.

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    • Marked as answer by DZ Wood Friday, May 17, 2019 1:46 PM
    Friday, May 17, 2019 1:14 AM
  • Might also check;

    Get-ADForest

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by DZ Wood Friday, May 17, 2019 1:14 AM
    Thursday, May 16, 2019 11:06 PM

All replies

  • Might also check;

    Get-ADForest

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by DZ Wood Friday, May 17, 2019 1:14 AM
    Thursday, May 16, 2019 11:06 PM
  • Might also check;

    Get-ADForest

     Yeah, this prompted the discovery of the ADdomain level of 2003, then I went to ADDS and found that I had not raised it there.  Once I raised it, there was no problem.

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    • Marked as answer by DZ Wood Friday, May 17, 2019 1:46 PM
    Friday, May 17, 2019 1:14 AM
  • Good news, glad to hear of success.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Friday, May 17, 2019 1:26 AM
  • Hi,

    Thanks for your post in our forum.

    I am glad to know that your issue has been resolved.

    If you have any questions or requirements, please feel free to contact us.

    Thanks again for your understanding and support.

    Best Regards,

    Otto 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 17, 2019 5:51 AM