Shulou(Shulou.com)06/02 Report--

Brief introduction of Exchange Server 2016

MicrosoftExchange Server 2016 introduces a new set of technologies, features, and services for Exchange Server, a messaging platform that provides e-mail, scheduling, and tools for customizing collaboration and messaging service applications. Its goal is to support people and organizations to shift their focus from communication to collaboration. At the same time, Exchange 2016 can also help reduce the total cost of ownership (whether deploying local Exchange 2016 or provisioning mailboxes in the cloud)

In the Exchange 2016 architecture, the server roles are as follows:

Mailbox server role:

Mailbox servers contain transport services for routing messages, mailbox servers contain mailbox databases that process, present, and store data, and mailbox servers contain client access services that accept client connections to all protocols. These front-end services are responsible for routing or proxying connections to the appropriate back-end services on the Mailbox server. Clients do not connect directly to back-end services, Mailbox servers include Unified messaging (UM) services that provide voicemail and other telephony services to mailboxes, and use Exchange Management Center (EAC) and the Exchange Management Shell to manage Mailbox servers.

Edge Transport server role:

The Edge Transport server handles all external mail flows of the Exchange organization; the Edge Transport server is usually installed in the perimeter network and subscribes to the internal Exchange organization. When the Exchange organization receives and sends messages, the EdgeSync synchronization process provides recipient information and other configuration information to the Edge Transport server, and when the Exchange organization receives and sends messages, the Edge Transport server provides anti-spam and mail flow rules. You can use the Exchange Management Shell to manage the Edge Transport server

Exchange Server 2016 uses a building block architecture to provide email services for deployment in organizations of all sizes, from small organizations to the largest multinational enterprises. This architecture is shown in the following figure.

High availability architecture

Mailbox high availability

Database availability groups (DAG) are the basic elements of the high availability site recovery framework built into Exchange 2016. DAG is a set of mailbox servers that not only hosts a set of databases, but also provides database-level automatic recovery from database, network, and server failures. Compared to Exchange 2013, DAG in Exchange 2016 has been improved.

Transport high availability

The transport service creates redundant copies of all messages in transit. This feature is called shadow redundancy.

The transport service creates redundant copies of all delivered messages. This feature is called a secure network.

In Exchange 2016, DAG represents the transport high availability boundary. You can deploy DAG across multiple Active Directory sites to achieve site recovery.

In Exchange 2016, transport high availability requires more than ensuring message redundancy as much as possible, because redundancy does not depend on the features supported by the outgoing mail server. Therefore, it can be said that Exchange 2016 attempts to retain multiple copies of messages during and after message delivery to ensure message redundancy.

Comparison of functional Features between Exchange 2016 and Exchange 2013

Compared with Exchange 2013, new features of Exchange 2016

The Mailbox server in Exchange 2016 includes all server components in the Exchange 2013 mailbox and client access server role:

The client access service provides authentication, limited redirection, and proxy services. The client access service does not perform any data rendering and does not provide any common client access protocols: HTTP, POP, and IMAP and SMTP.

Mailbox services include all traditional server components in the Exchange 2013 Mailbox server role: back-end client access protocols, transport services, mailbox databases, and unified messaging. The Mailbox server handles all activities of the active mailboxes on this server.

The Edge Transport role is typically deployed in the perimeter network, outside the internal Active Directory forest, and is designed to minimize the exposure to Exchange deployment. By handling all Internet-oriented mail flows, it also adds other mail protection layers against viruses and spam, and can apply mail flow rules (also known as transport rules) to control mail flow.

Outlook Web App, now known as Outlook on Web, continues to allow users to access their Exchange mailboxes from almost all Web browsers. The previous Outlook Web App user interface has been updated and optimized for tablets and smartphones, as well as desktops and laptops. The new Exchange 2016 features include:

Mobile-specific platform experience; advanced Android experience; email improvements: includes new single-line views in your inbox with optimized reading panes, archives, emoticons and new mailbox undo actions such as deleting or moving emails; contact links: users can add contacts through their LinkedIn account.

Calendar: the appearance has been updated and new features have been added, including email reminders of calendar events, the ability to propose new times in meeting invitations, enhanced search, and birthday calendars.

Performance improvement: involves multiple parts of Outlook on Web, including creating calendar events, composing mail, loading messages in the reading pane, popping up content, searching, launching, and switching folders.

The Outlook actions pane on the new Web allows you to quickly click on the most commonly used actions, such as New, reply all, and Delete. Several new operations have been added, including archiving, cleanup, and undo.

MAPI over HTTP

MAPI over HTTP is now the default protocol that Outlook uses to communicate with Exchange. MAPI over HTTP moves the transport layer to the industry-standard HTTP model, improving the reliability and stability of Outlook and Exchange connections.

Document collaboration

Instead of attaching files to messages, Exchange 2016 and SharePoint Server 2016 enable Outlook users on Web to link to and share files stored in OneDrive for Business on the local SharePoint server.

Office 365mix

The wizard can be updated quickly to support changes in the Office 365 service.

The wizard can be updated to address problems detected by customers when they try to configure a mixed deployment.

Everyone running Exchange 2013 or Exchange 2016 uses the same wizard when configuring a mixed deployment.

Mail policies and complianc

Data loss protection

On-site archiving, retention and electronic data display

Improved performance and scalability

Exchange 2016 reduces functionality compared to Exchange 2013

The client access server role has been replaced by the client access service that runs on the Mailbox server role. The Mailbox server role now performs all the functions contained in the previous client access server role.

The MAPI/CDO library has been replaced with Exchange Web services (EWS), Exchange ActiveSync (EAS), and declarative state transition (REST) * API. If your application uses the MAPI/CDO library, you need to move to EWS, EAS, or REST API to communicate with Exchange 2016

Here are the features that have been weakened in Exchange 2016

Third-party replication of API

RPC over HTTP

Database availability group support for failover cluster management access points

Exchange 2016 prerequisites

Active Directory is ready to install the following software in the order shown:

.NET Framework 4.6.2

After you install the software listed above, complete the following steps to install the remote tool management package. After installing the remote tools Management Pack, you will be able to use your computer to prepare Active Directory.

Open Windows PowerShell.

Install the remote tool management package. Install-WindowsFeature RSAT-ADDS

Windows Server 2012 R2 prerequisites, prerequisites for different Exchange roles

1. Prerequisites for mailbox and client access roles

Open Windows PowerShell.

Run the following command to install the necessary Windows components.

Install-WindowsFeature AS-HTTP-Activation, Server-Media-Foundation, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS

Install .NET Framework 4.6.2

Install Microsoft Unified Communications Managed API 4.0Core Runtime (64-bit)

2. Prerequisites for Edge Transport server role

Open Windows PowerShell.

Run the following command to install the necessary Windows components.

Install-WindowsFeature ADLDS

.NET Framework 4.6.2

Prepare Active Directory and domain

Before installing Microsoft Exchange Server 2016, you need to prepare the Active Directory forest and its subdomains. Exchange needs to prepare the Active Directory so that it can store information about the user's mailbox and the configuration of the Exchange server in the organization.

1. Extend the Active Directory architecture

The first step in getting an organization ready for Exchange 2016 is to extend the Active Directory architecture. Exchange stores a lot of information in Active Directory, but before storing it, you need to add and update classes, properties, and other items.

Make sure your computer is ready to run Exchange 2016 setup.

Open a Windows command prompt window and go to the location where you downloaded the Exchange installation file.

Run the following command to extend the schema.

Setup.exe / PrepareSchema / IAcceptExchangeServerLicenseTerms

2. Prepare Active Directory

Now that the Active Directory schema has been extended, you can prepare other parts of Active Directory for Exchange 2016. During this setup, Exchange creates containers, objects, and other items in the Active Directory used to store information. The collection of all Exchange containers, objects, properties, and so on is called the Exchange organization. When you run the following command to prepare Active Directory for Exchange, you need to specify the Exchange organization. This name is used internally by Exchange. When you are ready, do the following to prepare the Active Directory for Exchange. If the organization name you want to use contains spaces, put the name in quotation marks (").

Open a Windows command prompt window and go to the location where you downloaded the Exchange installation file.

Run the following command:

Setup.exe / PrepareAD / OrganizationName: "" / IAcceptExchangeServerLicenseTerms

3. Prepare Active Directory and domain

To prepare all Active Directory domains, you can use the PrepareAllDomains parameter when running the installer. Setup will prepare each Exchange domain in the Active Directory forest for you. When you are ready, do the following to prepare all domains in the Active Directory forest as Exchange.

Open a Windows command prompt window and go to the location where you downloaded the Exchange installation file.

Run the following command:

Setup.exe / PrepareAllDomains / IAcceptExchangeServerLicenseTerms

Prepare the domain specified in Active Directory

If you want to choose which Active Directory domains to prepare, you can use the PrepareDomain parameter when running the installer. When using the PrepareDomain parameter, you need to include the fully qualified domain name (FQDN) of the domain you want to prepare. Do the following to prepare the domains in the Active Directory forest as Exchange.

Open a Windows command prompt window and go to the location where you downloaded the Exchange installation file.

Run the following command. The FQDN that contains the domain you want to prepare. If you want the domain in which you are going to run the command, you do not need to include FQDN.

Setup.exe / PrepareDomain: / IAcceptExchangeServerLicenseTerms

Environmental deployment

In this Exchange 2016 deployment scenario, the list of planned servers in the experimental environment is as follows:

Network topology diagram:

The deployment ideas of this scheme are as follows:

Configure AD domain environment, DNS domain name system, certificate issuing function, etc.

Prerequisites for exch01 and exch02 servers to install Exchange 2016 and prepare AD and domain

Use the installation wizard or unattended mode to install the Exchange 2016 Mailbox server role for exch01 and exch02 servers

Configure mail flow and client access and certificate application installation

Configure DNS load balancer, DAG database availability group

Configure Exchange 2016 Edge Transport Server

Verify Exchange 2016 installation

Starting from this chapter, we will introduce the installation and deployment process of Exchange 2016 in detail, hoping to further enhance the awareness of Exchange 2016 through blog content and be proficient in the comprehensive deployment method of Exchange 2016. For the imperfections of this series of articles, please correct them in the comments section. Thank you very much.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.