The simple form is included as part of Microsoft Outlook Express and is not discussed here. Outlook versions have followed in close coordination. RiOS can perform optimization for each of these Exchange versions.
For information about Exchange , see Microsoft Exchange optimization. Because of the requirements of Exchange , the Exchange server communicates using an encrypted conversation with compatible versions of the Outlook client. By default, the encryption mode is enabled in Exchange and Exchange Cached Exchange Mode was introduced with Outlook Cached Exchange Mode attempts to hide performance issues over the WAN by preemptively downloading new email and their attachments from the Exchange server to a cache of storage on the local hard disk of the Outlook client workstation.
Although this gives an appearance of fast performance, it has no effect on emails going to the sent items or trash folder of the user. Using Cached Exchange Mode also means that any mail, including unwanted or junk mail and attachments , is downloaded to the Outlook client. These MAPI connections are used to send and receive emails, calendaring, address lookup, and more.
The conversation between the Outlook client and the Exchange server is quite complex. The following is a basic overview for the Exchange server communication:. The Outlook client performs remote operations ROPs to open that is, create and write a new email message, saves the changes, and creates and adds an attachment, if needed.
The Outlook client submits the message to the Exchange server for sending. Other conversations between the Outlook client and the Exchange server include opening folders for reading or searching, deleting items, and synchronizing folders. Synchronizing folders is required to download and read emails from the Exchange server to the Outlook inbox.
Figure: Outlook Client and Exchange Server synchronization shows the synchronization process. The incremental change synchronization ICS state is how the client knows what new items to download from the Exchange server.
Figure: Outlook Client and Exchange Server synchronization. Source: http:www. For Outlook client connections that are configured for correct addressing, the client-side SteelHead alters the port that the EPM service sends to the Outlook client for MAPI connections default is port If the Outlook client connections to the Exchange server are intercepted and optimized, MAPI-specific optimized connections are not used when the client-side SteelHead has an in-path rule to pass-through traffic on TCP port or the server-side SteelHead has a peering rule to pass-through traffic on TCP port Although this gives some performance benefits to new MAPI connections especially in large latency WANs , it also means that configuring pass-through or other types of in-path rules might not have the immediately desired impact on traffic.
Note: Always use the in-path probe-mapi-data command to perform autodiscovery for MAPI connections and to allow in-path rules to have immediate impact, even on Outlook clients that are currently optimized. When using fixed-target rules to optimize MAPI traffic, configure the client-side SteelHead to optimize traffic where the destination IP address is the Exchange server and the destination port is or whatever port is configured on the client-side SteelHead for MAPI optimization.
If you want optimization for NSPI connections, a fixed-target rule in which the destination IP address is the Exchange server and where the destination port is or whatever port is configured on the client-side SteelHead for NSPI optimization. The MAPI optimization module comprises several optimization techniques:. This setting uses port and is enabled by default. If the Exchange server is not configured to use random ports allocated by EPM and needs to use a fixed port configured by the administrator, you must change port to the fixed port number used by the Exchange server.
This is especially useful in global organizations where communication to a user continues long after local business hours. MAPI prepopulation considerably reduces the bandwidth consumed by a branch office when users start their day, and it can greatly accelerate the reception of mail when a user first connects to an Exchange server. The session begins if the following conditions are met:. No user credentials are used or saved by the SteelHead when performing prepopulation.
The remote SteelHead uses these preauthenticated connections to pull the data for mail from the Exchange server over the WAN link, automatically prepopulating the client-side RiOS data store. If for some reason the MAPI prepopulation session does not terminate for example, the user starts a new session in a location that is different than the SteelHead that has the MAPI prepopulation session active , the MAPI prepopulation session will eventually time-out per the configuration setting.
In RiOS 6. This allows for a higher rate of prepopulated sessions, and it enables MAPI prepopulation to take advantage of the read-ahead mechanisms in the MAPI optimization feature. The client-side and server-side SteelHeads can be at any of these code train levels and provide prepopulation v2 capabilities. In contrast, a 6.
This is helpful in scenarios where the user returns to the branch office and is assigned a different IP address by DHCP. In MAPI prepopulation v1 where just the IP address was tracked , the prepopulation session could have remained until the connection timed out default 96 hours.
When optimizing encrypted MAPI traffic, normal encryption methods are maintained between the Outlook client and client-side SteelHead and between the Exchange server and server-side SteelHead. For detail, see the SteelHead Deployment Guide. Figure: Encrypted connections between client and server. Join the server-side SteelHead to the same Windows domain that the Exchange server belongs to and operates as a member server.
The server-side SteelHead must be able to ping the domain controller by name. Verify that Outlook is encrypting traffic. Alternatively, use the protocol mapi encrypted enable command. Use transparent mode for all client types. Delegate mode is a legacy feature and should migrated to transparent mode, unless you have a specific need for Kerberos Constrained Delegation.
Restart the service on all SteelHeads that have the Encrypted Optimization option enabled. The Windows Security section also provides information about the relevant, earliest version of RiOS to ensure support for different Windows client operating systems and Windows domain structures.
For more information about how to ensure the SteelHead is joined to the domain, as well as configuring transparent or delegation modes, see Domain relationships. You can confirm that the SteelHead is successfully performing encrypted MAPI optimization by going to the SteelHead Management Console Current Connections report and looking for the highlighted lock icon listed in the Applications column of the report page.
This facility allows you to access Exchange account remotely using Internet when you are not in the organization. Outlook Anywhere can be executed through several requirements. Your Exchange server and system must be set to these requirements in order to utilize this facility.
This includes following requirements;. Exchange administrator can configure copies of Outlook or it provides a special executable script file, which enables "Outlook Anywhere".
Manually this feature can be configured when these requirements are fulfilled. Users must have correct URL and security details also about the Exchange administrator.
If this option is unavailable, the system might not fulfill all the requirements. In order to specify the proxy server, click on Exchange Proxy Settings. Here provide the URL provided by Exchange administrator. This allows traffic to traverse network firewalls without requiring RPC ports to be opened. In Exchange , this feature is enabled by default, because Exchange doesn't allow direct RPC connectivity. Outlook Anywhere offers the following benefits to clients that use Outlook , Outlook , or Outlook to access your Exchange messaging infrastructure:.
In Exchange , Outlook Anywhere is enabled by default, because all Outlook connectivity takes place via Outlook Anywhere. The only post-deployment task you must perform to successfully use Outlook Anywhere is to install a valid SSL certificate on your Client Access server. Mailbox servers in your organization only require the default self-signed SSL certificate. If you are planning to install Exchange in a coexistence scenario with previous versions of Exchange Server, you might still have Outlook clients in your organization.
Outlook is not a supported client for Exchange Before you move your namespace to Exchange , you need to ensure that all Outlook clients have been upgraded to the minimum supported version.
0コメント