Moving Exchange to new server...
I currently have exchange 2003 running on an old Win2k box that's in need of replacing. I will be moving it to a Win2k3 box running exchange 2003 & would like to keep server name the same, etc. Is there a good website or MS doc starting point I can go to on this?
March 18th, 2011 3:37pm

Any reason why you want to keep the same server name? Drop that requirement and you can do the migration with zero downtime. http://www.amset.info/exchange/migration.asp If you want to keep the same name because you don't want to visit every machine (which is the most common reason) then that isn't an issue, as Outlook will redirect automatically to the new system as long as both the old and the new server are live the first time they connect. To keep the same machine name is just complicated and the gain is very little. To do it with zero risk to the data you would need a third machine. Someone might suggest the backup/restore method but I personally don't use that as it puts your data at unnecessary risk. The swing migration method is risk free, with zero downtime. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2011 7:08pm

I would say its not a good idea as it will make the situation lengthy and if you require support from MS they won't support W2K as the support has been stopped. You should migrate to Exchange 2010 rather than 2003 again. You need one to have atleast on DC running W2K3 SP1 http://technet.microsoft.com/en-us/library/bb124558.aspxGulab | MCTS-MCITP Messaging: 2010 | MCTS-MCITP Messaging: 2007 | MCC 2011 | Skype: Gulab.Mallah
March 19th, 2011 10:23am

Keeping the same name was the main reason. Thanks for the link!
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2011 1:11pm

Thanks, but I'm not keeping it on a Win2k box, and as far as support from Microsoft? You mean the $250 phone call? Not gonna happen!
March 19th, 2011 1:19pm

Great. Got there & found out I had a 64-bit server to work with! I'm assuming my logical alternative will be to go with Exchange 2007, but my DCs are Win2k! I really didn't want to make exchange server a DC, either. How big of a monkey wrench does this throw into the works?
Free Windows Admin Tool Kit Click here and download it now
March 20th, 2011 8:47pm

Great. Got there & found out I had a 64-bit server to work with! I'm assuming my logical alternative will be to go with Exchange 2007, but my DCs are Win2k! I really didn't want to make exchange server a DC, either. How big of a monkey wrench does this throw into the works? This is not good. Having Win 2000 DC's are going to block you from Exch 2007 and 2010. Please see the Exchange Supportability Matrix in the following link, look the the supported AD Environments section. You must have a minimum windows 2003 DC for both Exch 2007 and 2010 and a 2003 Domain/Forest functional level for Exch 2010. http://technet.microsoft.com/en-us/library/ff728623.aspx I also agree that you should NOT make your Exchange server a DC if at all possible. Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharringto
March 20th, 2011 9:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics