Office Web Apps, which is now Office Online Server, allows to display/edit Office documents(Word, Powerpoint, Excel…etc) on a Web Browser, which is advantageous when working with SharePoint, thus Users don’t have to switch from a Browser to Office App to see or to edit a document.
Today i faced a Problem that made me crazy while connecting SharePoint and Office Webapps(Office Server Online).
When i run the command
New-SPWOPIbinding -ServerName srv-apps
I got the error : “The Server does not respond, trying again”, if i add the parameter -AllowHttp it works though… but here i am trying to implement a HTTPS connection.
So here the steps that i followed to resolve the problem.
Office Server Online :
Before starting the Setup.exe from the Installation DVD, you should install those Windows-Feature prerequisites :
Now you are ready to start the Setup.exe.
After the installation let’s configure our Office Server Online Farm :
New-OfficeWebAppsFarm -ExternalUrl “https://webapps.sharepoint.yourdomain.com” -InternalURL “https://webapps.sharepoint.yourdomain.com” -EditingEnabled -CertificateName “SharePoint Certificate”
3 important things :
- The Url i chose was a subdomain of my sharepoint domain for the only reason that i wanted to use one single Certificate for both of them
- ExternalURL and InternalURL are also the same : it was unfortunately the only solution i found to bypass the LoadBalancer problem
- Of course don’t forget the DNS entry webapps.sharepoint.yourdomain.com <-> Officer Server Online
Last step on the Office Online Server is to load the certificate on IIS :
Now lets move on to SharePoint and it is quite easy, we first need to set a Property on the Farm’s Propertybag.
$farm = Get-SPFarm
Another step is to allow OAuth over HTTP
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOaAuthOverHttp = $true
Next Step is to create the Binding
New-SPWOPIBinding -ServerName webapps.sharepoint.yourdomain.com
Here it is important to give the FQDN that you used as internal URL, if you just use the server name you will get the error mentioned up.
and last but not Least set the Zone, you can use “internal-https” if your farm is only internally accessible, otherwise you should use “external-https”
Set-SPWOPIZone -zone “external-https”
To test if it worked navigate to a SharePoint SiteCollection and you will notice that when you click on “+ new” inside a Library you will now get the Office Templates, instead of the Upload Pop-Up.
You will also be able to see the Document Preview and of course open the document in the Browser instead of getting it downloaded.