Exchange 2010 - 2013 coexistence OWA and activesync issue

Exchange 2010 - 2013 coexistence with one mailbox moved to 2013.  We can send and receive using the 2013 mailbox internally as both servers are talking nicely to each other.  When trying to set up iphone to 2013, activesync errors on the 2010 server below:

The Exchange ActiveSync user Test has a mailbox on a Client Access server running a newer version of Exchange. Exchange ActiveSync doesn't support proxying users to Client Access servers running a newer version of Exchange. The user needs to connect to a newer Client Access server.

I am sure it is a simple solution.  It is important I am able to have both activesync working on both servers while migrating over 200 mailboxes as most users are setup with smart phones and cannot be without email for too long.
accucomAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
The error is pretty self explanatory - you need to direct external ActiveSync traffic at the new server and let Exchange proxy to the old server.
On the old server you will need to remove the external URL so that Exchange knows it needs to proxy.

Simon.
accucomAuthor Commented:
so just remove the external URL from Server Config - Client Access - Exchange ActiveSync?

Is this the same for OWA?  Will exchange 2010 auto redirect to mail.company.com/owa?
Simon Butler (Sembee)ConsultantCommented:
With OWA, if you have an external URL set, then it needs to be different to the one set in Exchange 2013, as Exchange will see that as a request to redirect rather than proxy.
If you remove the external URL then it will proxy the request to the Exchange 2010 mailbox.

For anyone else reading - that does not apply to Exchange 2007, which can only redirect.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.