Exchange Server 2010 Learning (i) Understanding Exchange roles

According to the overall work arrangement of the Department, this year and even longer period of time, my main task will be responsible for several customer exchange projects. Take this opportunity to write a series of articles about Exchange Server. The purpose of this is to comb the rich features of Exchange Server2010 and its deployment and maintenance points for future inspection.

Exchange Server 2010 is divided into standard and Enterprise editions. The Enterprise Edition can support 100 databases per server, and Standard Edition is limited to 5 databases per server. and two licensed versions defined by the product key. The product key can be used only for exchanges and upgrades of the same version key, and the product key is not available for demotion. That is, you can move from a trial version to a standard or enterprise version using a valid product key, or move from a standard version to an Enterprise edition, or change a product key on the same version. No reinstallation or reconfiguration is required.

Microsoft, on the basis of Exchange Server SP1/SP2, officially released on February 12, 2013 to support the SP3 installed under Windows Server 2012, Enterprise users can download as needed.

This series of articles will take the Exchange Server SP1/SP2 as an example, starting with an understanding of the Exchange Server 2010 architecture, to introduce its deployment, role configuration management, mail \ Mailbox Management, backup recovery, high availability, and exchange migration. Let's take a look at the architecture of the Exchange Server2010 first.

Exchange 2010 is essentially the same architecture as Exchange2007, using 5 roles: The Client Access server role (CAS), The Hub Transport role (HT), the Mailbox database role (MBX), the Edge Transport server role (EDGE), Unified Communications Server Role (UM). But friends who have contacted Exchange Server2013 may know that the roles in Exchange 2013 will change, but this is something, and you'll have a chance to chat later.

1. Client Access server role

You can look at names. This is the role of processing client access requests, and Exchange2010 CAS roles have changed a little in comparison with the CAS role of Exchange 2007. In Exchange 2007, if clients are using Outlook, customers can use a connection to a mailbox server, but if they are using a different way to access mailboxes, such as POP3, OWA, IMAP4, ActiveSync, and so on, they cannot access the mailbox server directly. , they are connected directly to the client Access server, and then the server navigates the user to the mailbox server. However, in Exchange 2010, all client access requests are connected to the CAS server, authenticated, and then transferred to the appropriate mailbox server through the agent.

High Availability requirements: With regard to the high availability of client Access server roles, Microsoft recommends the use of hardware devices, but it can also be implemented using Windows NLB in SMEs.

Deployment requirements: This role must exist in the Exchange messaging system and must be added to the AD DS domain.

2. Hub Transport Role

The main role of the Hub Transport role is to complete mail delivery, applications such as message transfer rules, mail log rules, and within the organization, Hub Transport roles are responsible for the delivery of messages between different mbx, and if the Edge Transport server role is not installed, the Hub Transport role forwards and receives Internet mail. If you have an Edge Transport server role installed, external Internet Mail is responsible for this role, but the organization's internal messages are always responsible for the Hub transport role.

High availability requirements: the high availability of hub transport roles does not require a separate configuration, as long as multiple Hub Transport role servers are deployed in the same AD site, load Balancing can be achieved automatically between multiple servers.

Deployment requirements: This role, like the CAS role, must exist in the Exchange messaging system and be added to the AD DS domain. This role can be deployed on the same server as the CAS role when the network size is small.

3. Mailbox Database role

The primary role of this role is to load mailbox databases, public folder databases, to generate offline address books, and to manage mailbox-level databases, such as addresses lists, message retention policies, and so on. This server role is responsible for storing the contents of the client mailbox in the database, including users ' mailboxes and public folders, and does not transfer messages between mailboxes.

High availability requirements: The high availability of this role is implemented through DAG deployed on Windows clusters, where a DAG can deploy 15 mailbox database replicas, with replication technology for data synchronization between replicas.

Deployment requirements: This role must exist in the Exchange messaging system and must be added to the AD DS domain.

4. Edge Transport server role

The Edge Transport server role is typically deployed in the DMZ zone, which is responsible for sending and receiving messages on all over the Internet, and forwarding messages to external messages by the Hub Transport role within the Organization to the Edge Transport server role to complete external mail delivery. When external messages are received, they are first passed to the Edge Transport server role, which is forwarded to the internal Hub transport role after anti-spam and antivirus checks. Therefore, you need to replicate the recipient list and related settings information.

Deployment requirements: This role must exist as a stand-alone server role, in the general environment as an optional server role.

5. Unified Communications Server role

This role is responsible for combining the message with the voice. As early as Exchange 2007, voice Mail has appeared, the current version of this technology has been developing, especially with Lync, powerful. For example, a phone call comes in, and if the user is not there, no one is answering. The other person can leave a message. The content of the message can be converted to a voice mail. After the user has opened, it can be played automatically.

Deployment requirements: When you deploy this role, you must join the AD DS domain, and this role does not need to be deployed if there is no unified information requirement.

Exchange2010 five roles, except that the edge role is deployed as a stand-alone server in the DMZ area of the firewall, the other roles are deployed in the enterprise internal network and joined to the AD DS domain. And when it comes to real deployment, you need to take into account the cost of enterprise input, server performance, scalability and other factors to design deployment scenarios.

Small Business:

Small businesses use input costs as a primary reference, and in general, small businesses do not have voice mail requirements, so there is no need to install the Unified Communications Server role, but require such a role to be deployed on a separate server. Similarly, instead of installing the Edge Transport server role based on cost considerations, you are using a Hub transport role to implement Internet mail delivery, anti-spam, antivirus messages, and so on. So you can install the MBX, CAS, HT three roles on the same server, as shown in the following illustration: