I'm looking to complete a migration from our current Exchange 2007 (all running on a single-server) to our new Exchange 2010 (also running on a single-server) with little-to-no downtime, if at all possible. Ideally, I would have the new Exchange 2010 Server acting as the primary, with clients routed to whichever server their mailbox lives at -- and this would be true for Outlook clients, OWA access, EAS connectivity, etc..
My understanding is that this is very
Anyhow, there are a number of good write-ups out there
, but I'm still somewhat gun shy about moving forward. A lot of my confusion comes from the order of steps
around pointing folks to the new server (with SSL certificate), how they're routed between the servers (depending upon whether their mailbox has been moved yet), and getting things like the Public Folders, which we still use, moved over.
WHERE I'M AT CURRENTLY
At this point, I have our Exchange 2010 Server set up and ready to use -- complete with SP1 and latest rollups. I was able to successfully migrate a test mailbox from Exch2007 to the new Exch2010 server, and it's working great. It can both send & receive email.
Currently, going to our primary OWA address (https://webmail.ourdomain.com
) gets you to your mailbox -- except for the test mailbox that I migrated to Exch2010. In that case, it gives a suggestion for a better URL, and takes you back to the login. If you go to the temporary OWA address of our new server (https://webmail2
.ourdomain.com), you'll get routed to the Exch2010 interface on the test mailbox, and then routed to the Exch2007 interface for the rest of the mailboxes. Interesting.
Our layout is as follows:
- Exchange 2010 Server
- Internal Name: MX10
- External Name: webmail2.ourdomain.com
- Exchange 2007 Server
- Internal Name: MX07
- External Name: webmail.ourdomain.com
1) What is the next step for getting our Exchange 2010 Server as the primary box in our setup?
2) Do I go ahead and get a new SSL certificate for the Exch2010 Server for our current external URL, webmail.ourdomain.com?
3) I've read about setting up an external DNS name, legacy.ourdomain.com, for the old server, and then point webmail.ourdomain.com at the new server. Does it route users to the old server automatically?
4) Assuming that users are pointing to the new server and have access to their mailbox, wherever it lives, does the Mailbox Move function allow for moving users in real-time while on-line?
5) Will these changes affect users who have smartphones already pointed to webmail.ourdomain.com?
I realize that I'm looking for an awful lot
of hand-holding here, but I tend to not mess with our Exchange setup as much as possible. I like it to "just work", and so do my users!
Thanks for your help,