标签：
The Exchange server includes an Endpoint Mapper (EPM) that listens on TCP port 135. The Outlook client connects to this port and is assigned random TCP server ports to communicate with the Exchange server using the MAPI protocol.
The conversation between the Outlook and the Exchange server is quite complex.
The following is a basic overview for the Exchange server communication:
1. The Outlook client contacts the directory service and DNS to establish the universal resource identifier (URI) for the Exchange server.
2. The Outlook client uses the URI to connect to the EPM server, and then it logs in to the Exchange server.
3. 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.
4. Using Name Service Provider Interface (NSPI), the Outlook client resolves the name of a recipient.
5. The Outlook client submits the message to the Exchange server for sending.
To enable the SteelHead to optimize encrypted MAPI traffic between Outlook and the Exchange Server:
1. On the server-side SteelHead, choose Optimization > Active Directory: Domain Join.
2. 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.
3. Verify that Outlook is encrypting traffic.
4. Enable the Encrypted Optimization option on client-side and server-side SteelHeads involved in optimizing MAPI encrypted traffic. Alternatively, use the CLI command protocol mapi encrypted enable.
5. 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.
6. Restart the service on all SteelHeads that have the Encrypted Optimization option enabled.
标签：
原文地址：http://www.cnblogs.com/elewei/p/5432577.html
