Link to home
Start Free TrialLog in
Avatar of bergquistcompany
bergquistcompany

asked on

Replacing 2003 DC with 2012 DC

We have a domain controller at each branch office running a subnet of IPs for that branch.
Currently one of the branch DCs is running 2003 server and we're wanting to replace it with 2012.  This DC is NOT running any roles on it.

The new server has DNS and DHCP configured.  The plan is:
1. Bring it online at the branch.
2. Lower DHCP renewal on the existing domain controller
3. Turn off DHCP service on 2003 and turn on 2012.
4. If nothing comes up (as there are no roles to move) demote the 2003 after a week.

Am I missing anything?
SOLUTION
Avatar of Mike Kline
Mike Kline
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bergquistcompany
bergquistcompany

ASKER

Yes I have it up as a DC now to sync DNS as I know that can be ugly
That should not be ugly.  Active Directory and integrated DNS will automatically replicate.

Your way will work, fine; you could also transfer DHCP too.


Thanks

Mike
Would also run a DCDIAG /C /E /V any time I add or remove a DC.
No I know it's not ugly in that essence just if you jump without giving it time to replicate.

Ok good just wanting to make sure I didn't miss anything

What does DCDIAG /C/E/V do?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
To verify the health of DC you can run dcdiag and repadmin /replsum to check the replication status.

What does DCDIAG actually… do?  
http://technet.microsoft.com/en-us/library/cc776854(v=ws.10).aspx
http://blogs.technet.com/b/askds/archive/2011/03/22/what-does-dcdiag-actually-do.aspx

In addition you should also point clients DNS setting to point to new Win2012 server this may be in TCP/IP or DHCP setting before you proceed with Win2003 DC demote.It better to shutdown the DC during business hours for a day and if the clients dont face any issue you should be looking good to demote the Win2003 DC.

If DHPC is not move then see this http://blogs.technet.com/b/networking/archive/2008/06/27/steps-to-move-a-dhcp-database-from-a-windows-server-2003-or-2008-to-another-windows-server-2008-machine.aspx

Once dhcp is configured on Win2012 dont forget to change scope setting to point to new server as dns setting.Also for clients having static ip address assigned you need to manaully change the same.