Exch 2007 SP1--> can I have Server2016 DC on network if I don't update functional levels? RRS feed

  • Question

  • Working with a client that has Exchange 2007 SP1 running on a Windows 2008 w/SP2 (Not R2) domain controller

    Domain and forest functional levels are 2008

    I know it's nowhere near supported (I could just stop here after not supported...) to upgrade domain and forest functional levels until after Exch 2010 SP3RU22, but can I add a Server 2016 domain controller if I leave the functional levels at 2008? I can't find an answer to that specific scenario. I've seen "can't have 2016 domain controller" but does that assume the functional levels would be raised?

    We want to add redundancy for the DCs before we get the mail moved to O365, move printers and files off the old Exch07 server.

    If I can have a 2016 DC, next question, can I have that server hold the FSMO roles or must they be on the 2008 server? Seems to me that it shouldn't matter if the functional levels are held back.

    Thanks in advance!


    Friday, September 14, 2018 9:02 PM

All replies

  • I think you should be able to install the windows 2016 Domain Controller in functional level 2008 but you will not be able to use the advance features.

    Please mark as an answer if this answers your question .


    MCSE Exchange 2013, MCSA 2012 Server MCTS Exchange 2007,

    2010, MCITP Exchange 2007, 2010 MCSE 2003 Server,

    MCSA Exchange 2003 ITIL V3 Foundation


    This posting is provided AS IS with no warranties and confers no rights.

    Saturday, September 15, 2018 11:35 AM
  • That's what I was thinking too, if they were just DCs and didn't upgrade the forest of domain, but by just adding the DCs the schema will probably get updated.

    Was hoping someone else with old stuff may have been through this. 

    Thursday, September 20, 2018 2:33 PM
  • I suspect not.  Although there's no longer a published supportability matrix, Exchange 2010 is only supported with 2016 DCs when it's updated to the latest update rollup. 


    Seriously, upgrade.

    Exchange 2007 reached end of life on April 11th 2017. What’s your plan to move?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Sunday, September 23, 2018 9:51 PM
  • Thanks Ed, I noted there's no 2016 support in the original post.

    The plan is to move them off, just getting the pieces in the right order. Since this forum exists for old versions I figured I would give it a go to see what the community has run into if anyone had tried it.

    Monday, September 24, 2018 2:40 PM
  • The right order would be to upgrade Exchange to a supported version, which in your case would be 2013 to start.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, September 25, 2018 2:14 AM