- Prepare Exchange 2013 – rename DB, move DB and logs to separate volumes, configure Send/Receive connectors, import Exchange 2007 transport rules
- Configure Exchange 2013 URL and Outlook Anywhere
- Request and Install a GoDaddy Multiple Domain Certificate (UCC) in Exchange 2013
- Import the new GoDaddy Certificate in Exchange 2007, configure Split-Brain DNS or PinPoint DNS zones
- Configure Exchange 2007 URL and double check the Outlook Anywhere configuration
- Perform the Switchover – enable the new certificate on Exchange 2007, check the autodiscover information provided to local clients, change firewall rules, test with remote OWA, Outlook Anywhere, and Web Services clients
- Move the Mailboxes to Exchange 2013
- Move the Public Folders to Exchange 2013
- Decommission Exchange 2007
One of the corner stones of the successful upgrade is configuring correctly the Exchange URL and implementing successfully the legacy namespace for local and remote clients. If you stumble on this task for the first time, it’s easy to get utterly confused with the multitude of FQDN that need to be set on both the legacy and the new Exchange servers. Add to this equation the need to request a new Exchange certificate and take care of the name resolution for local and remote clients, and you come up with the “logical” conclusion to save time and simplify the whole process by performing the upgrade without using the legacy namespace. Unfortunately, this turns out to be the wrong choice where you get a significant amount of downtime and a ton of complaints from the local users.
One of the popular misconceptions is that the legacy namespace is used only by remote clients and you can easily live with cutting them out for a weekend. Keep in mind that all internal clients will switch to Outlook Anywhere and, of course, you will end up with a period when resources are shared on both servers (ex. Exchange 2013 mailboxes accessing Exchange 2007 Public Folders). On the other hand, configuring the URL takes a minute or two – we provide the text file with the commands, just do you homework first. Add a couple of DNS records, and GoDaddy generates the requested certificate normally within 5 minutes.
Moving the Public Folders to Exchange 2013 will be a memorable moment in your career. At first glance, you might find the whole process quite
indigenous ingenious. When you see the logic behind, it is as simple and user unfriendly as possible. Quite often, the reason that you get stuck after locking the Exchange 2007 Public Folders is because you haven’t waited until the lock took effect and proceeded immediately with completing the PF migration. If you get in this situation, shut down the Exchange 2007 server for a couple of minutes – normally, you will get “Network Failure” when you check the Migration Request Statistics in Exchange 2013 management shell. Then, turn it on and resume the PF migration request.
Finally, there are cases when you don’t need to migrate the Public Folders as they are not used anymore. Please, don’t take the hatchet (ADSIEDIT) and start hacking as suggested by some specialists. There is a polite and intelligent way to finalize your upgrade without migrating the Exchange 2007 Public Folders, and we’ll be publishing a video on this topic within days.
In this Screencast , we complete the upgrade from Exchange 2007 to Exchange 2013.
Tweet #Exchange2013 Follow @netometer
Stay tuned on NetoMeter – subscribe to NetoMeter RSS.