Step by step Office Online Server(OOS) Installation for SharePoint 2016

Step by step Office Online Server(OOS) Installation for SharePoint 2016

You can create, share and collaborate on Word, PowerPoint, Excel and OneNote files in your browser. Most notably, OOS with SharePoint lets multiple people work in a document at the same time and see everyone’s changes as they happen.Office Online Server 2016 needs to be installed on its own server, and cannot coexist with a SharePoint installation. It can still be used as a standalone installation.

The farm we are using here is a one SQL Server with the SharePoint 2016 Application Server MinRole installed on, a Web-Front end (MinRole), and a standalone Office Online Server (OOS) node.

We can download OOS from the Volume License Servicing Center at no cost. 

Pre-requisites:
Step Install these software packages on your Office Online Server(s).

.NET Framework 4.5.2
Visual C++ Redistributable Packages for Visual Studio 2013
Visual C++ Redistributable for Visual Studio 2015
Microsoft.IdentityModel.Extention.dll

Steps:
1.Enable web server role and features:
Open Powershell then rub the below script.

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, Windows-Identity-Foundation

2.Restart the server.

3.Download OOS from MSDN and click on setup file.

4. Keep the drive location to default C Drive.

5.Do the same setting for another server if you have.

6.If we don’t have certificate we need to configure it , in this case we have ‘OOSCert’. or Create Self signed certificate.

Import your Personal certificate:

7.Go to OOS server the run the following script.

Add the parameter -externalURL to define a different URL for accessing your Office Online Server farm. Shouldn’t be needed in most cases because you’re already using a FQDN with your internal URL. The parameter –CertificateName reflects the friendly name of your certificate.

Import-Module -Name OfficeWebApps 

# OWA Parameters

$InternalURL = "https://sp-oos.sharepoint.com"

$ExternalURL = "https://sp-oos.sharepoint.com"

$CertName = "OOSCert" 

$LogLocation = "E:\OfficeOnlineServerLogs\LogsOS" 

$maxMemoryCacheSizeInMB = 75  #Default 75

$CacheSizeInGB = 15  #Default 15

$CacheLocation = "E:\OfficeServer\DiskCache"

$RenderingLocalCacheLocation = "E:\OfficeServer\RenderingCache" 

# Create the farm

New-OfficeWebAppsFarm -InternalUrl $internalURL -ExternalUrl $ExternalURL -CertificateName $CertName -EditingEnabled -LogLocation $LogLocation -CacheLocation $CacheLocation -RenderingLocalCacheLocation $RenderingLocalCacheLocation -MaxMemoryCacheSizeInMB $maxMemoryCacheSizeInMB -CacheSizeInGB $CacheSizeInGB  

8. Click on "Yes" to continue this operation.

9. Verify at IIS websites and application pools.

10. Join Second Server to the farm if you have,Login to the server another server.

Run the following script.

New-OfficeWebAppsMachine -MachineToJoin server2name

11. Verify that the Office Web Apps Server farm was created successfully or not?

At this point, our job is done for the Office Online Server 2016 configuration. You can go ahead and test that the “Farm” was successfully created by trying to access https://<server name>/hosting/discovery using Internet Explorer (or edge if using Windows Server 2016 Preview). If everything worked, you should see the server’s XML WOPI output as shown in the figure below(image was copied from MSDN).

12.Go to SharePoint Farm server(Connecting to SharePoint) , run the following script in powershell.

Add-PSSnapin Microsoft.SharePoint.PowerShell

New-SPWOPIBinding -ServerName sp-oos.sharepoint.com

Get-SPWOPIZone

Set-SPWOPIZone -zone "internal-https"

#These lines adds supports for legacy excel services to be redirected to new OOS service

$Farm = Get-SPFarm

$Farm.Properties.Add("WopiLegacySoapSupport","https://sp-oos.sharepoint.com/x/_vti_bin/ExcelServiceInternal.asmx");

$Farm.Update(); 

If the command worked, you will see a lot of Office specific properties being output on screen.

13.We are now all set! , Now verify the OOS for office documents.

14. In case the office documents are not showing in the browser/preview then see the logs.

Log Location for Office Online Server is :  C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS