About MAPI optimization
You display and modify MAPI optimization settings under Optimization > Protocols: MAPI.
MAPI optimization requires a separate license that is included with the BASE license. This feature is enabled by default.
RiOS uses the SteelHead secure inner channel to ensure all MAPI traffic sent between the client-side appliance and the server-side SteelHeads is secure. You must set the secure peering traffic type to All.
You must enable MAPI optimization on all SteelHeads optimizing MAPI in your network, not just the client-side appliance.
Set up secure peering between the client-side appliance and server-side SteelHead and enable inner channel SSL with secure protocols.
Under Settings, these configuration options are available:
Enable MAPI Exchange Optimization
Enables the fundamental component of the MAPI optimization module, which includes optimization for read, write (receive, send), and sync operations.
By default, MAPI Exchange optimization is enabled.
Only clear this check box to disable MAPI optimization. Typically, you disable MAPI optimization to troubleshoot problems with the system. For example, if you are experiencing problems with Outlook clients connecting with Exchange, you can disable MAPI latency acceleration (while continuing to optimize with SDR for MAPI).
Exchange Port
Specifies the MAPI Exchange port for optimization. Typically, you do not need to modify the default value 7830.
Enable Outlook Anywhere Optimization
Enables Outlook Anywhere latency optimization. Outlook Anywhere is a feature of Microsoft Exchange Server 2003, 2007, and 2010 that allows Microsoft Office Outlook 2003, 2007, and 2010 clients to connect to their Exchange Servers over the internet using the Microsoft RPC tunneling protocol. Outlook Anywhere allows for a VPN-less connection as the MAPI RPC protocol is tunneled over HTTP or HTTPS. RPC over HTTP can transport regular or encrypted MAPI. If you use encrypted MAPI, the server-side SteelHead must be a member of the Windows domain.
Enable this feature on the client-side and server-side SteelHeads.
By default, this feature is disabled.
To use this feature, you must also enable HTTP Optimization on the client-side and server-side SteelHeads (HTTP optimization is enabled by default).
If you are using Outlook Anywhere over HTTPS, you must enable SSL and the IIS certificate must be installed on the server-side SteelHead:
• When using HTTP, Outlook can only use NTLM proxy authentication.
• When using HTTPS, Outlook can use NTLM or Basic proxy authentication.
• When using encrypted MAPI with HTTP or HTTPS, you must enable and configure encrypted MAPI in addition to this feature.
Outlook Anywhere optimized connections cannot start MAPI prepopulation.
After you apply your settings, you can verify that the connections appear in the Current Connections report as a MAPI-OA or an eMAPI-OA (encrypted MAPI) application. The Outlook Anywhere connection entries appear in the system log with an RPCH prefix.
Outlook Anywhere creates twice as many connections on the SteelHead than regular MAPI. Enabling Outlook Anywhere latency optimization results in the SteelHead entering twice as fast than with regular MAPI.
For details and troubleshooting information, see the SteelHead Deployment Guide - Protocols.
For details about enabling Outlook Anywhere, see
http://technet.microsoft.com/en-us/library/bb123513(EXCHG.80).aspx.
Auto-Detect Outlook Anywhere Connections
Automatically detects the RPC over HTTPS protocol used by Outlook Anywhere. This feature is dimmed until you enable Outlook Anywhere optimization. By default, these options are enabled.
You can enable automatic detection of RPC over HTTPS using this option or you can set in-path rules. Autodetect is best for simple SteelHead configurations with only a single SteelHead at each site and when the IIS server is also handling websites.
If the IIS server is only used as RPC Proxy, and for configurations with asymmetric routing, connection forwarding or Interceptor installations, add in-path rules that identify the RPC Proxy server IP addresses and select the Outlook Anywhere latency optimization policy. After adding the in-path rule, disable the autodetect option.
On an Interceptor, add load-balancing rules to direct traffic for RPC Proxy to the same SteelHead.
In-path rules interact with autodetect as follows:
• When autodetect is enabled and the in-path rule does not match, RiOS optimizes Outlook Anywhere if it detects the RPC over HTTPS protocol.
• When autodetect is not enabled and the in-path rule does not match, RiOS does not optimize Outlook Anywhere.
• When autodetect is enabled and the in-path rule matches with HTTP only, RiOS does not optimize Outlook Anywhere (even if it detects the RPC over HTTPS protocol).
• When autodetect is not enabled and the in-path rule does not match with HTTP only, RiOS does not optimize Outlook Anywhere.
• When autodetect is enabled and the in-path rule matches with an Outlook Anywhere latency optimization policy, RiOS optimizes Outlook Anywhere (even if it does not detect the RPC over HTTPS protocol).
• When autodetect is not enabled and the in-path rule matches with Outlook Anywhere, RiOS optimizes Outlook Anywhere.
Enable Encrypted Optimization
Enables encrypted MAPI RPC traffic optimization between Outlook and Exchange. By default, this option is disabled.