moving DHCP service from one server to another server
Hi,I'm running DHCP on a 2003 server and would like to move the DHCP service onto a different server without any downtime. I want to usethe same subnet scope on the new server. If I deactivate the scope on the old server and activate the scope on the new server does anyone know what the consequences will be? I'm concerned maybe the the new DHCP server may give out IP addresses that have already been given out by the old server and still have a few days remaining on their lease period.Or is it possible to copy the dhcp database from one server to the new server!thanks
October 5th, 2008 2:13pm
Hello, Yes its possible to move the DHCP database to another Server. Please follow the links http://support.microsoft.com/kb/325473 http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cncb_dhc_ipmj.mspx?mfr=trueHope it helps Syed Khairuddin
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2008 2:30pm
Hi,
We couldn't migrate DHCP services by directly copying DHCP database between the different servers. I will take migration DHCP server from Windows server 2003 to 2008 for example. In order to move DHCP services, we should perform the following steps:
To migrate from Windows Server 2003 to 2008
================================
1. Log on to the DHCP server by using an account that is a member of the local administrators group.
Note
If you try to run the following command under the domain administrator account, an Access denied error message may appear.
2. Open a Command Prompt window and type the following command:
3. netsh dhcp server export c:\dhcpNEW.txt all
After the configuration settings are exported, the following message appears: Command completed successfully.
4. To disable and stop the DHCP Server service:
Click Start, click Administrative Tools, and then click Services.
Right-click DHCP Server, and then click Properties.
On the General tab, in the Startup type list box, click Disabled. Then click OK.
Right-click DHCP Server, and then click Stop.
5. Copy the c:\dhcpNEW.txt file to the Windows server 2008 Server. Place the file in C:\.
6. Log on to the Windows server 2008 Server as domain administrator.
7. Verify that the DHCP Server service is started and set to automatically start. (In Administrative Tools, click Services to see the Status and the Startup type of the DHCP Server service.)
8. Open a Command Prompt window and type the following:
netsh dhcp server show scope
If the command shows that there are IP address scopes configured for this server, you must delete them before proceeding to the next step. To delete the scopes, type the following:
netsh dhcp server delete scope IPaddress dhcpfullforce
Where IPaddress is the scope address to delete. Repeat for remaining scopes.
9. At the command prompt, type the following:
10. netsh dhcp server import c:\dhcpNEW.txt all
11. After the configuration settings are imported, the following message appears: Command completed successfully.
12. To open the DHCP server console, click Start, click Administrative Tools, and then click DHCP.
13. In the DHCP server console, expand the node for the Management Server in the left pane and expand the IPv4 node until you can see your scope(s). If you see a red arrow icon:
14. For a server icon: right-click the icon and click Authorize. Then right-click the icon and click Refresh.
15. For a scope icon: right-click the icon and click Activate. Then right-click the icon and click Refresh.
16. Verify that your scopes, leases, and options migrated successfully.
For more information, you can visit the links provided by Syed.
October 6th, 2008 9:30am
Morgan CheMSFT said: Hi,
We couldn't migrate DHCP services by directly copying DHCP database between the different servers. I will take migration DHCP server from Windows server 2003 to 2008 for example. In order to move DHCP services, we should perform the following steps:
Sorry if it's a dumb Question Morgan, but I didn't quite follow the thread. Why couldn't the services DHCP be migrated? I've seen posts where if the options didn't match, then the services couldn't be migrated.
- Mike Scott
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2008 7:33pm
Why go through all the trouble of moving the database when you can just use a see-saw method? Say your DHCP range is 192.168.1.100-.150. If you have the room, just set the new server's DHCP range to 192.1681.151-.200. Then once all the clients have moved themselves over, drop the range back to .100-.150. I've done this a lot for many clients and it works great. Be sure to keep your lease time to just a day or two until you get everything on the correct range.
October 7th, 2008 7:05am
Thanks EagleinChains,that'sa great way to go about doing it!I usually do DHCP switches during off hours becuae they end up being part of a larger migration, so I had thought about changing lease times to a few hours, and then everyone will be pulling from the new DHCP server by time normal work hours start.I've actually done the export and import several times, and haven't had any problems. That's why I was curious as to why it didn't work for this poster. I'll have to keep your see saw method in mind for the next time though.Thanks!Mike Scott
Two Guys Tech
Free Windows Admin Tool Kit Click here and download it now
October 7th, 2008 6:31pm