Forum Discussion

Iron Contributor

Feb 21, 2018

Setting up WOPI Binding to Office Online Server Multi-server (not load balanced)

Hi I have inherited and existing on-premises farm infrastructure that consists of a pair of load balanced SharePoint 2016 WFEs with each having a single Office Online Server (OOS) instance. Th...

Iron Contributor

Feb 21, 2018

OK, lets clarify things from my perspective . The client is any intranet user who needs to render an office document that is hosted on premises - they don't need a cert import as far as know . I have only exported the cert created on a OOS instance onto the WFE in the same data centre . Repeat this config per data centre.

When I refer to the OOS farm , I mean going on to each OOS instance and running

New-OfficeWebAppsFarm -InternalUrl "https://oosa.contoso.com" -ExternalUrl "https://oosa.constso.com" -CertificateName "OfficeWebApps Certificate" -EditingEnabled

Then repeating for the other OOS instance (oosb.contoso.com) . I don't think it is possible to configure a multi-server OOS farm as there is currently no LB IP address available.

Trevor Seward

MVP

Feb 21, 2018

You can configure a multi-OOS farm without a load balancer, but yeah traffic will only be directed at a single host so the utility isn't there (I'd argue just get a free LB, like HAProxy). On the other hand, why build multiple OOS farms? Just share a single farm among multiple SharePoint farms/Exchange/SfB deployments.

Daniel Westerdale
Iron Contributor
Feb 21, 2018
I think you are right. I did the single host config just to get a demo working. However, with a bit more effort, I could configure one of the LBs and create a multi-sever OOS farm, to be shared across SFB, Exchange and the other SharePoint farms ( sp2016 dev , SP2013). Thanks, I will mention this to the team tomorrow.
- Trevor Seward
  MVP
  Feb 21, 2018
  If you go multiple server, you will want to have a trusted cert (internal or public). You need to have a subject name of the FQDN of the deployment (e.g. office.example.com) with multiple SANs. The first will match the subject name, the subsequent will be the FQDN of the Office Online Servers within your deployment (e.g. oos01.corp.example.com, oos02.corp.example.com, etc).
  - Daniel Westerdale
    Iron Contributor
    Feb 21, 2018
    Trevor Seward wrote:
    If you go multiple server, you will want to have a trusted cert (internal or public). You need to have a subject name of the FQDN of the deployment (e.g. office.example.com) with multiple SANs. The first will match the subject name, the subsequent will be the FQDN of the Office Online Servers within your deployment (e.g. oos01.corp.example.com, oos02.corp.example.com, etc).
    
    I understand ... let's hope the business agrees to this I think this the way we should go . Thanks for your help.