Forum Discussion

k_kirchev_28437's avatar
k_kirchev_28437
Icon for Nimbostratus rankNimbostratus
Apr 12, 2018

Exchange 2016 does not work through F5, manually configured.

Hello Guys,

 

I am searching since last 5 days a way to implement Exchange 2016 through F5 without iApp. I strictly followed deployment guide but I have 50% success. OWA is working for Exchange 2016 users but Outlook still stays disconnected. I am not using ASM or APM. Even MAPI health check monitor stays down. Syntax of monitor is absolutely the same as OWA, Autodiscovery, Activesync, Outlook Anywhere, EWS but still same result - not working for Outlook 2016. Interesting is that without going through F5 it works perfect.

 

  • Hello,

     

    I deployed it last week without problem. can you tell me what you get as a mistake? (blank page, reset, ...?)

     

  • Probably the easiest way to look at this would be to deploy the iApp and see how the iApp's configuration differs from your manually configured setup (please verify that the iApp is working before comparing). You can contact F5 support and they will help you, but they will also tell you that the only supported way to do this is through the iApp.

     

    But yes, understanding how things are breaking would be helpful.

     

  • Hello Guys, this morning I am starting to deploy iApp template.

     

    About Exchange error - Outlook console stays disconnected.

     

    Outlook connection status console "status column" stays "connecting". And still MAPI healthcheck monitor(from guide) is not working. I think this is the key because https:///mapi is the link for outlook connections.

     

    Thank you both for the answers

     

  • This is connection status console:

     

    Please ignore lines in red - client confidential info.

     

  • Hello,

    it's seems that your monitor don't Work. and therefore your requests to backend are forcibly blocked.

    From F5, can you please check backend health:

    Connect to F5 CLI, then enter this command

    curl -i -k https://1.1.1.2/mapi/healthcheck.htm -H "Host: mapi.domain.com"

    1.1.1.2 is one of your exchange backend and mapi.domain.com will be the fqdn of your mapi service.

    You will obtain this:

    HTTP/1.1 200 OK
    Server: Microsoft-IIS/10.0
    X-Powered-By: ASP.NET
    X-FEServer: servname
    Date: Fri, 13 Apr 2018 07:48:07 GMT
    Content-Length: 29
    

    normally this url must be reachable and there must be no authentication on it.

    You will have the same result for :

    /Microsoft-Server-Activesync/healthcheck.htm

    /EWS/healthcheck.htm

    ...

  • I think I found it.. Please take a look at CLI http test bellow:

     

    It seems that http connection is Forbidden.

     

  • I have the same issue, i tried using iAPP but still outlook for clients keep disconnected but OWA is working fine , how can i fix it !