Since May 4th, 2016 the Office Online Server (OOS) has been officially available (announced here). It’s the successor of the Office Web App Server and is used with Skype for Business Server 2015 for sharing PowerPoint presentations during meetings. The Office Online Server can also be used with Lync Server 2013.
Today I will talk about how to deploy Office Online Server for a Skype for Business Server 2015 environment. In this lab the Office Online Server will only be deployed for internal use.
The hardware requirements are described as “Office Online Server uses the same minimum hardware requirements as SharePoint Server 2016” (listed here). In my opinion you can go with less than that for just viewing PowerPoints.
The system requirements for Office Online Server are the following:
- Windows Server 2012 R2
- Microsoft .NET Framework 4.5.2 (get it here)
- Visual C++ Redistributable for Visual Studio 2015 (get it here)
- All available Windows updates installed
You will also need to install some additional Windows features:
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 -restart
Your server has to reboot to complete the installation.
Deploying the Office Online Server
1. First step is to run the setup.exe for Office Online Server and follow the wizard to install it.
2. Then you will need to request a certificate, which you will assign to OOS in step 3. I requested mine using the MMC Certificates Snap-in:
Right Click on Personal –> All Tasks –> Request New Certificate
You can use the default “Computer” certificate template. Click on “Properties” to make some adjustments.
Add a “Friendly name” – this is important, because you will use this name to assign the certificate to the Office Online Farm later.
Add the OOS External Web URL as a subject name (field “common name”) and the server FQDN as SAN (field “DNS”). For this lab the Office Online Server FQDN is the same as the Web URLs (internal/external), this is probably not something you would do in production, but for this lab simplicity is key.
You can also remove “Client Authentication” from the “Extended Key Usage”, which is included in the default template.
Finish you certificate enrollment and check your new certificate.
3. Last step is to create a new Office Online Server Farm. Define your internal OOS URL, External OOS URL and the certificate friendly name.
New-OfficeWebAppsFarm -InternalURL "<internal OOS URL>" -ExternalURL "<external OOS URL>" -CertificateName "<certificate friendly name>"
This command will take a bit to finish. When it’s done, the configuration of your new OOS Farm will be shown:
You can test if your OOS Server is working, if you enter the discovery URL (https://<OOSURL>/hosting/discovery) into a browser. If everything works alright, you will see some XML information.
Integrating OOS in Skype for Business Server 2015
1. Open your Skype for Business Topology Builder and download you current topology.
2. Under “Shared Components” add a “New Office Web App Server…”. At the moment this option is still refered to as Office Web App Server, I guess this will be renamed in future updates.
3. Add your Office Online Server FQDN and the discovery URL you tested a few steps earlier.
4. Also don’t forget to assign the Office Online Server to your Front End Pool.
5. Publish your topology.
Shortly after you should see Event 41032 (Web Conferencing Server Office Web Apps Server (WAC) discovery succeeded) and Event 41034 (Web Conferencing Server has successfully discovered Office Web Apps Server, PowerPoint content is enabled).
Try sharing a PowerPoint with your client now – it should work like a charm.
If your conferencing content along with your PowerPoints just don’t want to work for some reason, make sure you check whether you have installed .NET Framework Security Update MS16-065 on your Front End Server. If that’s the case, have a look at this.
I support partners with their Skype for Business projects and offerings following the Skype Operations Framework.
Opinions displayed on this blog and my social media pages are my own and do not express the views and opinions of Microsoft.
Latest posts by Simone (see all)
- Office Online Server with Skype for Business – Deployment - 1. July 2016
- Quickie: Mainstream support for Lync 2010 ending soon - 23. February 2016
- Using SEFAUtil – Part 2 – Perform configuration using the tool - 21. July 2015