locked
ActiveSync doesn't work for mailboxes moved to 2010 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have been using the 2010 CAS arrays to either redirect or proxy connections back to the 2007 environment for the 2007 mailboxes. In the case of ActiveSync, the externalURL field was set to something like "legacy.domain.com" to allow the 2010 CAS to do a redirect. On the EAS devices (e.g. iPhone/iPad), the server field was automatically changed from original setting of "mail.domain.com" to "legacy.domain.com" and all was good.

    The issue is that when a mailbox is moved to 2010, the activesync device still points to "legacy.domain.com" and stops working. In the "What happens when the user's mailbox is moved to Exchange 2010?" section of the "Upgrading Exchange ActiveSync to Exchange 2010" (The Exchange Team Blog) it says that CAS2007 will return a response (HTTP error code 451) indicating that the device should use "mail.domain.com" namespace (i.e. CAS2010) for all synchronization events and the device will automatically repoint. But that's not happening. I have verified the autodiscover settings and autodiscover is working fine based on every other test I have performed (including the connectivity analyzer). Also, creating a new profile on the an iDevice works just fine using ActiveSync autodiscover. The devices also work fine if I manualy change "legacy" to "mail" in their config, but it just won't happen automatically.

    Is there something else that I am missing? Is this a unique behavior with iDevices in particular?

    Thanks
    BSQRD1

    Wednesday, July 18, 2012 8:18 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Users may have to reconfigure their mail settings.  Autodiscover will do the heavy lifting, though.  Remember that mobile device manufacturers and device OS developers decide how to implement ActiveSync and not all (none?) do everything properly.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    • Marked as answer by Fiona_Liao Sunday, July 29, 2012 3:00 AM
    Wednesday, July 18, 2012 9:04 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Exchange 2010 will proxy ActiveSync so you should never have to do a redirect.

    This explains it all very well.

    http://technet.microsoft.com/en-us/library/bb310763.aspx

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    • Proposed as answer by Fiona_Liao Tuesday, July 24, 2012 8:58 AM
    Wednesday, July 18, 2012 8:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You are correct and actually changing the externalURL field on CAS2007 to $null (even in internet-facing site) appears to be a much better way to go as you had pointed out in a separate thread. I am not sure why most of the documentation I have seen says to change the externalURL to "legacy" and redirect.

    But that aside, if someone has already used redirection (which is at least a recommened method by Microsoft) and now has a bunch of ActiveSync devices pointing to "legacy" (i.e. CAS2007), are there automated ways to point them back to "mail" (i.e. CAS2010) when the mailbox is moved to 2010? "Upgrading Exchange ActiveSync to Exchange 2010" (The Exchange Team Blog) indicates that ActiveSync Autodiscover should do that (via HTTP error code 451), but it doesn't seem to work for me (the device simply says it cannot connect and remains disconnected indefinitely). Have you seen that work in your experience, or do we simply have to go the manual route?

    Thanks
    BSQRD1

    Wednesday, July 18, 2012 8:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Users may have to reconfigure their mail settings.  Autodiscover will do the heavy lifting, though.  Remember that mobile device manufacturers and device OS developers decide how to implement ActiveSync and not all (none?) do everything properly.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    • Marked as answer by Fiona_Liao Sunday, July 29, 2012 3:00 AM
    Wednesday, July 18, 2012 9:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Ed. I think you are right (users having to repoint manually). I haven't seen the behavior of mailboxes moved to 2010 automatically repointing to CAS2010 on any of the devices I have tried (iPhone/iPad with iOS 5.1.1, Windows Mobile 6.5, Android).
    Wednesday, July 25, 2012 6:42 PM