willux
asked on
Exchange 2010 to Exchange 2010 migration
Hi experts,
I do have get a few questions related to a migration between Exchange 2010 , source server running on domain A to a new Exchange 2010, destination server, setup running on domain B.
First of all: the trust between the both domains is already in place and working properly (by using ADMT).
Mail flow from and to the destination server has been tested and works properly.
Next step will be the migration of the mailboxes from source server to destination server (by using PrepareMoveRequest.ps1).
Questions I do have:
1) While migrating a mailbox: what will happen with the incoming mail for that particular mailbox, will it be delivered into the mailbox on the destination server after the migration ?
2) As long as you don’t click on the remove move request (after migration), will the original data of the mailbox reside on the source server (it’s obvious we can’t afford to lose any data at all) ?
3) While the migration process takes places, there will be users with mailboxes on both servers.
Are there any additional next steps required to route mail properly between servers (by using routing groups) ?
Example: User A (still on source server, domain A), sends a mail to user B, who is already migrated (on destination server domain B), will user B receive that internal mail ?
4) Same question goes for user B (on destination server) mailing to user A (on source server) ?
5) Final question, what with the external mail for user B (on destination server), MX records will be left alone, during migration, so pointing to the source server, will the source server automatically deliver the mail to the destination server ?
Many thanks for clearing out my questions, although we did several Exchange migrations, the end client allowed a disturbed mail flow (mail was filtered / kept for delivery by using a SPAM firewall, so no mails where lost), in this case a disturbed mail flow is not allowed , only an temporary “offline” user mailbox during its particular mailbox migration.
I do have get a few questions related to a migration between Exchange 2010 , source server running on domain A to a new Exchange 2010, destination server, setup running on domain B.
First of all: the trust between the both domains is already in place and working properly (by using ADMT).
Mail flow from and to the destination server has been tested and works properly.
Next step will be the migration of the mailboxes from source server to destination server (by using PrepareMoveRequest.ps1).
Questions I do have:
1) While migrating a mailbox: what will happen with the incoming mail for that particular mailbox, will it be delivered into the mailbox on the destination server after the migration ?
2) As long as you don’t click on the remove move request (after migration), will the original data of the mailbox reside on the source server (it’s obvious we can’t afford to lose any data at all) ?
3) While the migration process takes places, there will be users with mailboxes on both servers.
Are there any additional next steps required to route mail properly between servers (by using routing groups) ?
Example: User A (still on source server, domain A), sends a mail to user B, who is already migrated (on destination server domain B), will user B receive that internal mail ?
4) Same question goes for user B (on destination server) mailing to user A (on source server) ?
5) Final question, what with the external mail for user B (on destination server), MX records will be left alone, during migration, so pointing to the source server, will the source server automatically deliver the mail to the destination server ?
Many thanks for clearing out my questions, although we did several Exchange migrations, the end client allowed a disturbed mail flow (mail was filtered / kept for delivery by using a SPAM firewall, so no mails where lost), in this case a disturbed mail flow is not allowed , only an temporary “offline” user mailbox during its particular mailbox migration.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.