System Center Capacity Planner 2007 is designed to model those features of Microsoft Exchange Server 2007 that are most commonly used. The following sections describe the basic architecture of the Exchange Server application model, the topology, transactions, and Exchange Server 2007 features that Capacity Planner models in addition to the features that are not modeled.
|Capacity Planner models only the configurations related to an Exchange Server 2007 deployment, not configurations affecting extended network performance.
Information in this section does not address product availability or recommended hardware best practices that are suggested by Microsoft. For additional information about Exchange Server 2007 architecture deployment best practices, see the Messaging Services Build Guide Web page on TechNet (http://go.microsoft.com/fwlink/?LinkId=56112).
Basic Exchange Server 2007 Architecture
Capacity Planner is designed to model only a single Exchange organization, which includes Mailbox-only sites and client-only sites. For most organizations, this is the lowest unit of administrative access or control. Capacity Planner predicts the utilization of all processors, disks, network links, and the latencies of transactions.
Exchange Server 2007 Topology Limits
Because of the extensive size and distributed nature of many Exchange deployments, only a subset of possible deployments is modeled. Only sites containing at least one Exchange server are modeled—you cannot use Capacity Planner to model Outlook Web Access clients alone.
The following table describes topology limitations in Capacity Planner for Exchange Server 2007.
The Edge Transport server role cannot be collocated with any other server role.
The Hub Transport server role can be collocated with the Client Access and Mailbox (unclustered and local continuous replication (LCR) server roles only.
The Client Access server role can be collocated with the Hub Transport and Mailbox (unclustered and LCR) server roles only.
As many as 300 server computers are modeled.
The following client profile types are included in the application model:
Modeled Transactions and Operations
The following transactions and operations are modeled in the Capacity Planner application model for Exchange Server 2007.
- ActiveSync Aggregate Workload
- All calendar operations
- All contact operations
- Browsing folders
- Message From Internet
- Outlook Aggregate Workload
- Outlook Anywhere Offline Aggregate Workload
- Outlook Anywhere Send Message
- Outlook Offline Aggregate Workload
- Outlook Offline Send Message
- Outlook Online Send Message
- Outlook Web Access Browse Calendar
- Outlook Web Access Browse Contacts
- Outlook Web Access Browse Folder
- Outlook Web Access Create Contact
- Outlook Web Access Create Meeting
- Outlook Web Access Delete Meeting
- Outlook Web Access Delete Message
- Outlook Web Access Logon
- Outlook Web Access Move Message
- Outlook Web Access Open Contact
- Outlook Web Access Open Meeting
- Outlook Web Access Open Message
- Outlook Web Access Send Message
- Reading, moving, and deleting email
|Exchange Server 2007 includes other transactions that are not modeled by Capacity Planner.
Supported Exchange Server 2007 Features
The following table describes the Exchange Server 2007 features that are modeled by Capacity Planner.
|Exchange Server 2007 Feature
An Edge Transport server role is deployed to your organization's perimeter network as a stand-alone server. The Edge Transport server is designed to minimize the potential of malicious attacks, and it handles all Internet-facing mail flow, which provides Simple Mail Transfer Protocol (SMTP) relay and smart host services for the Exchange organization. Additional layers of message protection and security are provided by a series of agents that run on the Edge Transport server and act on messages as they are processed by the message transport components.
The Hub Transport server role, which is deployed inside your Active Directory forest, handles all mail flow inside the organization, applies transport rules, applies journaling policies, and delivers messages to a recipient's mailbox. Messages that are sent to the Internet are relayed by the Hub Transport server role to the Edge Transport server role that is deployed in the perimeter network.
The Client Access server role supports the Microsoft Outlook Web Access and Microsoft Exchange ActiveSync client applications, and it supports the Post Office Protocol version 3 (POP3) and Internet Message Access Protocol version 4rev1 (IMAP4) protocols. Capacity Planner calculates the additional CPU utilization caused by Office Communicator on Client Access servers.
The Mailbox server role is main Exchange component that contains all message traffic and performs the main functions of an Exchange system. The Mailbox server role hosts mailbox databases, which contain users' mailboxes. All transactions involve the Mailbox. Each server that acts as a Mailbox is automatically configured with four storage groups, each with five mailbox databases. Capacity Planner calculates the additional CPU utilization caused by Office Communicator on Mailbox servers.
Capacity Planner can model the following clustering are replication types for the Mailbox server role:
Unsupported Exchange Server 2007 Features
The following is a list of Exchange Server 2007 features that Capacity Planner does not model:
- Editions other than Exchange Server 2007 Enterprise
Only Exchange Server 2007 Enterprise Edition is modeled.
- Outlook 2003 clients
Only Outlook 2007 clients are modeled.
- RTF and plain text messages
Only HTML format messages are modeled.
- Internet Protocol security (IPsec)
- Really Simple Syndication (RSS) feeds
- Outlook clients using remote procedure call (RPC) over HTTP in