none
Transferring FSMO roles from 2008 to 2016 and changing DC IP address

    Question

  • Hi All,

    I am planning to transfer FSMO roles from DC 2008 to new DC server 2016, i want to use same IP address of existing 2008 DC on New DC 2016, is it possible that after i transferred the roles to new DC, can i shutdown old DC and use the same IP address on new DC 2016? because all users are using DC 2008 in preferred DNS and have Static IP address so it is difficult for me to change for 100s of users.

    Regards,

    Agha

    Tuesday, July 10, 2018 7:24 AM

Answers

  • Hello,

    Changing the IP address will have no impact on the FSMO roles so you can do it peacefully.

    Regarding the step you should :

    • Transfert the FSMO roles to the DC2016
    • Change the IP address of the DC2008 to a new IP (During non business hour)
    • Change the IP address of the DC2016 to the old IP of DC2008 (During non business hour)
    • Shutdown DC2008 during 1 week to check that everything is working fine (Regarding hardcoded application with the name of the DC2008)
    • Bring DC2008 online
    • Depromote DC2008

    Best Regards,

    • Marked as answer by Agha Ali Tuesday, July 10, 2018 11:40 AM
    Tuesday, July 10, 2018 8:48 AM
  • Hello,

    So you have to migrate your SYSVOL to DFSR, below an article regarding this migration :

    https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/

    Best Regards,

    • Marked as answer by Agha Ali Tuesday, July 10, 2018 11:40 AM
    Tuesday, July 10, 2018 10:28 AM
  • Hello,

    You don't need to worry about that AD DS 2008 is fully functional with AD DS 2016 so your DC on 2008 will work with DC on 2016 even if you move the FSMO roles to the new DC2016

    Best Regards,

    • Marked as answer by Agha Ali Thursday, July 12, 2018 1:09 PM
    Thursday, July 12, 2018 11:42 AM
  • We resolved the issue, it was happened because we immediately change the IP address and shutdown the old domain controller. so we should wait for 24 hours to replicate all the things.

    repadmin /showrepl  (to check the replication)

    Regards,

    Agha

    • Marked as answer by Agha Ali Monday, July 16, 2018 2:28 PM
    Monday, July 16, 2018 2:28 PM

All replies

  • Hello,

    Changing the IP address will have no impact on the FSMO roles so you can do it peacefully.

    Regarding the step you should :

    • Transfert the FSMO roles to the DC2016
    • Change the IP address of the DC2008 to a new IP (During non business hour)
    • Change the IP address of the DC2016 to the old IP of DC2008 (During non business hour)
    • Shutdown DC2008 during 1 week to check that everything is working fine (Regarding hardcoded application with the name of the DC2008)
    • Bring DC2008 online
    • Depromote DC2008

    Best Regards,

    • Marked as answer by Agha Ali Tuesday, July 10, 2018 11:40 AM
    Tuesday, July 10, 2018 8:48 AM
  • Thanks a lot Dokoh,

    I got the following warning while creating additional domain controller in existing domain in dc2016. what do i need to do? i tested by disabled one account in 2008 and checked in dc2016 it is showing immediately the user is disabled and enabled in 2016 so it means replication is working fine.

    The File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command.  If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server.

    regards,

    Agha

    Tuesday, July 10, 2018 9:36 AM
  • Hello,

    So you have to migrate your SYSVOL to DFSR, below an article regarding this migration :

    https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/

    Best Regards,

    • Marked as answer by Agha Ali Tuesday, July 10, 2018 11:40 AM
    Tuesday, July 10, 2018 10:28 AM
  • Hi,

    I am glad to see that your issue was successfully resolved.

    If there is anything else we can do for you, please feel free to post in the forum.

    Best Regards,

    Kallen


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

    Wednesday, July 11, 2018 6:36 AM
  • Hi Dokoh,

    i have a question that we have additional domain controller on windows 2008 R2 at branch office so when i transfer the FSMO roles to new DC2016 then will this ADC 2008 work with DC2016 automatically or do i need to do anything?  we will migrate this ADC2008 later to 2016 on new server.

    Thanks

    Agha

    Thursday, July 12, 2018 10:05 AM
  • Hello,

    You don't need to worry about that AD DS 2008 is fully functional with AD DS 2016 so your DC on 2008 will work with DC on 2016 even if you move the FSMO roles to the new DC2016

    Best Regards,

    • Marked as answer by Agha Ali Thursday, July 12, 2018 1:09 PM
    Thursday, July 12, 2018 11:42 AM
  • Thanks a lot Dokoh. it is very helpful for me.

    Regards

    Agha

    Thursday, July 12, 2018 1:12 PM
  • I transferred the FSMO roles and changed the IP address on both servers 2008 and 2016 but i am getting error DNS is not contacting to DNS server do you want to continue and after 2 minutes it becomes working.

    what could be the reason.

    i shutdown old DC2008 after transferred and changed the IP address.

    regards

    Agha

    Friday, July 13, 2018 11:34 AM
  • Hello,

    What do you mean by "i am getting error DNS is not contacting to DNS server" ?

    Best Regards,

    Friday, July 13, 2018 12:04 PM
  • error in logs

    The DNS server could not open socket for address 192.168.1.10.

    Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.)

    Friday, July 13, 2018 12:19 PM
  • Is it possible to have an output of the IP configuration of your 2 DC (Ipconfig /all) ?

    Can you check also which configuration you have on these DNS servers regarding the interface part and forwarders and send the info ?

    Note : A OneDrive link can be better

    Best Regards,

    Friday, July 13, 2018 2:47 PM
  • We resolved the issue, it was happened because we immediately change the IP address and shutdown the old domain controller. so we should wait for 24 hours to replicate all the things.

    repadmin /showrepl  (to check the replication)

    Regards,

    Agha

    • Marked as answer by Agha Ali Monday, July 16, 2018 2:28 PM
    Monday, July 16, 2018 2:28 PM
  • Hi,

     

    I am glad to hear that your issue was successfully resolved.

    If there is anything else we can do for you, please feel free to post in the forum.

     

    Best Regards,

    Kallen


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

    Wednesday, July 18, 2018 9:46 AM