• Annoying Bugs Fixed - Exchange 2007 fixes a lot of irritating problems from previous versions, including the 32kb rules limit and annoying behaviors within calendaring. While these are all relatively small, the number of fixes is impressive and makes for a better product.
• 64 bit Architecture - Exchange 2007 uses 64 bit architecture, a big move from past versions. While this change will give you more application horsepower, it comes with a price – you will have to upgrade to 64 bit hardware before upgrading, as there is no 32 bit version of Exchange 2007. Obviously a key planning and budgeting issue.
• High Availability - Exchange 2007 features improved mailbox availability through the introduction of two new features: Local Continuous Replication (LCR) and Continuous Cluster Replication (CCR). A big deal if you are committed to aggressive service levels. Both of these use Log Shipping technology and will be discussed in more detail in future articles.
• Exchange 2007 Server Roles - At install time administrators select the specific role or roles (groups of features or functions) they want each Exchange 2007 server to perform. Only the components needed for that role are installed (whereas Exchange 2003 installed everything). Exchange 2007 roles are as follows:
  • Mailbox – self explanatory, installs the ESE (Jet) database to store mailboxes and public folders.
  • Client Access – similar to Exchange 2003 front end server. Installs components and protocols to support Outlook Web Access (OWA), POP3, IMAP4, Active Sync and Outlook Anywhere (AKA MAPI RPC over HTTP).
  • Unified Messaging – enables users to receive voicemail and faxes, as well as email and calendar items, in their Exchange mailbox. A cool speech-enabled auto attendant provides touch tone access to interact with email and calendar over the phone.
  • Hub Transport – configures Exchange 2007 to perform functions like Exchange 2003 bridgehead servers. But now all email must pass through a Hub transport function – even email for a recipient on the same mailbox server as the sender. Exchange 2007 compliance features (transport rules) are available because all mail must pass through Hub Transport. More on Exchange 2007 compliance in future articles. Hub Transport now uses Active Directory site definitions rather than Exchange routing groups to configure connectivity across the WAN.
  • Edge Transport – processes and routes email to and from the internet. Designed to live outside the firewall (not a member of the Domain). Uses a read-only copy of Active Directory user data to validate in-bound email addresses.

These and other architectural changes drive a lot of functionality, but the above list only scratches the surface of what’s in Exchange 2007. Learn more by reading our other articles on Exchange 2007.

Back to News & Events