This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hi,
I have plan to migrate DHCP server from server 2012 R2 to windows server 2019 Standard. Initial plan is I want to backup the DHCP database and restore to new server, but unfortunately our management not approve that plan due to concern unexpected impact to certain scope (department). So they want me come with plan migrate scope by scope.
So example we have 15 scope inside that then i will divide by 5 scope per weeks (3 weeks to complete all)
I will use below command to backup 5 scope and then restore back to new DHCP server.
Export-DhcpServer -ComputerName DC1 -File "C:\DHCPBackup\dhcpexport.xml" -ScopeId 172.18.0.0,172.18.2.0,172.18.3.0,172.18.4.0,172.18.5.0 -Leases
So i will repeat this method for the rest of scope. My question, is it this is right method to migrate? Any impact i can foresee? Previously i only have experience to restore entire DB instead of scope by scope. I have tried on test environment and seems ok, new scope restoration will not overwritten other scope (previously restored).
Thanks
Hasmizi
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Yes, it looks good to me. Some other examples here.
https://learn.microsoft.com/en-us/powershell/module/dhcpserver/export-dhcpserver?view=windowsserver2019-ps
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hello @Mizi ,
I would like to suggest you to build 2019 DHCP server but do not authorize it so it should not impact your existing DHCP server and export that scope using that command
After it got successfully export just check everything thing looks in 2019 DHCP server for that scope you exported.
Impact here is you might not be able use new server as its not authorize yet.
If the reply was helpful, please don’t forget to upvote or accept as answer.
hello @Limitless Technology
Thanks for your feedback, i think we need to authorize that because when we import first 5 scope, i will deactivate those scope in old server. So for the next week, i will come with same method and continue with other 5 scope, export and import to new server. Did you see any issue on that method?
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
@Anonymous thanks for your feedback, ya if u think looks good, i will use this approach. At first im worry whether second import will overwritten the first import scope. But from my test environment i can see it just add new scope after we import that. So i think it would be safe to use this method, as a plan it will 3 time import . First week would first 5 scope been exported and following with second and third weeks. I will stick with this plan. Thanks for help.