About Outlook Anywhere
Outlook Anywhere acceleration requires that HTTP optimization is also enabled on server-side and client-side SteelHeads. For HTTPS, you’ll need to also enable SSL on the server-side appliance, and the IIS certificate must be installed there.
Outlook Anywhere creates twice as many connections on the SteelHead than regular MAPI. Enabling Outlook Anywhere acceleration results in the SteelHead entering admission control twice as fast than with regular MAPI.
Accelerated Outlook Anywhere connections can’t start MAPI prepopulation.
Other considerations:
• When using HTTP, only NTLM proxy authentication is available.
• When using HTTPS, NTLM or Basic proxy authentication are available.
• When using encrypted MAPI with HTTP or HTTPS, you must also enable and configure encrypted MAPI in addition to this feature.
When automatic detection of Outlook Anywhere connections is enabled, appliances automatically detect Remote Procedure Call (RPC) over HTTPS connections. Autodetect is best for simple SteelHead deployments with only a single appliance at each site and when the IIS server is also handling websites.
If the IIS server is only used as RPC Proxy along with asymmetric routing, connection forwarding or Interceptor installations, add in-path rules that identify the RPC Proxy server IP addresses and set the latency optimization policy to Outlook Anywhere. Disable Outlook anywhere autodetection after you add the in-path rule. On an Interceptor, add load-balancing rules to direct traffic for RPC Proxy to the appliance.
In-path rules interact with autodetect as follows:
• When autodetect is enabled and an in-path rule doesn’t match, appliances accelerate Outlook Anywhere if they detect the RPC over HTTPS protocol.
• When autodetect is not enabled and an in-path rule doesn’t match, appliances don’t accelerate Outlook Anywhere.
• When autodetect is enabled and the in-path rule matches with HTTP only, appliances don’t accelerate Outlook Anywhere, even if it detects the RPC over HTTPS protocol.
• When autodetect is not enabled and the in-path rule doesn’t match with HTTP only, appliances don’t accelerate Outlook Anywhere.
• When autodetect is enabled and the in-path rule matches with an Outlook Anywhere latency optimization policy, appliances accelerate Outlook Anywhere, even if it doesn’t detect the RPC over HTTPS protocol.