Domain Controller Upgrade -Win 2003 to Win 2008 R2


hi
doing windows 2003 domain upgrade , few things need confirmed before upgrade.
please find environment
main site
2 * win 2003 se- r2-sp2- 32 bit (one server hold fmso roles)
exchange 2007 – sp1 (active/passive cluster mail box)
2*hub/cas servers (nlb)
sharepoint 2007/sccm 2007/ sql 2005 sp3/wsus/ etc..
dr site
win 2003 se-r2-sp-32 bit domain controller.
exchange 2007 sp1 – mail box
exchange 2007-sp1 -hub/cas
here upgrade plan going execute.  have tested these steps in test environment without applications. please let me know missing/ wrong in production environment.
upgrade process
• extend schema attributes windows 2008 domain environment.
• join new server windows 2008 server existing domain
• transfer roles new server(all fsmo roles)
• leave times replications
• change application servers use new server domain & dns service
• promote additional windows 2008 domain controller in dr site
• point dr application servers used new win 2008 domain controller.
• shutdown old domain controllers( both main site , dr site)
• check application server issues (expect domain replication issues)

• start old domain controllers
• demote windows 2003 domain controllers
• move domain /forest functional level windows 2008 r2
• remove windows 2003 domain entries domain
• verify application functionalities

do have else exchange/sharepoint/sccm applications work? 

------------

i found that exchange 2007 sp1 need upgraded exchange 2007 sp1-ur9 or sp2 level support windows 2008 r2 domain enviroment.

thank you

indunil
 

 

howdie!
 
am 25.11.2010 08:59, schrieb indunil:
> upgrade process
> • extend schema attributes windows 2008 domain environment.
> • join new server windows 2008 server existing domain
> • transfer roles new server(all fsmo roles)
> • leave times replications
> • change application servers use new server domain & dns service
> • promote additional windows 2008 domain controller in dr site
> • point dr application servers used new win 2008 domain
> controller.
> • shutdown old domain controllers( both main site , dr site)
> • check application server issues (expect domain replication issues)
>
> • start old domain controllers
> • demote windows 2003 domain controllers
> • move domain /forest functional level windows 2008 r2
> • remove windows 2003 domain entries domain
> • verify application functionalities
 
the plan looks good. since exchange involved, make sure make
replacement dc global catalogs well. make sure new pdc
emulator has authoritative time source configured (either hardware
clock or external time service). we're talking physical dcs
here, no virtualization involved, right?
 
cheers,
florian
 
 

microsoft mvp - group policy (http://www.frickelsoft.net/blog)


Windows Server  >  Directory Services



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client