Solved

DHCP Migration

Posted on 2015-01-29
3
262 Views
Last Modified: 2015-01-29
Hi all

we have a windows server 2003 server which we are planning to decommision in next few months.

One of the only thing the server does is run as a DHCP server at one of our sites. The server at present is in local site.  The new DHCP server will be remote at a different site. Both sites are connected via a dedicated line.

The problem is how is best way to go about doing this.

Shall i install dhcp on the new server, create scope etc and then authorize and same time de-authorise the old DHCP server from server 2003.

or

install dhcp on new server as secondary so both gets replicated and then decommission the old one?

We are also thinking to configure a new IP range for this site so im thinking maybe just create new scope will be easier than migrating. what you guys suggest?
0
Comment
Question by:Sundeep V
  • 2
3 Comments
 
LVL 4

Accepted Solution

by:
WilsonsITDept earned 500 total points
Comment Utility
Hi.

When you say a new IP range, do you mean a new IP subnet? Or just a different range of addresses on the same subnet?

Unless there's a reason to retain the old IP addresses, I'd just get the new scope up and running and decommission the old one.

As long as your DHCP clients can use either IP range I would set the new server up, authorise it, then test the configuration by temporarily disconnecting the old servers NIC and booting a client. If it picks up the IP from the new server and works ok then just unauthorise and decommission the old server. When the rest of the clients boot they'll get their new addresses from the new server and all should be well.


Do you have any IP reservations or special requirements for any particular client devices? Are their any special scope options or settings handed out by the server?

Cheers.

Tom
0
 

Author Comment

by:Sundeep V
Comment Utility
It be new subnet too,  as currently we on the 192.168.1.0 subnet and we plan to move to 10.0.0 subnet.

We have 4 reservations but i think i will just manually create that. Probably configure DHCP scope and then once ready, authorize and unplug old server and give it a test.

No point setting up new server with old scope then changing later on.

thanks
0
 
LVL 4

Expert Comment

by:WilsonsITDept
Comment Utility
Sounds like a good plan. If the hosts don't pick up the addresses, or they pick them up but then can't access something they need to, then unplug the new server and troubleshoot from there.



All the best

Tom
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Join & Write a Comment

If you migrate a Terminal Server licenses server inside the 2008 server family, you can takte advantage of the build-in migration tool. If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you …
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now