Detailed server roles for Exchange Server 2013

In Microsoft Exchange Server 2010, the MBS role is used only to provide mailbox databases and public folder databases. In Microsoft Exchange Server 2013, MBS also provides client access protocols, Hub Transport services, mailbox databases, and unified Messaging components. This means that the three components (Mbs,hts,um) in Exchange2010 are now integrated into one component.

The Client Access server role for Exchange Server2013 has changed. Now the client Access server basically does a proxy server to handle all the client connections, acknowledging all the client requests and routing them to the correct active mailbox database. It provides authentication, redirection, and proxy services that support the following client access protocols: HTTP,POP,IMAP,SMTP. Therefore, the fact that the client accesses the server does not itself store any user data, nor does it do any message queues. The Client Access server role provides security features, such as the execution of SSL in communication with customers. In some cases, the Exchange server is deployed in the

Multiple sites within an organization so that requests can be redirected to a more appropriate mailbox server.

Note: The role of the Edge Transport Server (ETS) is not available in Exchange2013, but you can still use the ETS role in Exchange2010.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/Mail/

Cas:

The Client Access server for Exchange Server2013 provides the following features:

A stateless server. In Exchange Server 2007 and 2010, the protocol requirements on most client access servers are based on sessions. This means that all requests from an Outlook Web app client must be handled by a specific client Access server in the Client Access server array. In Exchange Server2013, this is no longer the case and is now a stateless client Access server. All processing now occurs on the mailbox server, so the client Access server on the client Access server in an array receives client requests from each individual. Because of this, you can use 4-tier load balancing instead of the more expensive 7-tier load

Balance. This enables hardware load balancing devices to support more concurrent connections.

Connection pool. In previous versions of Exchange, client Access servers managed client authentication and sent data to the mailbox server role. The connection between the established Client Access server and the mailbox server is a member of the Exchange Servers group by using a privileged account. This allows client access to the server to connect to the mailbox server in a valid pool. With this technology, client access arrays handle millions of client connections from the Internet or internal networks, but use fewer proxy requests than previous versions of the Exchange Mailbox server.

Mbs:

In Exchange Server2013, the Mailbox server role provides more functionality than previous versions of Exchange Server. This includes the Integrated Hub Transport Service (formerly known as the Hub Transport server role) and the Unified Messaging Service (formerly known as the Unified Messaging server role). Mailbox and public folder data storage is still the core function of MBS.

The mailbox server role interacts with the client Access server and with the AD DS domain controller and the global catalog. The mailbox server role no longer communicates directly with the client, but is possible in previous versions of Exchange Server.

Exchange Server2013 communication between client and server

From the client's point of view, the most important thing is that RPC no longer supports as a direct client Access protocol. In previous versions of Exchange, Outlook clients were connected to an Exchange server from an internal network using RPC (or MAPI). In Exchange Server2013, all clients are established by using RPC over HTTPS connections. This means that all customers are connected by using the Outlook Anywhere service. This eliminates the need for client access servers running on RPC services. Also, you will be less than an FQDN admin, because all clients will use the new connection point, by the user's mailbox guid+@ UPN suffix. Only Outlook 2007 and updated clients support connecting to Exchange Server2013.