Discussion Locked

New Exchange Server

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am setting up a new Exchange 2000 server and slowly migrating users from our current Exchange 5.5 server. In order for users to be able to receive messages at the new server, do I need to create an additional MX record with the IP address of the new Exchange 2000 server? Will this conflict in any way the ability for users still on the Exchange 5.5 server to receive mail?

Thanks for your time.

6 replies

by curacao_dejavu

you can have multiple ip adress with different mx records. The priority of the mx records (normailly 10) determines where the email will be sent to, a lower number (5 for example) has a higher priority. for example a mx record with the value of 5 has priority than a mx record with value 10.

That said if both exchange servers are using the same domian name 1 group of users will not receive the emails, Because the new exchange server will not have all the mailboxes yet and at the other hand the new users wont have access to the old exchange.

If they are on the different domain you wont have problems migrating them slowly.

Leopold

by chrisdent

MX won't work. MX records provide a mechanism for delivery if a server is unavailable. If both are available it'll send to the server with the lowest metric not both.

Given you are performing a slow migration this is what I suggest you do:

1. On the Exchange 2000 server create mailboxes for all your users.

2. On the Exchange 5.5 server create an additional e-mail address for each user (name@servername.localdomainname). So they can recieve e-mail on that address.

3. On the Exchange 2000 server create custom recipients for each user forwarding e-mail to the 5.5 server.

4. Change the MX record to point to the Exchange 2000 server. All 5.5 users will recieve e-mail via the forwarding.

5. As you move users onto the 2000 system simply delete the forwarder.

Optional bit:

If the e-mail flow must be bi-directional (5.5 users sending to 2000 users and vice versa) then:

6. On the Exchange 2000 server create an additional e-mail address for each user (name@servername.localdomainname). So they can recieve e-mail on that address.

3. On the Exchange 5.5 server create custom recipients for each user forwarding e-mail to the 2000 server.

Then as you move each user delete the Exchange 2000 custom recipient and activate forwarding on the Exchange 5.5 server.

Creation of all these custom recipients can be avoided if the migration is done over a very short space of time.

by chrisdent

Just to stress...

Its important that each server has an address to send to that it doesn't believe it owns if you are wanting to send mail between the two systems.

This is quite a big job, but I've done this method with a 400 user system and while it did take time for me and the other admins to set up the change over did go almost unnoticed.

by ktamayo

That was very helpful... but I didn't do a very good job of explaining my situation unfortunately.

I only need the ability to send and receive emails on both the Exchange 5.5 and 2000 servers while the migration is happening. Once all accounts have been moved over to Exchange 2000, I will no longer need this functionality.

I have moved over several mailboxes including my own (using Exchange Tasks -> Move Mailbox in AD) successfully, but it appears that my account is still somehow related or dependent on the Exchange 5.5 server. We have a problem w/ the Exchange 5.5 server this morning and while services were down, I noticed I could not receive mails from the Internet during this time.

Any ideas??

This discussion is closed to new replies.