How best to replace critical 2003 domain controllers with 2008 R2?

hi,

we looking 'transition' 2003 sp2 x86 domain controllers 2008 r2 x64.  have hundreds of branch sites routers use ip addresses of 2 windows 2003 dcs dns.  primary pointing dc1 , secondary dc2.  in addition, have split scope dhcp running subnets on these 2 windows 2003 domain controllers.

for obvious reasons, want retain ip addresses of 2 2003 domain controllers replacement windows 2008 r2 domain controllers.  strategy can think of @ present is:

- prepare ad 2008 r2 

- uninstall ad / dns from dc2, reboot.  change ip address of server, running dhcp, different.  ensure dns updated reflect before proceeding.

- configure new 2008 r2 domain controller (dc4) ip address of decommissioned 2003 dc above.  install ad 2008 r2 onto dc4, including dns.  install , configure dhcp in readiness host other half of dhcp split scope, still sitting on 2003 dc above.  migrate dhcp member server above 2008 r2 domain controller.  test , ensure well.

- now, same 2 steps above first dc (with bit more pain imagine, whilst apps / devices fail secondary dns server), transferring fsmo , time master roles.

 

any comments on 'transition' approach please or have easier transition plan minimise potential down-time further?

 

thank you.

looks fine - although might consider reviewing first:

http://blogs.chrisse.se/blogs/chrisse/archive/2011/04/01/upgrade-active-directory-from-ws03-to-ws08-r2.aspx

note intend dhcp server remain functional during transition, need adjust ip helper configuration on routers

hth
marcin

Windows Server  >  Directory Services