JamesonJendreas
asked on
DHCP Reservations - Migrating to a new Server
OK - as far as I can tell this will have to be done manually, but hey, why not ask?
So I currently have an aging DHCP server that's running Windows Server 2003 (also a DC). I have a new 2008 box that's taking over for the 2003 as my DHCP and my DC FSMO master. In my current DHCP server, we have a good 50+ reservations. These will be a pain to manually recreate.
So I did an export of my reservations hoping there was an ability to import into my new server. Doesn't seem to be the case (the export doesn't even hold all the reservation info, just the IP and host name. No MAC!)
Also, I'll need to be able to edit the reservation list, as with the DHCP switchover I am also re-creating my DHCP scheme to work with my new VLAN setups. Previously we have a DHCP scope of 192.168.0.0 255.255.240.0, creating an ugly huge, subnet with way too many users on it. I've been logically breaking this up and moving users over to the new DHCP server by assigning them a VLAN. Those with reservations are going to be tricky as I have to use subnets that aren't in my current subnet..
Probably more info than needed for a posts who's replies will be "Can't do it!"
Cheers JJ
.
So I currently have an aging DHCP server that's running Windows Server 2003 (also a DC). I have a new 2008 box that's taking over for the 2003 as my DHCP and my DC FSMO master. In my current DHCP server, we have a good 50+ reservations. These will be a pain to manually recreate.
So I did an export of my reservations hoping there was an ability to import into my new server. Doesn't seem to be the case (the export doesn't even hold all the reservation info, just the IP and host name. No MAC!)
Also, I'll need to be able to edit the reservation list, as with the DHCP switchover I am also re-creating my DHCP scheme to work with my new VLAN setups. Previously we have a DHCP scope of 192.168.0.0 255.255.240.0, creating an ugly huge, subnet with way too many users on it. I've been logically breaking this up and moving users over to the new DHCP server by assigning them a VLAN. Those with reservations are going to be tricky as I have to use subnets that aren't in my current subnet..
Probably more info than needed for a posts who's replies will be "Can't do it!"
Cheers JJ
.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Chris! I'll take a look at that code, I have powershell 2, but I'll add the DHCP man tools.
Simply copy the dhcp db from one to the other.
Create a scope with all your options.
Stop DHCP on both old and new server and copy the whole C:\WINDOWS\System32\dhcp folder to the new server.
Start DHCP on new server and authorize.
What's nice is it also copies the leases over too so there are not as many ip conflicts if some leases expire and get renewed.
Create a scope with all your options.
Stop DHCP on both old and new server and copy the whole C:\WINDOWS\System32\dhcp folder to the new server.
Start DHCP on new server and authorize.
What's nice is it also copies the leases over too so there are not as many ip conflicts if some leases expire and get renewed.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chris is correct about using netsh or a script. I have added my comment to the correct answer as I've outlined my steps I used for using netsh to move reservation info only, with the ability to edit the reservation IP addresses. Link from Ronny was close, but the exported file I was unable to edit (or more accurately was not plain text).
Thanks everyone for their help!
Thanks everyone for their help!
Don't know if this can be done for sure, but take a look here: http://blogs.technet.com/b/networking/archive/2008/06/27/steps-to-move-a-dhcp-database-from-a-windows-server-2003-or-2008-to-another-windows-server-2008-machine.aspx
Maybe you can edit the export .txt file to your wishes.