Active Sync Cross-Site Redirection failure

Hi Team,

We have below Exchange Configuration

Sites - 2 sites (Active, Active)
DB copies - 2 copies in Site 1
                     1 copy in Site 2 (Remote passive)
2 sites have separate Internet facing with separate name spaces

Users mailboxes are distributed between 2 sites Exchange 2010 MBX servers.  

Due to capacity and performance issues, we are in position to move mailboxes and mount databases to the alternate sites.

When the mailboxes are activated in alternate site, OWA works fine by redirecting to home OWA URLs.  But mobile Activesync users having issues of not synchronizing the emails until they modify the OWA URL for the other site.

Why the mobile devices are not automatically configured when are moved/activated in the other site.  

Any suggestions for silent configuration for Active sync.

Who is Participating?

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

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:
Have you read the proxy/redirection article at Microsoft?
This is the key quote:

Exchange ActiveSync users who access an Internet-facing Client Access server in a different Active Directory site than the site that contains their mailbox can be redirected to the Client Access server in the same site as their Mailbox server if that Client Access server is Internet facing and if the client mobile phone or device has correctly implemented the redirection logic built in to the protocol that's used when communicating with Exchange 2007 and Exchange 2010.

The big bit there is at the end.
In my experience, most ActiveSync devices do not have the redirection logic built in, so you have to proxy the traffic instead. That means taking out the external URL on the second server so Exchange knows to proxy the traffic.


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

From novice to tech pro — start learning today.