Before starting the installation, let’s first briefly discuss the roles and roles of
Exchange Server 2007 and 2016.
As it is known, there are 5 roles in 2007 and 2010 Exchange Server.
Mailbox Server Role = A role required to manage Mailboxes and public folders. Because this role will work in communication with Active Directory, the server on which you will install this role must be an
Active Directory Domain member.
Hub Transport Role = A role that is required to route mail. It categorizes the mail and allows it to pass through the organization. The server on which you will install this role must be an
Active Directory Domain member.
Client Access Server Role = This role enables all mail protocols to be used on the Exchange Server. Exchange Active Sync clients connect to Outlook Anywhere (RPC over HTTP), POP, IMAP, Outlook Web App, MAPI protocols. The server on which you will install this role must be an
Active Directory Domain member.
The roles above are usually what each organization should have, and the roles below are optional, with the Hub Trasport role being similar to the
Edge Transport role. For example, this role can also create filters for users and external domains.
Edge Transport Server Role = A role used for security between
SMTP and the Internet. It also does not need to be a member of the Active Directory server.
Unified Messaging Server Role = A role that enables voice and faxes messages to be used for your organization.
Therefore, the number of roles in
Exchange Server 2013 has decreased from 5 to 2. These are
Mailbox Server Role and
Client Access Roles. In addition, the
EMC is now replaced by the
Exchange Administration Console (EAC). In this way, management over the web was achieved.
In Exchange Server 2016, it can be deployed as 2 roles. Mailbox Server and Edge Server. They removed the role of Cas as a service to the Mailbox role. Developed by adding faster and more effective innovations to the user.
I recommend you to review this link https://technet.microsoft.com/en-us/library/mt170645(v=exchg.160).aspx for system requirements and other information for Exchange Server 2016.
Directory Service support
User application support
Now we can proceed with the installation. The simple scheme of the structure we will create is as follows.
Domain Controller and
Exchange Server is ready to install the machine and as shown in the screenshot below I bought the machine domain. I also recommend that you create a user on the AD DC for both Exchange Server setup and administration, and then grant privileges to that user. Since I am in a test environment, I will do my operations with Domain Admin.
In addition, the region and language settings of the server to be installed in
English & United States to avoid future problems I suggest you do.
Then run the following command on the server where Exchange will be installed after opening
PowerShell in Admin mode.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, 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,
We started the installation by pasting the commands and the installation is done.
And the installation is finished, then restart the server.
Then install the following requirements. Usually
.Net 4.5 is installed on the server.
- .NET Framework 4.5.2 http://www.microsoft.com/en-us/download/details.aspx?id=42642
- Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit http://www.microsoft.com/en-us/download/details.aspx?id=34992
Next, several adjustments must be made to make Active Directory compatible for Exchange Server 2016. We can do this in two ways. By using several commands manually or by using the Exchange Server setup wizard.
By manually running CMD in admin mode, you can go to the Exchange Setup directory and run the following commands there. I extracted the files under
C: \ Exchange2016.
Active Directory Schema Expansion
C:\Exchange2016>setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Preparing Active Directory
C: \ Exchange 2016> setup.exe / PrepareAD / OrganizationName: “organization name” / IacceptExchangeServerLicenseTerms
Preparing All Domains in a Domain
C:\Exchange2016>setup.exe /PrepareAllDomains /IacceptExchangeServerLicenseTerms
After doing this, you can use the command below to check the schema version, or you can check it from ADSI EDIT. If the update was successful, it will return the version number to you, otherwise, it will be empty.
You can also access Schema Versions for Exchange Server 2016 from this link.
“Exchange Schema Version = ” + ([ADSI](“LDAP://CN=ms-Exch-Schema-Version-Pt,” + ([ADSI]”LDAP://RootDSE”).schemaNamingContext)).rangeUpper
Second, we can leave this job in the setup wizard, but you must install Remote Server Administration Tools beforehand. You can do this with the GUI interface, or you can do the following after running PowerShell in admin mode.
By this time, we have made all preliminary preparations for the installation. Now go directly to the setup directory and run the setup file.
Next to check for updates.
Files are copied and made available for installation.
Continue with Next.
Accept the license agreement and continue with
You can select the recommended settings or the other, then continue with
The installation will appear as follows. As soon as you select the Mailbox role, the Management tools will be selected automatically. The edge transport role will be passive. The reason is that it cannot be run on the same server as the mailbox. You can also enable the option to have the necessary downloads for
Exchange Server checked and installed if necessary.
The final figure will be as follows. Then continue with
After determining the location to be installed, continue with
The organization would then ask you to specify the name and finish the setup after expanding the schema but did not ask me for these steps because I did the schema expansion manually.
If you want to confirm the malware scan, you can continue with
Then click Install to start the Exchange installation. And wait until it’s set up, the process will take a little longer.
Installation in progress.
When the installation is finished, confirm for the opening of the EAC and click Finish.
The Exchange Admin Center web interface opens as
https: // servername / ecp.
Then, both the continuation of the article and the basic operations that need to be done can be found on the following link.