none
2016 Domain fucntional levels

    Question

  • Hi,


    We would like to upgrade our domain from 2008 R2 and go to 2016. I can't seem to find any official documentation on 2016 domain & forest functional levels, what the new features are, and any other requirements. We still have the odd 2003 server, all clients are Windows 7 and above, and some Linux serers around.


    I've reviewed the following or found them via searches, but they don't have any info post 2012r2.

    • https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/plan/security-best-practices/understanding-active-directory-domain-services--ad-ds--functional-levels?f=255&MSPPError=-2147217396
    • https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/windows-server-2016-functional-levels?f=255&MSPPError=-2147217396
    • https://technet.microsoft.com/library/understanding-active-directory-functional-levels(<g class="gr_ gr_913 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="913" id="913">ws</g>.10).aspx

    Has anyone got any more info, please?


    Tuesday, February 7, 2017 10:19 AM

All replies

  • The TechNet link is here for ADDS : https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/active-directory-domain-services


    Tuesday, February 7, 2017 10:24 AM
  • Hi

     You can check these ms articles;

    What's new in Active Directory Domain Services for Windows Server 2016

    https://technet.microsoft.com/en-us/windows-server-docs/identity/whats-new-active-directory-domain-services?f=255&MSPPError=-2147217396

    Windows Server 2016 Functional Levels

    https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/windows-server-2016-functional-levels

    Also for migrate to server 2016,current functional level needs to be at least server 2008 or higher.


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Tuesday, February 7, 2017 10:31 AM
  • Thanks, I've read through those already. What I'm looking for is this link, but updated with 2016 info. https://technet.microsoft.com/library/understanding-active-directory-functional-levels

    Also any minimum requirements for devices to communicate with 2016 DCs - will I break some of my Linux machines which use AD authentication, for example?

    Tuesday, February 7, 2017 10:45 AM
  • Thanks, I've read through those already. What I'm looking for is this link, but updated with 2016 info. https://technet.microsoft.com/library/understanding-active-directory-functional-levels

    Also any minimum requirements for devices to communicate with 2016 DCs - will I break some of my Linux machines which use AD authentication, for example?

    hi,

    if the forest functional level is 2003, you are able to add new domain controller on Windows 2016 , you don't need to raise your functional level to 2008 before adding the first DC 2016. 
    To add new domain controller under 2016 the forest functional level must be at least 2003 :

    you will get a message when you install the first domain controller on Windows 2016 to inform you that the level 2003 is deprecated , the same for FRS:

    Windows 2008 functional level is recommended functional level, it let you to avoid of any future DC on Windows 2003 (unsupported operating system) and let you to be able to migrate the FRS to DFS-R for sysvol replication.


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

    Tuesday, February 7, 2017 11:38 AM
  • Thanks, we are already on 2008 R2 functional level on our domain and forest. We will be updating all DCs to 2016 then raising the levels.

    My main concern is client compatibility




    • Edited by voyco Tuesday, February 7, 2017 11:55 AM
    Tuesday, February 7, 2017 11:53 AM
  • Thanks, we are already on 2008 R2 functional level on our domain and forest. We will be updating all DCs to 2016 then raising the levels.

    My main concern is client compatibility




    Windows 7 is compatible with domain controller Windows 2016.

    You if you have another application installed , you have to check with editor if it's compatible with domain controller 2016. For example, Exchange 2010 is not compatible with domain controller 2016. 


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

    Tuesday, February 7, 2017 1:30 PM
  • Is there a document/matrix regarding these systems that arent compatible, like Exchange 2010? We use Exchange 2013 anyway, but we do have old versions of SharePoint and various flavours of Linux that I need to be aware of.
    • Edited by voyco Tuesday, February 7, 2017 1:38 PM
    Tuesday, February 7, 2017 1:38 PM
  • Is there a document/matrix regarding these systems that arent compatible, like Exchange 2010? We use Exchange 2013 anyway, but we do have old versions of SharePoint and various flavours of Linux that I need to be aware of.

    Unfortunately , no document  for sharepoint compatibility.

    The best  is to test in test environment before if you can before perform upgrading you DC in you production environment.


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

    Tuesday, February 7, 2017 2:07 PM
  • Unfortunately, it would be impossible to test the many different clients and applications we have. I was hoping that TechNet would just have a decent article, like they did with 2008 and 2012, outlining the 2016 domain functional level, and any minimum requirements, and compatibility considerations.


    • Edited by voyco Tuesday, February 7, 2017 2:13 PM
    Tuesday, February 7, 2017 2:12 PM
  • Unfortunately, it would be impossible to test the many different clients and applications we have. I was hoping that TechNet would just have a decent article, like they did with 2008 and 2012, outlining the 2016 domain functional level, and any minimum requirements, and compatibility considerations.


    The Technet documentation helps but it's not enough , it is recommended to not touch the production environment before validating the configuration in a test environment.
    You should also contact the vendors or Editor of your applications for their confirmation on compatibility with the new version.


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/



    Tuesday, February 7, 2017 2:31 PM
  • Thanks, we are already on 2008 R2 functional level on our domain and forest. We will be updating all DCs to 2016 then raising the levels.

    My main concern is client compatibility




    This article realted to "Supported Windows guest operating systems for Hyper-V on Windows Server 2016" but a reference for client OS for Server 2016;

    https://technet.microsoft.com/windows-server-docs/compute/hyper-v/supported-windows-guest-operating-systems-for-hyper-v-on-windows

    for other OS you can check Multi Vendor Support Community ; http://www.tsanet.org/


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Tuesday, February 7, 2017 6:33 PM
  • Hi,

    Just checking in to see if the information provided was helpful. And if the replies as above are helpful, we would appreciate you to mark them as answers, please let us know if you would like further assistance.

    Best Regards,

    Wendy


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

    Monday, February 13, 2017 9:41 AM
    Moderator
  • Thanks, we are already on 2008 R2 functional level on our domain and forest. We will be updating all DCs to 2016 then raising the levels.

    My main concern is client compatibility




    Windows 7 is compatible with domain controller Windows 2016.

    You if you have another application installed , you have to check with editor if it's compatible with domain controller 2016. For example, Exchange 2010 is not compatible with domain controller 2016. 


    Please don't forget to mark the correct answer, to help others who have the same issue. Thameur BOURBITA MCSE | MCSA My Blog : http://bourbitathameur.blogspot.fr/

    Just wanted to note that Exchange 2010 can now be used with 2016 FFL/DFL domain controllers, thanks to updates for Exchange 2010:

    https://blogs.technet.microsoft.com/rmilne/2018/06/21/exchange-2010-support-for-windows-server-2016-domain-controllers/

    Friday, November 30, 2018 5:28 PM