I have a D-Link / TP-Link router which is working as DHCP server leasing IP address to IP phones and workstations. I need to replace this with Windows Server 2012 without interrupting the operation of the devices. How this is possible?
The risk you have is that the new server assigns the same IP address to a new client while some other device still has a non-expired lease from the old DHCP server. There are several approaches to avoid this:
- Decrease lease time before the change down to 30 or 60 minutes and do the change overnight. This need to be at least the current lease time in advance.
- If you have space within the subnet and don't need to use the same pool, pick the new pool from non-overlapping range.
- List all leases from the old DHCP and add then as static reservations to the new one before starting the service. This option minimizes the risk but possibly makes your DHCP less manageable in the future as you need to manually remove unnecessary reservations (when retiring devices or if you have temporary/foreign devices).
- If you can say for sure that all devices will connect DHCP if the network goes down, you can reboot all switches right after the change. However, this doesn't fulfill the requirement of no downtime at all.
You know your network and needs better to pick the most suitable alternative.
If you don't mind changing the IP addresses you can just configure the scope on 2012 - it won't hand out addresses that are still in use (verified through ARP).
If you don't want to change any of the IP addresses, you can configure an empty(!) scope and add all present addresses to the reservations. That way only the reservations are offered, guaranteeing unchanged addresses. When you're done, shut down the old DHCP server and add a scope for the dynamic pool.
Setup DHCP and go.
- Setup your scopes for your lan
- Enable conflict detection on the DHCP server in server 2012.
- Turn off DHCP from the router
- Authorize and activate the scope on the DHCP on the server.
That's all there is to it. Conflict detection was made for this. You don't have to jump through any of the other hoops.
You can try the following points to configure the same environment:
- First, disable the dhcp from your dlink router so that your workstations/host can get the IP from windows server 2012 dhcp.
- Install DHCP role in your windows server
- Configure the scope of the ip addresses, lease time, reserved ip, and other details.
- Make sure that your windows server is connected to the dlink router directly.
- Install router role on your windows server 2012 and you need an extra network adapter to provide connection to the host.
- Connect switch to windows server 2012 and now you can distribute the ip from your windows server 2012