5 replies
by chuonghuan Accepted solution
by huoml Accepted solution
Buy new hardware, preferably one each for DC and exchange.
Install Windows 2003 Server and DCPROMO to make it a DC
Transfer ALL FSMO roles to new DC server
Install new Exchange server
Move all mailboxes from first exchange server
MS site has articles on how to move exchange and DC server to a new hardware.
After successful move of DC and exchange, you will need to follow few steps to properly remove DC and exchange if you wish to shutdown the old DC/Exchange server.
-H
by chuonghuan Accepted solution
by cg it Accepted solution
to go from SBS to standard.
http://www.microsoft.com/WindowsServer2003/sbs/techinfo/planning/transition.mspx
download the word doc.
Also there are issues with SP2
http://support.microsoft.com/kb/932600
I would say best practice would be to transition to W2003 Standard, then move to new hardware as after transition, the constraints that SBS has are removed.
by anmol_email Accepted solution
i have gone thru this process for a couple of clients-
step 1 - install second dc via dcpromo and patch to sp2 first.let replication complete and this generally depends on size of Ad- say an hour or so as rough guide for a typical 50 user site
verify replication via windows support tools (repadmin etc)
step2- install exchange in same organization on dc2. patch it. move mailboxes etc. move first exchange roles (article in msexchange.org)
step 3- verify mail boxes connect for each user or sit on this for a day or 2 so that all users login and get autoredircted to new exchange in their outlook.
step 4- remove exchange from first server
step5- move fsmo and global catalogue role to new server-refer ms kb on this. And SBS allows this -refer note below
step 6- remove ad from first server.
Above is general guideline -
note1-Under no circumstances allow small buinsess server to run for more than 6 days without all fsmo roles as it will begin to shutdown because it wants to hold on to fsmo roles- thats also ms licensing requirement- 7 days is provided as migration time to new server.
note2- dc promo should always be run first before installing exchange otherwise this mangles ad attributes-there is a fix for this issue but why cause an issue in first place -:)
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending