Planning and Architecture
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2008-11-17
An increasing number of businesses today regard messaging systems as mission-critical systems. Therefore, companies have strict reliability and availability requirements for their e-mail systems. Equally important is the heightened demand for new messaging system features. An increasingly mobile work force and more geographically dispersed businesses mean that user requirements are continually evolving. These factors place demands on information technology (IT) managers and system architects, who are charged with designing highly reliable and consistently available messaging systems that meet users' needs.
Before you deploy Microsoft Exchange Server 2007, we recommend that you review the following topics, which provide guidance on planning for the supported Exchange organization models (Simple, Standard, Large, and Complex):
In addition to the content listed above, you can use other technical content in "Planning and Architecture" to design the ideal Exchange solution to meet your business needs. You can also use this information to plan for the use of specific features, such as compliance, address rewriting, anti-spam antivirus features, and more. For more details, see the following topics:
Exchange 2007 introduces several architectural changes from previous versions of Exchange Server. Many features and components have been redesigned, some features have been removed, and several new features have been added.
The following topics discuss Exchange 2007 architecture from an IT professional perspective:
Architectural information for developers is in the Microsoft Exchange Server 2007 SDK Documentation.