locked
Exchange 2010 & Exchange 2016 Co-existence ActiveSync Not working on Exchange 2016 but works on Exchange 2010 RRS feed

  • Question

  • Exchange 2010-2016 coexistence  Email is working, OWA is working. All email is still configured to send out of 2010 server. ( I have not updated the send connector for the 2 new exchange 2016 servers)  I have not been able to get Activesync to work for any mailbox on the new exchange 2016 servers.   Getting error that says failed to detect activesync. http status 505    All mailboxes on 2010 are working fine with active sync.  All phone users are getting email on their phone on 2010 server.  I moved my mailbox to 2016 server and cannot get email on phone.   also getting this in events  

    Exchange ActiveSync device requests for your users are being blocked. This problem frequently occurs when the HTTP OPTIONS method request isn't allowed by the firewall. Please check the firewall that filters requests in front of your Client Access server and the Microsoft-Server-ActiveSync virtual directory.

    We use a third party system called Maas360 to manage our cell phones connecting to exchange.   This is now configured to point to the first 2016 exchange server (2 server DAG environment) and all phones are working for our 2010 server just not 2016.

    Not really sure where to go from here...


    Jeff Tresnak

    Monday, January 29, 2018 7:07 PM

Answers

  • Problem was activesync was still pointing to 2010 server once changed to 2016 this error went away.

    Jeff Tresnak

    • Marked as answer by Jeff Tresnak Friday, February 9, 2018 1:03 PM
    Friday, February 9, 2018 1:03 PM

All replies

  • Hi Jeff,

    According to your description, you need to publish Exchange 2016 server to internet, and all namespaces need to be moved to resolve to Exchange 2016 Client Access component infrastructure, then Exchange 2016 will handle all client requests, for mailboxes sitll on Exchange 2010, it will proxy the request to Exchange 2010 CAS server, for mailboxes on Exchange 2016, it will proxy the request to the Exchange 2016 mailbox server directly.

    Details see: Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2010


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.



    • Proposed as answer by Niko.Cheng Tuesday, January 30, 2018 8:13 AM
    • Edited by Niko.Cheng Tuesday, January 30, 2018 8:13 AM
    Tuesday, January 30, 2018 8:13 AM
  • Hi Niko

    The problem isn't that all exchange 2010 requests for mobile phone access isn't being handled. IT is working just fine.   The problem is my mailbox which was working on the exchange 2010 server does not work from a mobile phone perspective on 2016.

    We do not allow Outlook Web Access from the Internet.  This has been turned off for some time.  We Do allow company owned mobile phones to be used but only through the Maas360 application.  This worked when it was pointed to the old Exchange 2010 server and it is working now that is pointing to the new 2016 server only for mailboxes on 2010.  My mailbox does not work on my cell phone because it is now on exchange 2016.   I'm testing internally (LAN) using an activesync tester and it fails for the 2016 server but passes for the 2010 server.  

    Thanks for your help!!!

    Jeff


    Jeff Tresnak

    Tuesday, January 30, 2018 2:53 PM
  • So now I'm getting this event on my 2010 CAS server.   MY MAAS application is connecting to my 2016 server and see's both mailbox servers.     For some reason when I try and authenticate on my cell phone this error ends up on the 2010 server.   I have changed all activesync Virtual directory servers to resolve to the new 2016 server internal and external (except the original 2010 server)

    Log Name:      Application
    Source:        MSExchange ActiveSync
    Date:          2/1/2018 9:17:47 AM
    Event ID:      1052
    Task Category: Configuration
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      S-EXCA-01.EHIMRX.local
    Description:
    The Exchange ActiveSync user EHIMRX.local\2016jefftest 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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ActiveSync" />
        <EventID Qualifiers="32772">1052</EventID>
        <Level>3</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2018-02-01T14:17:47.000000000Z" />
        <EventRecordID>766342</EventRecordID>
        <Channel>Application</Channel>
        <Computer>S-EXCA-01.EHIMRX.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>EHIMRX.local\2016jefftest</Data>
      </EventData>
    </Event>


    Jeff Tresnak

    Thursday, February 1, 2018 4:08 PM
  • Problem was activesync was still pointing to 2010 server once changed to 2016 this error went away.

    Jeff Tresnak

    • Marked as answer by Jeff Tresnak Friday, February 9, 2018 1:03 PM
    Friday, February 9, 2018 1:03 PM