SOLVED

windows 2008r2 in a 2016 domain and forest

Brass Contributor

HI,
I have question about windows 2008r2 and windows 2016 forest and domain level features.
I currently have two dc's with 2008r2 domain capabilities and windows 2016 os.
Now I want to put a third dc with windows server 2022 and upgrade domain and forest level to windows 2016.
There are windows 2008r2 servers in my domain.
Will upgrading the domain and forest to windows 2016 cause problems for these servers?
Does Windows 2008r2 work correctly in a 2016 domain and forest?

Thank you

6 Replies
best response confirmed by pazzoide76 (Brass Contributor)
Solution

Absolutely is not a problem.    

     

The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR              

             

I'd use dcdiag / repadmin tools to verify health `correcting all errors found` before starting `any` operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.            

                 

 

        

 

 

@pazzoide76 you're welcome, please don't forget to mark helpful replies.     

    

 

HI,
I meant that the current ds have windows 2016 operating system and 2008r2 domain and forest level.
There are windows 2008r2 member servers in the domain.
Will my windows 2008r2 member server continue to validate correctly once I put a windows 2022 dc and upgraded the domain and forest level to windows 2016?
Will there be problems with these member servers?
Thank you

Greetings

Absolutely not a problem.   

  

thank you
1 best response

Accepted Solutions
best response confirmed by pazzoide76 (Brass Contributor)
Solution

Absolutely is not a problem.    

     

The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR              

             

I'd use dcdiag / repadmin tools to verify health `correcting all errors found` before starting `any` operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.            

                 

 

        

 

 

View solution in original post