Exchange 2007 to 2013 migration

Posted on 2014-02-17
Last Modified: 2014-04-10
I'm migrating Exchange 2007 to Exchange 2013 using as a guide. I'm at step 8. I'm trying to get OWA and Active-Sync for the 2007 server to redirect through the 2013 server. When I change the NAT to point to the 2013 server, OWA for a 2013 user works fine, but when I log on as a 2007 user I get a blank page.

I have added legacy to the certificate. I setup an internal DNS for the public domain, pointing mail and autodiscover to the 2013 server, and legacy to the 2007 server.

What am i missing here?


Question by:cwconley
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39865320
Exchange 2007 does not proxy, it only redirects.
Therefore you need to ensure that you have an external URL populated within Exchange 2007 for


Author Comment

ID: 39865367
The external URL is forwarded to to the internal IP address of the 2013 server. The internal DNS points to the internal IP of the 2007 server.

Is this correct? Wil the 2013 server not  redirect to the 2007 server? Do I need to configure one of the virtual directories on the 2007 server with the external or internal URL of If so, which ones?

LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39865862 should go exclusively to the Exchange 2007 server, both internally and externally. All virtual directories on the Exchange 2007 server should be changed to use the legacy URL for at least internal traffic.
Outlook Anywhere and ActiveSync will be proxy-ed to Exchange 2007 by Exchange 2013 so those can be left without external URLs set.


Author Comment

ID: 39865954
If I change all the 2007 virtual directories' internal URL to, will disrupt outlook for the users on the 2007 server? Also when I make these changes will  will the external 2007 OWA users still use or will they use

LVL 63

Accepted Solution

Simon Butler (Sembee) earned 500 total points
ID: 39871439
If you change the URL to legacy, but the existing URL still resolves to Exchange 2007, then OWA will "correct" the URL for you.
The idea behind the two URLs is that you point the existing host name at the new platform, then let Exchange sort out whether it is redirected to the new host name or logs in to the mailbox on the new platform.


Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
SMTP Receive connector logging 1 44
AddressList in EXCH2013 6 38
EWS Throttling - The Budget for user X is locked out 8 66
Block Hacker? 2 37
Find out what you should include to make the best professional email signature for your organization.
In-place Upgrading Dirsync to Azure AD Connect
This video discusses moving either the default database or any database to a new volume.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit If you want to manage em…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question