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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
You import the database with this command:


 netsh dhcp server import c:\dhcpdatabase.txt all
leegclystvaleCommented:
I used this method when I did it and it worked fine
http://support.microsoft.com/kb/325473

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

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 ?
Darius GhassemCommented:
No.
MaurizioSchmidtAuthor Commented:
No iam not right or NO theres no problem ?
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.
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!
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
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.
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)
Pete LongTechnical ConsultantCommented:
<grin>
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 :)
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)
Pete LongTechnical ConsultantCommented:
ThanQ
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DHCP

From novice to tech pro — start learning today.