SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, SharePoint 2016: Tips & Tricks for Office Online Servers deployment – SharePoint

SharePoint 2016: Tips & Tricks for Office Online Servers deployment

In this article, I will list some tips, tricks & information for a successful deployment of Office Online Server 2016 for SharePoint server 2016.

  • Office Online Server 2016(OOS) is new version of Office Web Apps 2013
  • Configuration of Office Online Server only possible via PowerShell, No GUI like SharePoint
  • No SQL Server or Database requirement
  • OOS support Deployment supported on both Physical as well as Virtual machines
  • OOS should install on Dedicated server
  • Don’t
    • No other server application should install on it
    • No Office version should install on the Office Online Server
    • Don’t Install OOS on the Domain Controller
  • Multi Server Farm and Load-Balancer
    • Single OOS farm support multiple deployment i.e. a single farm can bind with SharePoint, Exchange and Skype for Business
    • OOS farm can be a single server or multiple server farms like SharePoint
    • You can add more servers into OOS farm anytime, it is flexible.
    • All servers in the OOS farm must be in same data center
    • You need a loadbalancer if OOS farm consist on more than 1 server.
    • LoadBalancer should meet the following requirement
      • Layer 7 routing
      • SSL Offloading or SSL Bridging
      • Enabling client affinity or front-end affinity
  • Hardware and Software Requirement
  • Language Packs
    • OOS server support multiple languages, Download the Language packs from this link (https://www.microsoft.com/en-us/download/details.aspx?id=51963)
    • It is highly recommended to install the base language pack before applying any updates to farm.
    • Same Language pack must be installed on both (OOS and SharePoint)
    • Language Pack must be installed on all server in OOS farm
    • There are no separate updates for the Language Packs.
  • Authentication and Firewall
    • OOS only support the Claims Based Authentication on Web Application, No Classic based
    • OOS support both Http & Https
    • OOS can be access via Internal or External Url or both using either http or https.
    • It is recommended use the Https for the Incoming traffic
    • No firewall blocking between OOS and SharePoint host.
    • Make Sure following ports are not blocked in firewall or used by other application.
      • 443 for HTTPS traffic
      • Port 80 for HTTP traffic
      • Port 809 for private traffic between the servers that run Office Online Server
  • SSL
    • SSL certificate must be installed on SharePoint farm (using Central admin > security manage trust, you can add it)
    • SSL certificate from trusted certificate authority
    • SSL Certificate in OOS must include the FQDN of OOS in Subject Alternate Name.
    • If you have multiple server in OOS farm, all server’s FQDN must be in Subject Alternate Name.
  • Configuration http
    • To Create single Server OOS f arm over Http (not recommended for the Production farm) (Run this on OOS server)
    • Configure SharePoint Server to use Office Online Server using Http, run following commands (Run this on SharePoint server)
    • To Set the WOPi Zone (Run this on SharePoint server)
    • If Use Office online server over http (which is highly recommended for the Test environment only) then you have to configure the Oauth over http otherwise it won’t work. (Run this on SharePoint server)
    • To test the OAuth over http run this command
  • Configuration https
    • To Create single Server OOS f arm over Https (Run this on OOS server)
    • Configure SharePoint Server to use Office Online Server using Https, run following commands. (Run this on SharePoint server)
    • To Set the WOPi Zone. (Run this on SharePoint server)
  • Excel Service
    • Excel Service is now part of OOS
    • Build server-to-server authentication between SharePoint Server 2016 and Office Online Server 2016, in order to use the advance feature of OOS ( I.e. excel data refresh).
    • To enable the Excel SOAP API
  • Wopi Zones
    • SharePoint server use the following WOPI zones
      • Internal-http
      • Internal-https (default)
      • External-http
      • External- https
    • If you want to use the external url then run the WOPI zone command will be like this. (No Need to use the Internal zone)
      • Set-SPWOPIZone -zone “external-https”
  • Testing
    • After Successful installation, you can test OOS via http://OOS server/hosting/discovery
    • Office Online server cannot be tested via System account. You need a user account to test it.
    • Browse to SharePoint Site and open the any Office document, if it open in Office online (browser) then your configuration are correct.
    • Goto Search center and search for the office document, Hoover the Mouse on the URL & you will see the Document Preview in popup window.
  • Always Monitor Office online server, at least for the memory usage, if servers run out of memory then it can be failed.
  • To disconnect Office online farm from SharePoint 2016, run this command
  • Updates and PowerShell
    • By default, Windows PowerShell include the Office Online Server Module added in it but for reference here is module to be used to import all OOS PowerShell commands
    • To apply the Updates to Office online Server, you have to remove the server from 1st then apply the updates.
    • Once Server upgraded then add the server into farm by running new command.
    • Some handy PowerShell commands

Reference

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *