none
Moving dhcp from Win2k8r2 to Win2016

    Question

  • I just promoted a Win2016 server to domain controller.  I have 4 other DC's and they are all 2008r2.  I have already migrated SYSVOL replication from FSR to DFS.  I plan on retiring one of the 2008r2 DC's soon.  The server i plan to retire is running dhcp.  So my next step is to move dhcp from the DC i plan to retire to the new 2016 DC.  Below is the plan I hope to use for this.  Please look at my steps and let me know if I am missing anything or have something out of order.  This information did not fall out of the sky.  I compiled it from several different articles and posts and have used this same method to migrate dhcp at another location from a Win2008 dhcp server to a Win2008r2 server.  For some reason the restore failed and I had to set everything up manually.  I know there are other ways to do this.  Thanks

    1. Add the DHCP role to the 2016 server

    2. Use the right-click 'backup' option on the 2008r2 server and backup to a folder.  Copy the backup to the new dhcp server.

    3. Unauthorize, stop, and disable DHCP service on old server

    4. Restore the backup (created in step #2) on the 2016 server using the right-click option in the MMC

    5. Restart DHCP service if necessary.

    6. Authorize the 2016 DHCP server.

    7. Go to DHCP server properties, Advanced, set conflict detection to 1.

    8. Immediately test a workstation by using ipconfig /release, /renew

    9. Verify scope settings and test other clients

    10. After verifying dhcp functionality, if necessary modify any scope options and server options.

    mardi 24 octobre 2017 21:19

Réponses

  • So would you recommend using the following method which uses netsh?

    On source DHCP server
    1. Log on to the source DHCP server.
    2. Open the dhcp management console
    3. Highlight the dhcp server name
    4. On the Action menu, click Backup.  Select a location for the backup file.
    5. Open an elevated command prompt
    6. Type netsh dhcp server export C:\dhcpdb.txt all, and then press ENTER.
    7. Copy the exported DHCP database file to the local hard disk of the destination DHCP server.
    On destination DHCP server
    8. Install the DHCP server service on the destination DHCP server.
    9. Stop the DHCP service
    10. Delete  the c:\windows\system32\dhcp\dhcp.mdb file
    11. Start the DHCP service
    12. Open an elevated command prompt
    13. Type netsh dhcp server import C:\dhcpdb.txt all, and then press ENTER
    14. Stop and restart the DHCP service
    15. Open the DHCP management console
    16. In the console tree, click DHCP.
    17. On the Action menu, click Authorize.

    Note:  some articles recommend authorizing the server following step #8.

    Am I missing anything? 

    • Modifié Poly Admin mercredi 25 octobre 2017 19:31
    • Marqué comme réponse Poly Admin mardi 31 octobre 2017 15:57
    mercredi 25 octobre 2017 18:54
  • Hi,

    Your process should be working. 

    Step 2 ~ 4 in your original process should be changed to use “netsh” (step 1 ~17) you had listed on the above reply. 

    If possible, it is recommended to reproduce the process in a test environment. It would be helpful to complete your plan and avoid possible problem. 

    Microsoft Evaluation Center provides trial OS version to be downloaded, it can be used to build a virtual test environment:
    https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016

    Best Regards,
    Eve Wang

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

    • Marqué comme réponse Poly Admin mardi 31 octobre 2017 15:57
    jeudi 26 octobre 2017 01:27
    Modérateur

Toutes les réponses

  • Hi,

    More I information and just for your reference:
    1. It is recommended to back up first before any change. Please reference - More About DHCP Backup and Restore:
    https://technet.microsoft.com/en-us/library/dd759235(v=ws.11).aspx

    2. Step 2 of your plan, I would recommend you to use DHCP database Export and Import to move a DHCP database from old server to new server.
    More About Exporting and Importing the DHCP Database:
    https://technet.microsoft.com/en-us/library/dd759224(v=ws.11).aspx

    3. There might be a period of DHCP down time, schedule the migration in during a non-production time.

    Migrate DHCP Server to Windows Server 2012 R2:
    https://technet.microsoft.com/en-us/library/dn495425(v=ws.11).aspx

    Best Regards,
    Eve Wang

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

    mercredi 25 octobre 2017 09:33
    Modérateur
  • So would you recommend using the following method which uses netsh?

    On source DHCP server
    1. Log on to the source DHCP server.
    2. Open the dhcp management console
    3. Highlight the dhcp server name
    4. On the Action menu, click Backup.  Select a location for the backup file.
    5. Open an elevated command prompt
    6. Type netsh dhcp server export C:\dhcpdb.txt all, and then press ENTER.
    7. Copy the exported DHCP database file to the local hard disk of the destination DHCP server.
    On destination DHCP server
    8. Install the DHCP server service on the destination DHCP server.
    9. Stop the DHCP service
    10. Delete  the c:\windows\system32\dhcp\dhcp.mdb file
    11. Start the DHCP service
    12. Open an elevated command prompt
    13. Type netsh dhcp server import C:\dhcpdb.txt all, and then press ENTER
    14. Stop and restart the DHCP service
    15. Open the DHCP management console
    16. In the console tree, click DHCP.
    17. On the Action menu, click Authorize.

    Note:  some articles recommend authorizing the server following step #8.

    Am I missing anything? 

    • Modifié Poly Admin mercredi 25 octobre 2017 19:31
    • Marqué comme réponse Poly Admin mardi 31 octobre 2017 15:57
    mercredi 25 octobre 2017 18:54
  • Hi,

    Your process should be working. 

    Step 2 ~ 4 in your original process should be changed to use “netsh” (step 1 ~17) you had listed on the above reply. 

    If possible, it is recommended to reproduce the process in a test environment. It would be helpful to complete your plan and avoid possible problem. 

    Microsoft Evaluation Center provides trial OS version to be downloaded, it can be used to build a virtual test environment:
    https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016

    Best Regards,
    Eve Wang

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

    • Marqué comme réponse Poly Admin mardi 31 octobre 2017 15:57
    jeudi 26 octobre 2017 01:27
    Modérateur
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

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

    lundi 30 octobre 2017 05:45
    Modérateur
  • I plan to use netsh to move dhcp later today.  I will post tomorrow with the results and any questions.

    thank you

    lundi 30 octobre 2017 13:55
  • Hi,

    It’s my pleasure. If there is any update, please feel free to let me know.

    Best Regards,
    Eve Wang

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

    mardi 31 octobre 2017 01:41
    Modérateur
  • Moved dhcp yesterday using netsh.  Everything went well.  I stopped the dhcp service and set it to disabled on the old dhcp server.  I have tested a couple clients using ipconfig /release /renew.  They got an ip from the new dhcp.  Everything looks good.  I will mark an answer.  thanks
    mardi 31 octobre 2017 15:57
  • Hi,

    Thank you for taking the time to update the result. 

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

    Best Regards,
    Eve Wang

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

    mercredi 1 novembre 2017 01:37
    Modérateur
  • This doesn't seem to move the leases.
    mercredi 13 juin 2018 19:17