Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Move Exchange to new hardware?

Status
Not open for further replies.

MoaTad

Programmer
Jun 7, 2002
27
US
We have:
server1 - W2k3 Server, which is the Domain Controller
server2 - W2k3 Server, which has Exchange 2003 Server
clients - Win XP, which use Outlook as the mail client

We want to replace the hardware for the Exchange server. No software or configuration changes at all.

What is the best way to get the Exchange implementation onto the new server when we get it?

The hardware will not be identical, so a full system restore from tape is not an option. However, we have full tape backups of everything which could be used if necessary.

Thanks in advance for your help!



 
Since you are getting new hardware your best method is to set up the new server as an additional Exchange server in the Exchange site. Then use the Move Mailbox wizard to move your mailboxes.

Use Folder replication to get your public folders moved over then break the replica and set the master location to the new server. Then gracefully remove the old box and direct mail to the new one.

I hope you find this post helpful.

Regards,

Mark
 
along with markdmac's good info, you should know once you move the mailboxes to the new server, the clients profile will automatically switch over to the new server - so that will save you a worry and time ;)
 
Thanks to both of you! That is very helpful and gets me on the right track.

I had tried to find something in the MS knowledge base on this, but no matter how I designed my searches, there were no results that were relevant.
 
Sorry but you won't be able to use the above link posted by Marcs41. That is for keeping the same server name which you can't do because you would then not be able to use the Move mailbox method (can't have 2 machines with same name).

I hope you find this post helpful.

Regards,

Mark
 
Well that is correct Mark, but this is also a way of doing it.
I just thought to post an alternative for which a KB exists.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]
Have a look at the shop @ !
 
My post wasn't intended to be a slam at you Marc. I've used that KB myself. It is intended to be used more as a disaster recovery method than a migration.

Advantages of doing the way I have proposed is that it leaves the exisitng machine intact until all mailboxes are safely moved. Users can continue to receive email. If there is a problem with the migration to the new server you can reverse all changes, since the existing server remains. Using the KB that is not possible without having to first rebuild the existing server.

I hope you find this post helpful.

Regards,

Mark
 
Oh, I agree. I was not offended or anything, don't worry.

I personally try to avoid active users during a migration, and, if something goes wrong, I still got the 'old' server.
Just another way of doing it.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC!
[/sub]

Have a look at the shop @ !
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top