• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 312
  • Last Modified:

DHCP Migration

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
Sundeep V
Asked:
Sundeep V
  • 2
1 Solution
 
WilsonsITDeptCommented:
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
 
Sundeep VAuthor Commented:
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
 
WilsonsITDeptCommented:
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
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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now