Office Web Apps ServerComments (0)
Office Web Apps Server is an Office server product that provides browser-based file viewing and editing services for Office files. Office Web Apps Server works with products and services that support WOPI, the Web app Open Platform Interface protocol. These products, known as hosts, include SharePoint 2013, Lync Server 2013, and Exchange Server 2013. An Office Web Apps Server farm can provide Office services to multiple on-premises hosts, and you can scale out the farm from one server to multiple servers as your organization’s needs grow. Although Office Web Apps Server requires dedicated servers that run no other server applications, you can install Office Web Apps Server on virtual machine instances instead.
Setup Office Web Apps for Lync Server 2013Comments (0)
Lync Server 2013 uses Office Web Apps Server to handle PowerPoint presentations as legacy systems like Lync 2010 used the client to render information.
Install Windows Components
Add-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, NET-Framework-Features, NET-Framework-Core, BITS -Source D:\sources\sxs
Download the package
Download the language pack
Create a farm using HTTPS
New-OfficeWebAppsFarm -InternalUrl "https://owas01.company.com" -ExternalUrl "https://owas.company.com" -CertificateName "Office Web Apps Certificate" -EditingEnabled
Run the following:
dism /online /enable-feature /featurename:IIS-ASPNET45
Verification, try to browse the following URL
Firewall requirements for Office Web Apps Server when configured alongside a Lync pool!Comments (0)
Communication between a web browser and servers that run Office Web Apps Server are common knowledge. This usually caused when placing OWAs server in a different area in the network, not alongside clients or Lync Servers.
Ensure that the following ports are open on either OWAs server(s) or HLB:
- 809/private traffic between OWAs servers if running a multi-server farm
Troubleshooting Office Web Apps together with Lync Server 2013!Comments (0)
So you have installed a new Lync 2013 environment and added the OWAS (WAC) server but powerpoint presentations cannot be shared.
You can try out two things here than can narrow down the root-cause!
1) Validate the configuration by navigating to the discovery URL of the Office Web Apps server. Example would be:
If you can see and XML file, this is a good thing meaning the IIS and permissions is OK.
2) After Office Web Apps Server has been added to the topology, and after that topology has been published, you should see two new event log events in the Lync Server event log.
An LS Data MCU event (event ID 41032) should be added; this event will report that the Office Web Apps Server has been discovered:
Web Conferencing Server WAC is discovered, PowerPoint content is enabled.
Another LS Data MCU event (event ID 41032) shall be added that reports back Office Web Apps Server URLs. For example:
Web Conferencing Server WAS discovery has succeeded.
WAC internal presenter page: https://owas01.company.com/m/Presenter.aspx?a=0&embed=
WAC internal attendee page: https://owas01.company.com/m/ParticipantFrame.aspx?a=0&embed=true&=
WAC external presenter page: https://owas01.company.com/m/Presenter.aspx?a=0&embed
WAC internal attendee page: https://owas01.company.com/m/ParticipantFrame.aspx?a=0&embed=true&
If you see an LS Data MCU event with the event ID of 41033 that means that Office Web Apps Server discovery has failed. In that case, Microsoft Lync Server 2013 will try as many times as needed to discover the newly-configured Office Web Apps Server. If the discovery process fails repeatedly you should remove Office Web Apps Server from your topology document, publish the updated topology, and then try adding Office Web Apps Server back to the topology after the connectivity issues have been resolved.
One last thing...it seems that the official installation documentation does not mention .NET Framework 3.5 for WAC to operate correctly.
Install it via PowerShell using:
Add-WindowsFeature NET-Framework-Features, NET-Framework-Core
Error when trying to browse Office Web Apps!Comments (0)
When Office Web Apps are to be utilized by Lync Server 2013 there are sometimes issues when trying to browse https://owas.company.com/hosting/discovery
The error message that are being displayed is: Lync 2013 WAS Handler Error 500.21
To resolve this issue verify that .NET Framework is installed and then re-register it again using: