1) For moves within the site (ie – the moves that you’ve always been able to do), or for moves between sites when you’re in Exchange 200x native mode, you do NOT need to do anything with the Outlook profile. Outlook will attempt to connect to the original server the next time you start Outlook and will be automatically redirected to the proper server.

Migration Grunt –

When you login to the mailbox after the mailbox has been moved, you will make a connection to the original mailbox server (presuming this server is still up and running). This server will “know” that the mailbox has been moved (because it can consult the directory and see the updated HomeMDB/HomeMTA). The original server will then “tell” the Outlook client “hey, you’re on SERVER-X now” and Outlook will update its profile to reflect this automatically.

So, in short, sure there are things that can break this process. But so long as the original server is still up and running, and so long as the directory is updated and replicating properly, this process should be quite automatic.

You Had Me At EHLO… : How does move mailbox really work?:

Somewhere buried in the documentation I’ve read is this gem… when you are in the process of “Move mailboxes” the client/Outlook has to close and reopen one time once the mail has been moved over.

Once that runs and says it’s successful, you need to have the users close and reopen their Outlook.  As was pointed out by Axel Larson, this is obviously going to work the best while that SBS 2003 is still up.  So … what’s a gal to do on a Thanksgiving weekend when everyone has left and you want to ensure the boss’s email account works?

You reset his password is what you do and log into his workstation/profile and make sure it works.  For people that you aren’t as nice to (let’s be realistic here) you keep the box up until past Monday morning. 

But the way to check is close and reopen Outlook.  It should now point to the new server in the exchange server settings under the hood.


Comments are closed.