Question Locked

Replacing Exchange Server

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am in the process of replacing the Exchange server. I wanted to get some feedback to see if there may be an easier way than I am looking at. It is the domain controller, and exchange server. The current server is running out of room on the system partition and the hard drive has bad sectors. There is a 2nd server that is a file server I was going to run dcpromo on it so that it would be a second domain controller and have a copy of AD and become the PDC on the exising box went away. I have named the exchange replacement the same name since it is for internal and external email. It is currently not on the network. I was going to leave it off until I could switch to avoid conflict. I also have backups of exchange to restore mail.

3 replies

by churdoo

Well since you already have a second DC, don't forget to transfer all of the FSMO roles to the new DC if the first box is that unstable. http://support.microsoft.com/kb/255690

Next I would MIGRATE exchange. You didn't mention, so I'm assuming Exchange 2000 or 2003; I'm also assuming since you didn't mention Exchange 2007 that you're going to stay on the same version of Exchange as you are now. Moving to 2K7 would be an entirely different animal and is called a Transition as opposed to a Migration (not any more difficult, just different).

Keeping the new box the same name will be troublesome because you will not be able to have it on the network at the same time as your old box, and its SID will be different so will not match up to AD in place of the existing Exchange Server, even if you could just shove your exchange infostore backup into a new server and have everything happy. A migration is the answer, and in a migration, your new box has to have a new name since it will have to live on the network alongside the old for the span of the migration.

In a migration, the high level steps are that you'll
1. Join the new box to AD with a new name
2. Install Exchange Server (again assuming 2K3 or 2K) into your existing Exchange Organization
3. Create Send Connectors for the new server as applicable
4. Replicate public and system folders
5. Use the move mailbox wizard and move test mailbox(es)
6. Test send and receive and OWA.

All of the above can be done alongside Production

7. At this point just before moving all of the user mailboxes, if your exchange server has only a private IP that's NAT'd for it to Send / Receive external email, I would swap the IP's of the two exchange servers. This step needs to be done outside of Production hours for obvious reasons. Let each update the AD DNS with their new IP's and test Outlook for a couple of Production user accounts
8. Set the FQDN in the new server's SMTP Server properties to that of the first server
9. Next you can use the Move Mailbox wizard and move all of the production mailboxes.

Note: after the mailboxes are moved to the new server, users' Outlook profiles will AUTOMATICALLY be redirected to the new server the first time the users launch their Outlook. You must leave the old server on for this automatic redirection to happen.

Production should now be live on the new server and it should be sending, receiving, and OWA just as the old one did.

Finally you can go through the process of removing the first server from the exchange organization
http://support.microsoft.com/kb/822931

http://www.msexchange.org is also a good resource for MS Exchange, and has many articles that should help you through this process -- or of course you can post back other questions.

Good Luck!

Edited: typo

This discussion is closed to new replies.