Forum Discussion
Setting up WOPI Binding to Office Online Server Multi-server (not load balanced)
Thanks, I rechecked my config this morning and discovered a couple of things
- The external url I had configured when I created the farm was incorrect as there wasn't a DNS entry for each OOS. Not an issue as not allowing external access.
- The main show showstopper is exactly as you have stated no clients can access OOS on port 443. Looks like we missed the firewall rules for OOS when as part of a previous installation.
If I put in a RFC in tomorrow, then a part from ports: 80 and 443 , are there other ports OOS needs to communicate with clients that you can think of?
We do have the option for internal CA but I have testing with self-certs, which I export as ".cer" and import into the Trusted Hosts on each of WFEs. I assume this is ok.
Looking at DNS with entries per OOS verses Load balancer - going to test with the single instances ( each bound to a single WFE) when the rules are in place and give the business the option.
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.
- 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.
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.