SharePoint 2016 integrated deployment Office Web APP Server (iii)

Now that the Office Web App server is installed, let's configure

First we want to deploy the office Web APP server farm, which is roughly divided into three concepts and types, and the deployment steps are slightly different.

Microsoft's official explanations and scenarios are described below:

1. An Office Web Apps server farm with a single server that uses HTTP

If you only use Office Web Apps server deployment for testing or internal use, and you do not have to provide Office Web Apps server functionality to Lync Server 2013, this program is for you. You will install an Office Web Apps server farm that uses HTTP and contains a single server. You do not need a certificate or load balancer, but you need a dedicated physical server or virtual machine instance that does not run any other server applications. You can use this Office Web Apps Server Farm to provide Office Web Apps functionality to SharePoint 2013 and Exchange Server 2013.

650) this.width=650; "Title=" deploys the three main steps of the Office Web Apps server farm that contains a single server. The "alt=" deployment has three main steps for the Office Web Apps server farm that contains one server. "src=" Https://i-technet.sec.s-msft.com/dynimg/IC699282.gif "/>

2. An Office Web Apps server farm that uses HTTPS and contains a single server

For most production environments, we strongly recommend that you use HTTPS for their security features. Similarly, if you want to provide Office Web Apps Server functionality to Lync Server 2013, you need HTTPS so that users can view the PowerPoint broadcast in the browser. Here you will learn how to install an Office Web Apps server farm that uses HTTPS and contains a single server. You need to install the certificate on the server as described in using HTTPS to protect Office Web Apps Server Preview communications.

This Office Web Apps Server Farm provides Office Web apps functionality to SharePoint 2013, Lync Server 2013, and Exchange server 2013.

650) this.width=650; "Title=" deploys the three main steps of the Office Web Apps server farm that contains a single server. The "alt=" deployment has three main steps for the Office Web Apps server farm that contains one server. "src=" Https://i-technet.sec.s-msft.com/dynimg/IC699282.gif "/>

3. Load balancing with multiple servers using HTTPS Office Web Apps server farm

You should use this type of topology if you expect your Office Web Apps Server Farm to be large and you want it to be available over the Internet and in the internal network. This section describes how to install an Office Web Apps server farm that uses a load balancer and HTTPS that contains multiple servers. If you are interested, please read more about this topology.

Before you begin, make sure that you have configured the load balancer as described in load balancer requirements for Office Web Apps Server. You also need to install the certificate on the load balancer as described in securing Office Web Apps Server Communications using HTTPS. This Office Web Apps server farm provides Office Web apps functionality for SharePoint 2013, Lync Server 2013, and Exchange server 2013.

650) this.width=650; "Title=" deploys the four main steps of the Office Web Apps server farm that contains multiple servers. The "alt=" deployment has four main steps for the Office Web Apps server farm that contains multiple servers. "src=" Https://i-technet.sec.s-msft.com/dynimg/IC699283.gif "/>

Today, our test environment chooses the second, using HTTPS deployment method, because we this will involve public network release (will involve public network certificate), consider the security encryption, so choose the second kind.

1. First create the OWA server farm

Open PowerShell with Administrator role, enter a command

New-officewebappsfarm–internalurl "https://owa.contoso.com" –externalurl "https://owa.contoso.com"- Certificatename "Public Certificate" –editingenabled

Note: If everyone and I like to do the public network release, and the certificate is a wildcard certificate (*.contoso.com), then here I strongly recommend that you better unify the internal and external URL name, so that the client's authentication and query.

650) this.width=650; "Width=" 654 "height=" 497 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M01/8E/6F/wKioL1jAoUvTGfYEAAPR9nmLfgc450.png" border= "0"/>

After creation, the Get-officewebappfarm command can be used to query the settings of this farm.

650) this.width=650; "Width=" 541 "height=" 497 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; " alt= "image" Src= "http://s3.51cto.com/wyfs02/M02/8E/6F/wKioL1jAoU3x4HWiAAMjkac10TA797.png" border= "0"/>

2. Verify that the OWA farm is successful

It is not enough to see the PowerShell above, we need to access the Office Web Apps Server Discovery URL by using a Web browser. The Discovery URL is the internalurl parameter that you specified when you configured the Office Web Apps server farm, followed by /hosting/discovery, for example:

Https://server.contoso.com/hosting/discovery

I'm going to use a browser to access Https://owa.contoso.com/hosting/discovery.

650) this.width=650; "Width=" 1098 "height=" 424 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; " alt= "image" Src= "http://s3.51cto.com/wyfs02/M02/8E/71/wKiom1jAoVCzWh8yAASvXNzIgfE169.png" border= "0"/>

If Office Web apps Server is running as expected, you should see the Web application Open Platform Interface (WOPI) protocol Discovery XML file in your Web browser. As described above, the OWA farm is configured successfully.

3. Configure the host, and SharePoint to do a compatible configuration

With the above two steps, the farm now has the ability to provide Office Web Apps for hosts over HTTPS.

Now bind SharePoint to the OWA farm by using the following command.

This action operates on a SHAREPOINT server!!!! Open the SharePoint Management Shell in Administrator role

650) this.width=650; "Width=" 681 "height=" "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; " alt= "image" Src= "http://s3.51cto.com/wyfs02/M00/8E/71/wKiom1jAoVHjVOHLAABh_3Jqf9A714.png" border= "0"/>

Note that the official order given by Microsoft is this new-spwopibinding-servername <wacservername>–allowhttp

I have no back here behind the –allowhttp, mentioned before, I this OWA farm is to use the public network certificate to do encryption released, so I did not add this parameter.

Now let's take a look at the Wopi zone for SharePoint bindings

Get-spwopizone with command

650) this.width=650; "Width=" 488 "height=" 117 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; " alt= "image" Src= "http://s3.51cto.com/wyfs02/M01/8E/71/wKiom1jAoVHzC906AABZmG4ZMAk080.png" border= "0"/>

My direct feedback here is that External-https achieved my goal, if it was added to the parameters –allowhttp, here should be feedback is internal-http

To modify this Wopi area, you can use the following command

Set-spwopizone-zone "Internal-http" or Set-spwopizone-zone "Internal-https" or Set-spwopizone-zone "External-https"

I am here because of the use of the external HTTPS protocol, it is possible to directly carry out the final effect test.

------------------------------------------------------------------------------Split Line---------------------------------------- ---------------------------------------------------------------

Note: If you are using internal-http, then there is one more step

To use SharePoint 2013 with Office Web Apps in a test environment with HTTP, you need to set Allowoauthoverhttp to True. Otherwise, Office Web Apps will not work. You can check the current status by running the following example:

(Get-spsecuritytokenserviceconfig). Allowoauthoverhttp

If this command returns False, run the following command to set it to True.

$config = (get-spsecuritytokenserviceconfig)

$config. Allowoauthoverhttp = $true $config. Update () Run the following command again to verify that the Allowoauthoverhttp setting is now set to True.

(Get-spsecuritytokenserviceconfig). Allowoauthoverhttp------------------------------------------------------------------------------Split Line---------------------- ---------------------------------------------------------------------------------

Next .... Next ... then we'll test it directly.

We try to open a PPT file

650) this.width=650; "Width=" 622 "height=" 497 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; " alt= "image" Src= "http://s3.51cto.com/wyfs02/M01/8E/71/wKiom1jAoVSR6hDfAAOEf6dR-rI763.png" border= "0"/>

Have effect ...

650) this.width=650; "Width=" 559 "height=" 306 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; " alt= "image" Src= "http://s3.51cto.com/wyfs02/M01/8E/6F/wKioL1jAoVXCZJfmAABHXDry3g4042.png" border= "0"/>

Success!

650) this.width=650; "Width=" 765 "height=" 497 "title=" image "style=" border-right-width:0px;background-image:none; border-bottom-width:0px;padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8E/71/wKiom1jAoVbTN-BtAACkCTadNX4166.png" border= "0"/>

By the end, let's say a command, if you want to cancel the bindings for SharePoint and OWA Farms, on the SharePoint Management Shell, use the following command.

Remove-spwopibinding-all: $true

This article is from the "June Ma Run Space" blog, be sure to keep this source http://horse87.blog.51cto.com/2633686/1904607

SharePoint 2016 integrated deployment Office Web APP Server (iii)