none
Domain Controllers on different OS versions RRS feed

  • Question

  • Currently we have 3 Domain Controllers running our Active Directory.  One is running Windows Server 2016 and two are running Windows Server 2012 R2.  Our domain functional level is at 2012 R2 and we need to keep it at that for a while longer.  We also just purchased two new domain controllers that we are ready to setup and add into our environment.  

    We need to get the two new ones up and running before I can upgrade the two that are running 2012 R2.  Can I install Windows Server 2019 on the two new ones?  Will it work to have domain controllers running 2012 R2, 2016, and 2019?

    Thursday, January 23, 2020 4:04 PM

Answers

  • Yes - you can deploy WS 2019 domain controllers into the existing domain. This is fully supported.

    Note that the promotion of the new domain controllers will automatically include forest/domain prep - you have the option of performing these prep steps separately.

    This process is pretty much the same as the one you are already familiar with (since you deployed WS 2016 domain controllers). Details at https://www.petenetlive.com/KB/Article/0001262

    hth
    Marcin


    • Edited by Marcin PolichtMVP Thursday, January 23, 2020 4:15 PM
    • Marked as answer by WSUAL2 Thursday, January 23, 2020 5:07 PM
    Thursday, January 23, 2020 4:10 PM
  • Yes, not a problem, the two prerequisites to introducing the first 2019 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
    https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

     

     



    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 WSUAL2 Thursday, January 23, 2020 5:07 PM
    Thursday, January 23, 2020 4:14 PM
  • Delayed startup for one, but I'd check with manufacturer or in their forums about driver stability. Again unless there's some compelling reason for it, don't do it.

     

    (please don't forget to mark helpful replies as answer)

     

     



    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 WSUAL2 Friday, January 31, 2020 5:59 PM
    Friday, January 31, 2020 4:52 PM

All replies

  • Yes - you can deploy WS 2019 domain controllers into the existing domain. This is fully supported.

    Note that the promotion of the new domain controllers will automatically include forest/domain prep - you have the option of performing these prep steps separately.

    This process is pretty much the same as the one you are already familiar with (since you deployed WS 2016 domain controllers). Details at https://www.petenetlive.com/KB/Article/0001262

    hth
    Marcin


    • Edited by Marcin PolichtMVP Thursday, January 23, 2020 4:15 PM
    • Marked as answer by WSUAL2 Thursday, January 23, 2020 5:07 PM
    Thursday, January 23, 2020 4:10 PM
  • Yes, not a problem, the two prerequisites to introducing the first 2019 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
    https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

     

     



    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 WSUAL2 Thursday, January 23, 2020 5:07 PM
    Thursday, January 23, 2020 4:14 PM
  • Thanks for the information.  That's just what I was looking for.
    Thursday, January 23, 2020 5:08 PM
  • You're welcome.

     

     



    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.

    Thursday, January 23, 2020 5:31 PM
  • We got this error when running the Active Directory Domain Services Configuration Wizard during the Prerequisites Check.  This is a physical server with a hard wired connection to the network on the same VLAN that the other domain controllers in our network are on.  The TCP/IP settings are the same as the other Domain Controllers as well.  I can ping the Domain Controller that I specified in an earlier step. Why does it say that I need to complete the TCP/IP configuration before continuing?  Where do I figure out what settings are missing or wrong?  More detail somewhere sure would be helpful.


    • Edited by WSUAL2 Friday, January 31, 2020 2:52 PM
    Friday, January 31, 2020 2:51 PM
  • Please post an unedited
    ipconfig /all
    and the results in of
    %SystemRoot%\Debug\dcpromo.log

     

     



    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, January 31, 2020 3:13 PM
  • Your reply made me think about it differently and I realized that 2 NICs in the server were not being used and were unplugged.  After disabling those 2 unplugged NICs, the pre-req check completed successfully.

    This DC is replacing a failed DC on another campus, that has been removed and cleaned up from AD.  The plan is to get this DC up and fully replicated on the same network as the other DCs on this campus.  Then we are going to take it over to the remote campus which is on a different network but has all the needed ports available to communicate properly as it was before the failure of the old one.  Is it OK to change the IP when we move it to the other network or will that cause any issues?

    Also, I am planning on teaming 2 of these NICs using Teaming Mode: Switch Independent, Load balancing mode: Dynamic, Standby adapter: None (All Adapters Active).  I was going to do that later when we moved it to the other campus but am wondering if I should team it now before moving it.  Would changing it from a single nic to a team when moving it cause any issues being it is a DC and all?

    Friday, January 31, 2020 4:25 PM
  • It shouldn't be a problem to re-ip it. Just do ipconfig /flushdns, ipconfig /registerdns, restart netlogon service. I can't imagine a domain controller needing the bandwidth of teaming and may end up causing more grief than its worth.

     

    (please don't forget to mark helpful replies as answer)

     

     



    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, January 31, 2020 4:29 PM
  • Got it.  What kind of grief in regards to teaming are you referring to that could happen?
    Friday, January 31, 2020 4:48 PM
  • Delayed startup for one, but I'd check with manufacturer or in their forums about driver stability. Again unless there's some compelling reason for it, don't do it.

     

    (please don't forget to mark helpful replies as answer)

     

     



    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 WSUAL2 Friday, January 31, 2020 5:59 PM
    Friday, January 31, 2020 4:52 PM
  • Got it.  Thanks again for your help.
    Friday, January 31, 2020 5:58 PM
  • You're welcome.

     

     



    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, January 31, 2020 7:44 PM