We need new domain controllers using the same names and IP addresses as the old servers.

The idea I have is to move FSMO roles from first server to the second, then demote. rename and re-IP the first server.  Remove DNS role from the demoted server and leave it running as a DHCP server.  Then create a 2012 R2 server with the name and IP of the old DC.  Then promote this to DC and DNS server using the old name and IP.

Repeat for second DC.

Once this is complete, we want to also migrate the DHCP server to 2012 R2 and take advantage of the new option where the DHCP servers coordinate IP leases with each other.

Are there additional steps needed or is there a better way to plan this?

Hi MyGposts,

Given you're talking about moving the DHCP server role to a new server in any case, I'd actually be inclined to start with migrating the DHCP database out to a new server as the first task. At that point rebuilding the two domain controllers can be done with ease using the guidelines you've already mentioned.

You can read more about DHCP 2008 R2 to 2012 (R2 is the same process) migration here.

Also keep in mind that if you only have two domain controllers, you don't strictly need to move the FSMO roles as the demotion process will automatically move any FSMO roles to the other domain controller. You can certainly do it manually yourself if you're feeling particularly cautious, but it's not a required step.

Cheers,
Lain