Migration from Exchange 2000 to Exchange 2003 with MTA shut down on Exchange 2003 (924250)
The information in this article applies to:
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange 2000 Server
Source: Microsoft Support
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION IN RESPONSE TO EMERGING OR UNIQUE TOPICS, AND MAY BE UPDATED AS NEW INFORMATION BECOMES AVAILABLE. SUMMARYHow to migrate from Exchange 2000 to Exchange 2003 7 node cluster with the MTA
disabled on the clusterMORE INFORMATIONone Routing Group with Exchange 2000 and Exchange 2003. MTA running on both
servers. Routing Group Connector set up with the Exchange 2003 as the local
Bridgehead.
created a second Routing Group with an Exchange 2003 server in it. turned the MTA
off on this server.
created 2 test mailboxes on the Exchange 2000 server. called one of them TestMove
and sent mail to make one of them 100 MB so that it would take a few minutes to
move. then logged into the second mailbox and created 5 messages addressed to the
TestMove mailbox, but did not send them yet. initiated the move of TestMove from
Exchange 2000 to the Exchange 2003 server in the remote Routing Group. As soon as
the move began, sent all 5 messages.
When the move completed, the mail that was "in transit" was not delivered. waited
several hours, then reviewed the message tracking and saw that there was a 30
minute delay between when the server got it as "in transit" and when it rerouted
it.
In summary, if the 7 node E2K3 Cluster is separated from the Exchange 2000 servers
with a Routing Group Connector during the move and turn off the MTA, the "In
Transit" mail will be delivered with a 30 minute delay.
Modification Type: | Minor | Last Reviewed: | 10/6/2006 |
---|
Keywords: | kbhowto kbrapidpub KB924250 kbAudITPRO |
---|
|