Overview

This post will focus on a deployment of Office Online Server (OOS, formerly known as “Office Web Apps Server”) single server farm that will be used for a SharePoint server 2019 farm. In this post, a Virtual Machine (VM) with Windows Server 2019 Standard (with Desktop Experience) will be used as OOS single server farm.

Planning for a deployment of Office Online Server farm

The deployment of the OOS single server farm is straight forward. However, the following are things you should review carefully before deploying OOS.

Supported operating systems:

You can run Office Online Server on the following operating systems:

  • The 64-bit edition of Windows Server 2012 R2
  • The 64-bit edition of Windows Server 2016 (Office Online Server April 2017 or later required).
  • Note: we will use Windows Server 2019 Standard in this post.

Domain servers

All servers in the Office Online Server farm must be part of a domain. In this post we use only one server

Don’t:

  • Don’t install any other server applications on the server that’s running Office Online Server. This includes Exchange Server, SharePoint Server, Skype for Business Server, and SQL Server.
  • Don’t install any services or roles that depend on the Web Server (IIS) role on port 80, 443, or 809.
  • Don’t install any version of Office. If it’s already installed, you’ll need to uninstall it before you install Office Online Server.
  • Don’t install Office Online Server on a domain controller. It won’t run on a server with Active Directory Domain Services (AD DS).

Firewall requirements

Make sure the following ports aren’t blocked by firewalls on either the server that runs Office Online Server or the load balancer:

  • Port 443 for HTTPS traffic
  • Port 80 for HTTP traffic
  • Port 809 for private traffic between the servers that run Office Online Server (if you’re setting up a multi-server farm)

DNS requirements

In environments that use HTTPS and load balancing, you have to update DNS so that the fully qualified domain name (FQDN) of the certificate resolves to either the IP address of the server that runs Office Online Server or to the IP address assigned to the load balancer for the Office Online Server farm.

Prepare servers for Office Online Server farm

Install prerequisite software for Office Online Server on Windows Server 2019

If you build your server from scratch and try to install OOS without additional configuration, you will see Setup Errors dialog box shown below.

As you see the error messages, we don’t need to install any additional software (such as .NET Framework 4.5.2, Visual C++ Redistributable Packages for Visual Studio 2013, Visual C++ Redistributable for Visual Studio 2015, Microsoft.IdentityModel.Extention.dll) before installing OOS on Windows Server 2019 like we do with Server 2016 and lower version (see https://docs.microsoft.com/en-us/officeonlineserver/deploy-office-online-server). The only thing we need is adding Web Server (IIS) role and ASP.NET 4.7 feature by using Add Roles and Features GUI from Server Manager.

On the Add Roles and Features Wizard dialog box, keep the default settings and click Next to skip the first three screen (Before You Begin, Installation Type and Server Selection)

On the Server Roles screen, click on Web Server (IIS) then Add Features button to confirm.

On the Features screen, expand .NET Framework 4.7 Features and select ASP.NET 4.7 component. Click Next

Click Next and skip Web Server Role (IIS) screen.

On the Role Services screen, make sure you select the components that follow Window Authentication, .NET Extensibilities 4.7, ASP.NET 4.7, ISAPI Extensions, ISAPI Filters, and Server Side Includes. Click Next to continue and install the Roles and Featues.

The installation completed and we can move on the installation of Office Online Server.

Install Office Online Server

Download Office Online Server from the Volume Licensing Service Center (VLSC). Office Online Server is a component of Office, so it is available under each of the product pages including Office Standard 2016, Office Professional Plus 2016, and Office 2015 for Mac Standard.

Double-click and run Setup.exe. On the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and click Continue.

On the Choose a file location page, keep the default option and select Install Now. If the folder you specified doesn’t exist, Setup creates it for you.

When Setup finishes installing Office Online Server, choose Close.

Note: If you plan to use Kerberos Constrained Delegation with Excel Online, there are two additional steps you need to perform:

  1. On the OOS server, open Windows Services, set the Claims to Windows Token Service to start automatically on this server.
  2. Add the OOS server (if it is OOS multi-server farm, be sure to add all of them) to the Active Directory Domain Services delegation list.

Install language packs

If you plan to let your users view web-based Office files in multiple languages, you will need to install the language packs. You can download and install them from Microsoft Download Center.

Deploy Office Online Server

Deploy a single-server Office Online Server farm that

Open PowerShell ISE with Run as administrator and run the New-OfficeWebAppsFarm cmdlet to create a new Office Online Server farm that consists of a single server.

If you are deploying a farm that uses HTTP, run the following cmdlet.

New-OfficeWebAppsFarm
-InternalURL
“http://OOS”
-AllowHttp
-EditingEnabled

For deployment of a farm that uses HTTPS, use the following cmdlet:

New-OfficeWebAppsFarm -InternalUrl “https://OOS.spmonkey.local” -ExternalUrl “https://OOS.spmonkey.com” -CertificateName “SPMonkey OOS Certificate” -EditingEnabled

Click Yes to confirm the operation.


Next, we run the following cmdlet. It is to make sure that we can support allowing the end user to open the document in the browser.

Set-OfficeWebAppsFarm
-OpenFromUrlEnabled

Verify that the Office Online Server farm was created successfully

Now it is time to verify the deployment has been completed successfully by opening the IE browser. Enter the discovery URL that shown below (in this case, the server name is Sp17ADFS-OOS).

OOS Discovery URL: http://sp17adfs-oos/hosting/discovery

If the deployment completed properly, you should see a XML file in your web browser that shown as below.

Integrate SharePoint with Office Online Server

Office Online is installed. We can now start the process of setting up SharePoint. From an SharePoint App Server, open an elevated SharePoint 2019 Management Shell (Right-click SharePoint 2016 Management Shell, and then click Run as Administrator).

Run the following command to create the binding between SharePoint 2019 and Office Web Apps Server. In this case, we need to specify the -AllowHTTP parameter to allow SharePoint Server 2019 to receive discovery information from the Office Online Server farm by using HTTP.

New-SPWOPIBinding -ServerName SP17ADFS-OOS -AllowHTTP

After running the command above, you should see the WopiZone is internal-http (if you are deploying OOS farm that uses HTTP). Or you can also verify it by running the Get-SPWOPIZone cmdlet. If it doesn’t display as internal-http, you can change it by running the cmdlet that follow.

Set-SPWOPIZone -zone “internal-http”

LEAVE A REPLY

Please enter your comment!
Please enter your name here