Hey everyone! I'm currently working on migrating DHCP services during our domain controller upgrade from two Windows Server 2016 instances to one Windows Server 2022 instance. Both of the 2016 servers currently handle DHCP load balancing equally and cover the same scopes. I know the general process of moving DHCP services, but I'm trying to figure out the most efficient way to migrate all the DHCP configurations and lease info.
Would it be sufficient to just export the DHCP config and leases from one of the primary servers and import it into the new 2022 server? Or should I export and merge the scopes and leases from both servers to avoid any potential conflicts?
Additionally, I'm considering removing the secondary 2016 server and adding the new 2022 server so that it will replicate the data. After everything is migrated, I plan to disable services on the legacy servers, authorize the new server, and update the IP helpers. Any advice on the best approach?
4 Answers
Be cautious with the consolidation! Centralizing DHCP can create risks of greater outages. I had a situation where one data center failure caused issues nationwide because everything was funneled through that one point. If you're consolidating, ensure the business understands the risks!
Microsoft has detailed guidelines on this migration process. Check out their official documentation [here](https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-dhcp-server). When migrating, it's crucial to export scopes and leases from both servers; otherwise, you might face IP conflicts until all devices renew their IP addresses. Keeping everything intact helps minimize issues post-migration.
If Windows Server is a must for DHCP, consider isolating it on a separate server just for that purpose. This also goes for DNS; it might save you a lot of headaches later on.
My recommendation is to break the failover relationship between your 2016 servers. Then, just run DHCP from a single 2016 server, export the DHCP database, stop the service on the old one, and import everything onto your new 2022 server. After that, just authorize it and make sure to force some clients to renew their IPs.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures