Update 4/8/14 - Updated prerequisites for Windows Server 2008 R2.Update 1/12/13 - Updated with additional information.Update 11/10/13 - Updated with links to updates for Office Web Apps Server.Update 3/18/13 - Updated for RTM of Lync Server 2013.Update 11/14/12 - Updated for RTM of Office Web Apps Server.
The Office Web Apps Server is a required role when deploying Lync Server 2013. By default when you add conferencing to the pool, you'll notice that in Topology Builder, you will be required to associate the Standard Edition Server or Enterprise Edition pool with an Office Web Apps Server, either new or existing:
However, you can deselect the check box and continue along without associating the Office Web Apps Server. This is not recommended, as you won't be able to use any features that rely on the Office Web Apps Server.
Defining a New Office Web Apps Server is easy...all you need is the FQDN of the server:
Once the Office Web Apps Server is defined, Topology Builder will let you continue:
So what is the advantage of using an Office Web Apps Server? From the Overview of Office Web Apps Server TechNet article:
How Lync Server 2013 uses Office Web Apps Server for viewing PowerPoint broadcasts
In Lync Server 2010, PowerPoint presentations are viewed in one of two ways. For users who run Lync 2010, PowerPoint presentations are displayed by using the PowerPoint 97-2003 format and they are viewed by using an embedded copy of the PowerPoint viewer. For users who run Lync Web App, PowerPoint presentations are converted to dynamic HTML files then viewed by using a combination of the customized DHTML files and Silverlight. Although generally effective, this approach did have some limitations:
To help address these issues, and to improve the overall experience of anyone who presents or views PowerPoint presentations, Lync Server 2013 uses Office Web Apps Server to handle PowerPoint presentations. Among other advantages, this new approach allows the following capabilities:
Now that you know what the Office Web Apps Server does, how do you go about preparing to install it? From the Deploy Office Web Apps Server TechNet article:
Installing Required Roles and Services
Windows Server 2008 R2 and Windows Server 2012/2012 R2 have slightly different prerequisites. Be sure to install the correct prerequisites for your operating system.
To prepare a server that runs Windows Server 2008 R2:
Install the following software:
Next, open the Windows PowerShell prompt as an administrator and run the following sample commands to install the required roles and services:
To prepare a server that runs Windows Server 2012/2012 R2:
Make sure that you also install any updates to the Office Web Apps Server(s). You will need to download and install the updates listed here: Update center for Office, Office servers, and related products.
When creating the certificate request the Office Web Apps Farm make sure that you include SAN entries for the FQDNs of all of the servers in the farm:
If you don't include all of the Office Web App Server 2013 server FQDNs in the SAN of the certificate, you may see the issues here.
Once you have the Office Web Apps Server installed, updated, and configured, the Lync Server 2013 Front End Servers will discover the Office Web Apps Server and you will see the following events in the Event Log on the Front End Servers:
What is the User Experience if you Don't Deploy an Office Web Apps Server?
So what happens you define, but haven't yet deployed an Office Web Apps Server in your environment? The first thing you'll notice is that the Lync Server 2013 Front End Servers will throw the following error in the Event Log:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
Attempted Office Web Apps Server discovery Url: https://TEST-OWAS.test.deitterick.com/hosting/discovery/Received error message: The remote name could not be resolved: 'test-owas.test.deitterick.com'The number of retries: 2, since 8/7/2012 10:38:06 PM.Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.Resolution:Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
Also, clients will notice the following error message when they try to share a PowerPoint presentation:
As you can see, the Office Web Apps Server will be an important component in your Lync Server 2013 deployments! Make sure to plan and include it when installing/migrating to Lync Server 2013.
I have a problem "Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled."
What me doing now!?
I deploy WAC following
@Maksim V. Lemeshko
Are you using a certificate on the Office Web Apps Server that Lync trusts and vice versa? What happens when you go to the Office Web Apps Server discovery URL? Do you see XML or do you get an error?
Whet i go to Office Web Apps Server discovery URL i receive this XML code:
<?xml version="1.0" encoding="utf-8" ?>
- <net-zone name="internal-http">
- <app name="Excel" favIconUrl="http://servername/x/_layouts/images/FavIcon_Excel.ico" checkLicense="true">
<action name="view" ext="ods" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" />
<action name="view" ext="xls" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" />
<action name="view" ext="xlsb" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" />
<action name="view" ext="xlsm" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" />
I using options with IIS "Create Self-Signed Certificate"!
When you say you're using "options with IIS "Create Self-Signed Certificate"", if that means you're using a certificate issued by the Office Web Apps Server, then that isn't going to be trusted by Lync. You need to use a certificate issued from either an internal certificate authority or a public certificate...something that is trusted by both Lync and the Office Web Apps Server.
I have created the farm without the certificate:
New-OfficeWebAppsFarm –InternalURL "http://SERVERNAME" –AllowHttp.
Then the discovery URL is working fine but it is not working after I configured it in the front end. I still recieve the 41033 error. Is it a must to have it https? Any help for troubleshooting please?
Hi, I have deployed the Office Web App Server and can see within the FE Lync event logs that it has been discovered successfully because I can see entrie for 41032 and 41034. However when I try to connect to the hosting/discover URL I cannot gte to see the xml, it comes up with a 404. Will it still work or should I be able to connect to discovery within a browser? I am using an internal certificate which is trusted by the FE and OWA server.
You should see the XML when going to the /hosting/discovery URL. You shouldn't be getting a 404 error message.
I'm having an issue when uploading big powerpoint files! It works with small size presentations but not with big ones.
I couldn't see any errors except this on Lync FE.
Event ID: 41029
No connectivity with the Lync Web App. Affected Web browser clients cannot use Web Conferencing modality.
Server Machine FQDN: My Lync FrontEnd FQDN, Port:8061
Server Type: External-WebApp-Edge [HTTP side error:The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.]
If the problem persists this event will be logged again after 20 minutes
Cause: Service may be unavailable or Network connectivity may have been compromised.
Two quick questions:
So, is it mandatory to install a WAC server?
Could be installed in the same Lync 2013 Server.
If you are going to be using conferencing, then yes, it will be a required role. No, it will need to be a separate server. We don't support collocating it on any Lync Server 2013 servers.
Im facing problem in discovering office web server from Lync 2013 stnd edition server. I can access the OWAS server Url from Lync Server and its showing the URL.im getting the follwing error on my lync server
Log Name: Lync Server
Source: LS Data MCU
Date: 1/14/2013 12:26:44 PM
Event ID: 41033
Attempted Office Web Apps Server discovery Url:
Received error message: Invalid Uri syntax for WAC configuration
The number of retries: 1,
Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.
Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
I can access the OWAS server Url from Lync Server
<?xml version="1.0" encoding="utf-8" ?>
- <net-zone name="internal-https">
- <app name="Excel" favIconUrl="owas-01.xxxxx.com/.../FavIcon_Excel.ico" checkLicense="true">
<action name="view" ext="ods" default="true" urlsrc="hq-owas-01.kufpec.com/.../xlviewerinternal.aspx />
<action name="view" ext="xls" default="true" urlsrc="hq-owas-01.kufpec.com/.../xlviewerinternal.aspx />
<action name="view" ext="xlsb" default="true" urlsrc="hq-owas-01.kufpec.com/.../xlviewerinternal.aspx />
I’m using Web Server certificate on both server issued by the same internal CA. I can access the Office Web Apps Server URL and i can access the server without any issue..
Lync Topology also published without any errors
Any help to solve this problem is highly appreciated..
Thanks in advance,
I have soloved the problem with powerpoint presenations and OWA discovery after re-issuing new OAuthTokenIssuer certificate . My server already had one cerifficate issued by the same CA..but no idea why it was not working..Any way after installing NEW certificate everything started working..Lync Server has discovered the OWA pool.also my powerpoint presentations also working fine.
Server-to- server communication in Lync 2013 and using Token certificate is more important..
Thanks to all...
Guys, When I try access
servername.corp/.../discovery I receive a simple message "Server Error. We're sorry. An Error has occurred".
Anyone know about this?
I have a fairly simple setup. All internal on a single domain. I Am trying to install the Office Web Application Server. There is only one server in the pool.
The rest of the servers are installed fine. I am able to instant message and Conference call with Video. I am able to share whiteboards etc.
When I try and present a Powerpoint I get "Some Sharing Features are unavailable due to Server Connectivity Issues"
I have tried lots of things, I have been through numerous threads including all those suggestiions on this thread
I am convinced it is to do with certificates but could be wrong.
For the record, I can see the full XML stuff when I visit
server.domain.local/.../discovery I am also able to see the 41032 and 41030 events as expect.
Can anyone help, I am desperate and have been looking for a solution for about 3 days pretty much solidly.
Have you restarted both servers?
Cna the FE sees the WebApps Server correctly? After the restart can you see the Events refered?