Communications

The communication speed between Outlook 2003 and Exchange Server 2003 has been improved through the use of server-side compression and buffer packing, which returns information to the client using a large buffer packet and reduces the amount of communication between Outlook and Exchange.

Another enhancement in how Outlook communicates with Exchange Server is the introduction of HTTP access from Outlook. With HTTP or HTTPS access configured, you don't need to configure a virtual private network, remote access, and so on. You can just give Outlook users access to Exchange through an HTTP request.

This feature requires the use of the Windows Server 2003 RPC proxy service. To configure HTTP access, you need to configure one of your Exchange front-end servers as an RPC proxy server, which then manages which ports to use to communicate to other back-end components (such as Exchange servers, domain controllers, and global catalog servers).

CONNECTING THROUGH HTTP

For more information on connecting to Exchange through an HTTP connection, see Chapter 8 "Security," page 101.

You can configure HTTP access in a number of ways. Microsoft recommends that if you are going to allow HTTP access from outside your network, you should use an Internet Security and Acceleration (ISA) server as the connection point and leave your Exchange front-end servers contained within your own network, where they can have unfettered access to the different back-end components required.

For more information on configuring ISA Server for Windows Server 2003, visit http://www.microsoft.com/isaserver/techinfo/deployment/WindowsServer2003.asp.




Microsoft Exchange Server 2003 Delta Guide
Microsoft Exchange Server 2003 Delta Guide
ISBN: 0672325853
EAN: 2147483647
Year: 2003
Pages: 109

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net