2003 to 2008 Upgrade


i planning on upgrading (inplace) main domain controllers 2003 2008 in our environment. first give information on our network questions , concerns.

information:

1. have our fsmo roles divided on 2 dc's.
2. server has schema master, operations master & infrastructure master
3. server b has rid & pdc
4. running exchange 2003 latest service pack
5. have citrix 4.0 on 2003 latest service pack.

questions / concerns:

1. 1 of 2 fsmo roles should upgraded first? matter?
2. want on 2008 r2, once have servers upgrade 2008, can r2 upgrade done without total upgrade scratch? since r2 64bit only, exchange have problems r2 or 2008 dc @ all?


http://www.netometer.com/video/tutorials/windows-dc-2008-inp lace-upgrade/

hello,
please inline response

1- 1 of 2 fsmo roles should upgraded first? matter? 
 
  doesnot matter, advise transfer rid , pdc role (temporarily)from server b server a, inplace upgrade of server b after success, move 5 roles server b , inplace upgrade server , move fsmo roles where..this incase hardware or other failures might occur during upgrade.

2. want on 2008 r2, once have servers upgrade 2008, can r2 upgrade done without total upgrade scratch? since r2 64bit only, exchange have problems r2 or 2008 dc @ all?

this depend on current hardware..w2k8 r2 runs on 64bits, if current hardware not support 64 bit, need buy 64 bit system , clean install, if current hardware support 64 but, can inplace upgrade well.

exchange 2003 is not supported on 64 bit system. may have upgrade exchange 2007
http://support.microsoft.com/kb/555468


on side note, remember run adprep /forestprep, adprep /domainprep on server before start inplace upgrade.

also, instead of inplace upgrade, may suggest clean install on both move roles 1 server , vice versa
isaac oben mcitp:ea, mcse


Windows Server  >  Migration



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file