1

We have one Windows 2008 R2 Foundation box which serves as our Domain Controller/DHCP/DNS/FileServer, all in one kind of deal. It’s currently running a Function Level of Windows 2003 Server.

In a month or so we are going to purchase three new servers with Windows 2012 Standard on them, and demote this 2008 R2 box. Two will act as domain controllers, and one a file server. I’ve searched around Google and have put together a plan, and just wanted to run my plan by and see if I’m missing anything. Everything is backed up, but this is my first production domain move outside of a test environment.

My Plan

  1. Update the function level to 2008 R2, and backup the DHCP settings.
  2. Bring 1 Windows 2012 Server up, add it as a second domain controller having the DNS point to the 2008 R2 Domain.
  3. Move the FSMO Roles to the 2012 machine.
  4. demote the 2008 r2 box after verifying the roles are moved, and change the DNS server back to point back to itself on the new 2012 box.
  5. add the second 2012 box as a domain controller pointing its dns to the new 2012 box.

(where i haven’t been able to find some good information is, once both the new 2012 DC’s are up. Does the DNS settings now change? Meaning, DC1 will point to itself and will DC2 now point back to itself? The only thing I’ve seen is that DNS should always point back to itself somewhere in the list. I’m just wondering after they are both online should DC1 point to DC2 for primary and DC2 point to DC1? and the second dns on each point back to itself?

Also should all the FSMO roles be on one server, or should i spread them out across the two DC’s? these new servers will be DC’s only and provide DNS, only one should provide DHCP, but I was considering implementing DHCP Failover after I backup and move the DHCP settings to the new box.

Any helps/ideas are as always, greatly appreciated.

9 Spice ups
2

Your plan is sound. I’ve just done a few of these myself.

DNS should always point to itself. Not to something like itself. Itself. So DC1 points to DC1. DC2 points to DC2. This is for speed.

3 Spice ups
3

Thanks for the quick reply. Should DC1 point to DC2 for secondary DNS and DC1 point to DC1 for seondary?

As far as the FSMO Roles, should they be spread out across the two DC’s or should DC1 handle them all?

4

Secondary DNS: DC1 point to DC2 and DC2 point to DC1

FSMO Roles: DC1 should be handling the master Roles.

2 Spice ups
5

Here is Microsoft’s offical take on FSMO Placement: Flexible Single-Master Operation (FSMO) placement and optimization on AD DCs - Windows Server | Microsoft Learn

What I normally do is as Nazih suggested. Put them on DC1.

1 Spice up
6

take a look at this link. It will help you as well.

http://community.spiceworks.com/how_to/show/32356-updrade-path-for-a-2012-domain-controller