exchangefaq.org
brought to you by Simpler-Webb

Table of Contents

  1. Administrivia
  2. Definitions
  3. Administration
  4. Setup/Upgrade
  5. Migration/Interoperability
  6. Transport
  7. Store
  8. Clustering
  9. ADC
  10. OWA
  11. OMA
  12. Outlook 2003
  13. What's New
  14. Tracking Log EventIDs
  15. Logon Modifications for OWA Users
  16. OWA Segmentation


Other FAQs

Exchange 2003 FAQ
Exchange 2000 FAQ
Exchange 5.5 FAQ


Exchange Resource Manager

Find out how you can manage rooms and resources though Exchange with out the hassles and complications of scripting!

» Download a free trial today

FAQs / Exchange 2003 / Outlook 2003

01


Client
  • Outlook 2003, Windows XP with Service Pack 1 + Q331320
Server-side
  • Exchange 2003 on Windows 2003 for FE (if FE is deployed)
  • Exchange 2003 on Windows 2003 for BE
  • Exchange 2003 on Windows 2003 for Public Folders
  • Exchange 2003 on Windows 2003 for System Folders
  • Windows 2003 for Global Catalog server
When used with the Microsoft Windows Server 2003 RPC Proxy Service and Exchange 2003, Outlook 2003 clients can connect simply using HTTP or HTTPS, thereby reducing the need for virtual private networks (VPNs) or dial-up remote access. If remote users only need to gain access to corporate messaging information, your IT department may not need to deploy VPN infrastructure. VPN-less access reduces costs and provides for increased security by ensuring that remote Outlook users don’t need access to the entire network.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1060)
Categories: Exchange 2003/Setup/Upgrade | Exchange 2003/Outlook 2003 |

02


Yes. Windows XP with Service Pack 1 + Q331320

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1125)
Categories: Exchange 2003/Outlook 2003 |

03


04


The following tables illustrate how RPC compression and buffer packing works on the wire between the Outlook client and Exchange Server.

Outlook 2002 against Exchange 2000 / 2003

Mode

Data Flow

Network Client

Buffer Size

Data Buffer Size

Size on Wire

Compressed

OnlineDownload/UploadLAN32Kb32Kb32KbNo
OnlineDownload/UploadWAN4Kb/8Kb4Kb/8Kb4Kb/8KbNo
OfflineDownload/UploadAll32Kb32Kb32KbNo

Outlook 2003 against Exchange 2003

Mode

Data Flow

Network Client

Buffer Size

Data Buffer Size

Size on Wire

Compressed

OnlineDownloadAll32Kb32Kb<32KbYes
OnlineUploadAll32Kb32Kb<32KbYes
CachedDownloadAll96Kb>96Kb96KbYes
CachedUploadAll32Kb32Kb<32KbYes
OfflineDownloadAll32Kb>32Kb32KbYes
OfflineUploadAll32Kb32Kb<32KbYes

The compression technology used between Outlook 2003 and Exchange 2003 is called XPRESS(tm) and is based on the Lempel-Ziv (LZ-77) algorithm. This is the same technology that Active Directory uses to perform compression of its’ RPC data when replicating between servers. All data over the size of 1 KB is compressed, and the technology is built into both client and server; therefore the compression is full duplex.

The compression gain is dictated by the message format and attachment(s) type. Because the compression is performed at the RPC level, all message data is compressed.

  • Plain text and HTML messages usually compress between 60% and 80% (on the wire saving)
  • Rich-text (RTF) messages usually compress up to 20% (on the wire saving)
  • Word documents compress down better than PowerPoint files


Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1127)
Categories: Exchange 2003/Outlook 2003 |