Hi, I hoping that you will be able to give me some guidelines on the replacement of an Exchange 2003 server. We have an Exchange 2003 server that pre-dates everyone in the office, and it appears to have been set up with a few "gotcha's", so after a couple of weeks of trying to unpick the server, we decided to perform a DR Restore, so we took copies of our DC's and VM'ed these. Then on a test network (complete separate from company network), we launched the VM DC's and rebuilt the Exchange Server (following DR procedure), and everything appears to have restored and works all OK. With the apparent success of this, it has now been asked that we switch the problem Exchange server off and replace it with the clean built DR Exchange server, (we also have 1 Front End Server that hooks into the Exchange server, which we have not been able to test) I was wondering if anyone can advise of the necessary steps to take to help the "new" server go in without any problems. Thanks for your time.

Hi There is official guide of the process. 1. Set up new exchange in the same domain. 2. Move user mailbox from old box to new box. 3. Turn off old server. Moving Exchange Server 2003 to New Hardware http://technet.microsoft.com/en-us/library/bb124429.aspx How to Move Exchange Server to a New Computer That Has the Same Name http://support.microsoft.com/kb/q155216/ TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.comTerence Yu TechNet Community Support

That is not the usual way of replacing the server. A swing migration is the usual method which is completely risk free, requires no downtime for the server and does not result in any loss of data. By using the swing method you will be able to control and manage the migration to the new server, at no point is the data at risk and you can back out of it at any time. I have a guide to the process here: http://exchange.sembee.info/2003/migration/swing-migration.asp While it takes longer than the DR method, the DR method does mean that you are at the mercy of the backup or database being good. It also could mean that problems with the existing installation are actually brought across, particularly corrupt or bad data in the database. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I would not mock around the production the way you are thinking to do. As others said correct way to deal with this building new Exchange server and moving mailboxes on it and at the end you will need to decommission your old Exchange server. Same goes for domain controllers, just DCPromo new one and make sure your current domain content replicates on the new DC properly. You can then move existing services over newly build servers and decommission old server at the very end. This is the correct way of doing what you want to do Good luck OcdOz Casey, Dedeal MCITP (EMA), MCITP (EA), MCITP (SA) Visit smtp25.blogspot.com Visit Telnet25.wordpress.com This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Hi Do you have anything update ?Terence Yu TechNet Community Support