Forum Discussion

am_gli_287451's avatar
am_gli_287451
Icon for Nimbostratus rankNimbostratus
Jul 25, 2018

Outlook clients not working with iapp for exchange 2016

Hi,

I've just implemented the iapp for MS Exchange 2016. Everything works properly (OWA, EAS, etc.) - except the outlook clients themselves.

When starting Outlook with host-entries adapted to the F5 VS, Outlook isn't able to connect. We use a pretty simple setup with LTM for loadbalancing, SSL-Bridging, no AFM, no APM. All services share the same IP.

For Outlook clients, MAPI- and RPC-over-HTTP are chosen.

In the troubleshooting section of the deployment guide, there is a part regarding "clients experiencing Outlook connectivity issues", which would be a possible problem in our case, but even by adjusting the Idle-Timeout like suggested in the irule (CAS 15 minutes -> irule 1200 seconds), the problem still persists.

   when HTTP_REQUEST {
    switch -glob -- [string tolower [HTTP::path]] {
     "/ews*" -
     "/oab*" -
     "/mapi*" -
     "/rpc/rpcproxy.dll*" {
     TCP::idletime 1200
     return
     }
    }
   }

Any other ideas or hints, what or where to check?

Thanks!

application delivery
iApps
LTM

1 Reply

Sort By
  • am_gli's avatar
    am_gli
    Icon for Altostratus rankAltostratus
    Jul 25, 2018

    Self-resolved -> adding an additional irule to the configuration as proposed in the DG doesn't work. You have to adapt the generated irule "XXX_combined_pool_irule7":

        "/rpc/rpcproxy.dll*" {
         Outlook Anywhere.
        TCP::idletime 1200
        pool /Server_LAN/XXX_exc_int.app/XXX_exc_int_oa_pool7
        COMPRESS::disable
        CACHE::disable
        return
    }