Export DHCP Database from Windows Server 2003 to another Windows Server 2003

How can i move some working DHCP Server to another DHCP Server. Ive got an Article:

http://support.microsoft.com/?scid=kb%3Ben-us%3B325473&x=13&y=11

But it says, i should not use the DHCP Tool to Import the DHCP to an Windows 2003 Server,
how can i manage this ?
LVL 4
MaurizioSchmidtAsked:
Who is Participating?
 
leegclystvaleCommented:
I used this method when I did it and it worked fine
http://support.microsoft.com/kb/325473
0
 
Darius GhassemCommented:
You import the database with this command:


 netsh dhcp server import c:\dhcpdatabase.txt all
0
 
Pete LongTechnical ConsultantCommented:
1.      First ensure the new server has DHCP installed and is authorised.
2.      Go to the OLD Server
3.      Start > run > cmd {enter}
4.      netsh dhcp server export C:\dhcp.txt all {enter}
5.      Start > Run services > DHCP Server
6.      Stop and Disable the service.
7.      Copy the dhcp.txt file from the source servers c: drive to the new servers C: Drive
8.      Go to the NEW Server
9.      Start > run > cmd {enter}
10.      netsh dhcp server import c:\dhcp.txt all {enter}

Note: If the source server is 2000 or NT then you need to Export the config using the DHCPEXIM.exe tool from the support tools
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MaurizioSchmidtAuthor Commented:
ah thx alot guys! thats all ? did i have to check any lease times etc ? i dont think so cause i import/export the settings so it shouldnt be any problem, right ?
0
 
Darius GhassemCommented:
No.
0
 
MaurizioSchmidtAuthor Commented:
No iam not right or NO theres no problem ?
0
 
Andrej PirmanCommented:
My oppinion is that there is no need for moving DHCP database to other server.
Instead you simply setup the new server with same DHCP settings, shut down old DHCP, start new DHCP, authorize it and off you go. DHCP is broadcast, so clients will get new leases when they request them, and old leases are CLIENT-based, not DHCP-based, so there is really no need to transfer DHCP database.
0
 
leegclystvaleCommented:
By just uninstalling it and installing on a new server as per Labsy suggestion, you will lose all your reservations (which is a hassle!) and also could get duplicate addresses as the new DHCP server will not know what has already been issued (if you use the same DHCP scope) and what addresses are already out there.
Move it gracefully I'd suggest and it will save you lots of hassle!
0
 
Darius GhassemCommented:
Moving a DHCP database isn't hard at all. I have never had one issue moving DHCP over to another server. No you have everything correct
0
 
Pete LongTechnical ConsultantCommented:
Ive done this loads of times? yes it is easy to start from scratch but wait till you've copy 'n'n pasted the MAC address of 100 network printers into a new DHCP config, and you will be doing it this way from now on.
0
 
leegclystvaleCommented:
Who said they've done it loads of times PeteLong? And yes, you'll only install a fresh copy of DHCP once as you say :o)
0
 
Pete LongTechnical ConsultantCommented:
<grin>
0
 
MaurizioSchmidtAuthor Commented:
yep thats the problem, i just dont wanna reconfig all the settings within the DHCP. ill test the:

1.      First ensure the new server has DHCP installed and is authorised.
2.      Go to the OLD Server
3.      Start > run > cmd {enter}
4.      netsh dhcp server export C:\dhcp.txt all {enter}
5.      Start > Run services > DHCP Server
6.      Stop and Disable the service.
7.      Copy the dhcp.txt file from the source servers c: drive to the new servers C: Drive
8.      Go to the NEW Server
9.      Start > run > cmd {enter}
10.      netsh dhcp server import c:\dhcp.txt all {enter}

and hopefully it works :)
0
 
leegclystvaleCommented:
More than a hope, it'll be just fine. If for some strange reason it isn't, you still have the old server and you can just restart the service, and de-authorise the new server and you're back where you started...nothing lost and all your reservations and configs in place as well :o)
0
 
Pete LongTechnical ConsultantCommented:
ThanQ
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.