Initial knowledge of Exchange 2016

Microsoft Exchange Server 2016 introduces a range of new technologies, features, and services in Exchange Server. Its goal is to enable people and organizations to shift their focus from communication to collaboration. There are many changes compared to the previous Exchange server. The following is a brief description of the features we often use. For more information, refer to:https://technet.microsoft.com/zh-cn/library/jj150540 (v=exchg.160). aspx.

1. Server architecture role Changes Exchange 2016 currently has only two server roles: the Edge server and the mailbox server role.

2, weakened RPC over HTTP function, that is, we are familiar with the outlookanywhere. Personally feel that the current Exchange 2016 support RPC over HTTP is primarily asked for compatibility with Outlook 2010/2007. If it is Outlook 2013/2016, you can use MAPI over Http directly.

3. Link connector, unable to link the Send connector to the Receive connector. That is, the Linkedreceiveconnector parameter is removed in the command New-sendconnector and Set-sendconnector. Linkedreceiveconnector is used to force messages received by a receive connector to be sent out through a send connector.

4, mail flow changes. (This is important for future troubleshooting, understanding mail flow for Exchange 2016) (refer to:https://technet.microsoft.com/zh-cn/library/aa996349 (v=exchg.160) . aspx . Exchange 2016 has changed greatly in mail flow compared to previous versions of Exchange, and the SMTP service has been layered, mainly in the following sections:

1), Mailbox server Front End Transport service (Front end Transport service on Mailbox servers) the service will external inbound/outbound mail (inbound and outbound) proxy to Exchange 2016 organizations. The layer SMTP service does not check for mail content. After receiving the message, Proxy to Mailbox Transport service on Mailbox servers.

2), back-end transfer service (Transport service on Mailbox servers) the server can be understood as the hub (Hub Transport role) in Exchange 2010, except that the server is not directly and Mailbox Database for interaction. And the service will check the contents of the received messages. Primarily used to receive proxy requests for front End Transport service and service on Edge Transport servers.

3), Mailbox Transport service Mailbox Transport service on Mailbox servers) The server consists of two parts:

A, the Mailbox Transport submission Service (Mailbox Transport submission Service) The service receives a message and connects directly to the local mailbox database and uses RPC (Exchange Remote Procedure call (RPC) ) to retrieve the message (retrieves whether the recipient is on the local database). Responsible for submitting the message to the local back-end transport service (Transport service on the local Mailbox server) or another mailbox server.

B, the Mailbox Transport delivery service (Mailbox Transport Delivery Service) is responsible for delivering the message to the Transport service on the local Mailbox server.

C, The Edge Transport Service (Transport service on edge Transport servers) is used for message routing between the Edge server and the Exchange organization.

The specific mail flow toward can be viewed, Microsoft Public network gives the flow of mail. Note that Exchange 2016 users send messages to the public network, and messages will be sent from mailbox server if the front end agent is not checked on the Send connector.

650) this.width=650; "Src=" http://img.blog.csdn.net/20160425163910581?watermark/2/text/ Ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity/center "/>

Initial knowledge of Exchange 2016