Exchange 2016 version has only two roles
Mailbox role
Edge Transport Role
In Exchange 2016, a feature that previews documents in the OWA interface, including Excel, Word, PPT, PDF, and other common documents, is to use Office Web apps to support the preview feature. In the Exchange 2016 version of the OWA server, you need to use the next-generation OWA server, named Office Web Apps VNext, so the additional roles are:
3. Office Web Apps vnext role
Annotations:
office Web Apps is a very important role,
office support for Web Apps
Exchange 2016 adds an optional prerequisite for installing the next version of Office Web Apps ("Office Web Apps VNext") server in one or more servers in your organization. With the Office Web Apps vNext Server, users can view supported file attachments in Outlook on the web, without having to download them first, or install related programs locally. If the Office Web apps vNext Server is not installed, Outlook users need to download the attachments to their local computer, and then open them in the local application.
The following describes the installation of this role, referred to as Owav server.
First, or
1 System Requirements:
The Office Web Apps VNext Server needs to have the following installed:
You cannot install the Office Web Apps vNext Server on an Exchange server, a SharePoint server, an Active Directory domain controller, or any other computer that has an existing application installed.
2 Prerequisites:
Run the following command in PowerShell:
Install-windowsfeature Web-server, Web-mgmt-tools, Web-mgmt-console, Web-webserver, Web-Common-Http, Web-Default-Doc , Web-static-content, Web-performance, Web-stat-compression, Web-dyn-compression, web-security, Web-Filtering, Web-windows-auth, Web-app-dev, Web-net-ext45, Web-asp-net45, Web-isapi-ext, Web-isapi-filter, Web-Includes, Inkandhandwritingservices
Restarting the server
3 Installing Owav
Download the Office Web Apps vNext server. (software in the connection)
Go to the download Office Web Apps vNext server location, and then run Setup.exe.
Follow the Office Web Apps vNext Server Setup Wizard, select the installation location, and then click Install Now.
If you are installing the Office Web Apps vNext Server Language Pack, see Office Web Apps Server Language Pack. (If you want to owav support for multiple languages, you will need to download the corresponding language pack)
Gets and imports an SSL certificate that contains the fully qualified domain name (FQDN) of the Office Web Apps vNext server. If your organization has a split DNS feature configured, you only need to configure one FQDN on the certificate. For example, wac.contoso.com. If you have different internal and external FQDNs, you need to configure two FQDNs on the certificate. For example, wac.internal.contoso.com and wac.contoso.com.
(note: such as the official version, set up a demo to improve the application steps, we can refer to the previous version of the application: http://xiaoyuanzheng.blog.51cto.com/7269200/1640406)
Configure the DNS records to point the FQDN on the certificate to the Office Web Apps vNext server. If you have different DNS servers for both internal and external users, you need to configure the appropriate FQDN on each server.
Open Windows PowerShell and run the following command. When you run the command, use your own to replace the sample FQDN and the certificate friendly name.
-
same internal and external FQDN https://wac.contoso.com "- Externalurl "https://wac.contoso.com "-certificatename "office Web Apps vNext Certificate "
-
different internal and external FQDNs https://wac.internal.contoso.com "-externalurl" office Web Apps vNext Certificate "
set-mailboxserver -wacdiscoveryendpoint
Restart-webapppool Msexchangeowaapppool
Where MBX is the computer name of the mailbox server (it is recommended to use the FQDN), the rear link changes the name of the server name to the Owav server.
Exchange 2016 worker Roles