UPDATE: I have updated this post for Lync Server 2013 RTM, although some screenshots may still say “preview” on them.
Introduced in Lync Server 2013 is the requirement of Office Web Apps server to support the use of PowerPoint presentations in Lync Online Meetings. The purpose of this post is to show the absolute minimum requirements in order to get Office Web Apps integrated and usable with the Lync Server 2013 environment. This does not take into account high availability or other design decisions that may need to be made for your overall implementation.
Requirements and Prerequisites
Office Web Apps cannot be collocated on any Lync server, so I am starting off with a fresh installation of Windows 2008 R2 SP1 (Windows 2012 can also be used). You will need to install the following on the Windows 2008 R2 server:
Next thing needed is to install supporting Windows Components. For Windows 2008 R2, run:
Import-Module ServerManager
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support
For Windows 2012, run:
Import-Module ServerManager
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, NET-HTTP-Activation, NET-Non-HTTP-Activ, NET-WCF-HTTP-Activation45
Installation of Office Web Apps Server
Download the Office Web Apps Server and start the installation. Default installation is fine:
Configuration of Office Web Apps Server
The first step is to create an Office Web Apps Server farm. I will do this by running the following command. Note that I am only configuring an Internal URL for my lab and already have a certificate provisioned for the URL referenced.
New-OfficeWebAppsFarm -InternalURL “https://labad03app01.w15lab.local” –CertificateName “Office Web Apps Certificate”
Validate the configuration by navigating to the discovery URL of the Office Web Apps server. In my case, that is https://labad03app01.w15lab.local/hosting/discovery
You should see something similar to the following XML output:
If you get an error, try repairing .NET by running:
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
Configure Lync Topology
To add the Office Web Apps server to your Lync 2013 Topology, open Topology Builder and navigate to “Site –> Shared Components –> Office Web Apps Servers”. Right-click and select “New Office Web Apps Server…”
Next, type in the FQDN of your newly deployed Office Web Apps server and the discovery URL should auto-fill:
Next validate (or assign) the Office Web Apps server to your Front-End servers:
Publish your topology.
Validate Lync Functionality
The first things to validate for your Office Web Apps implementation is look at the Front-End servers Event Viewer. In the Lync Server logs, you will see two different Events:
Event 41032 stating that Web Conferencing Server Office Web Apps Server (WAC) discovery succeeded:
Event 41034 stating that PowerPoint content is enabled:
If you see Event 41033 then something is wrong. Go back and check all the previous steps.
Now on to validating PowerPoint uploads with the Lync client. In this example, I am just going to start an ad-hoc conference with Meet Now and upload a PowerPoint presentation:
This post described how to get an Office Web Apps server deployed and integrated with Lync Server 2013.
Is it required to have SharePoint 2013 deployed and integrated with the Office Web Apps 2013 server for this to be successful? Or can you literally only install Lync Server 2013 and Office Web Apps 2013 and have no tertiary installation of SharePoint 2013?
ReplyDeleteIn my lab, I do not have any other sharepoint component installed. I am assuming that Lync 2013 will support stand-alone installs of Office Web Apps.
DeleteOk that's good to know. Trying to force our SharePoint team to upgrade from SharePoint 2007 RTM (yes, you read that right....RTM) to SharePoint 2013 just to support Lync 2013 would have been a nightmare.
Deletei have problem "There was a problem verifying the certificate from the server. Please contact your support team." when i share powerpoint ?
ReplyDeleteThe certificate that you have provisioned for your office web apps server, is it trusted by the client that is connecting to it? Did you install the certificate chain correctly on the office web apps server? If using an internal certificate, make sure your client can trust it by importing the CA chain on your client machine.
DeleteI already create and assign certificate at IIS. I import Root CA chain on my computer and office web app server.
DeleteAt office web app server have error id 1010,2010,1193,2193 in eventlog
error picture:
http://imageshack.us/photo/my-images/580/001keu.png/
http://imageshack.us/photo/my-images/805/002eo.png/
http://imageshack.us/photo/my-images/835/003re.png/
http://imageshack.us/photo/my-images/4/004bw.png/
http://imageshack.us/photo/my-images/138/005x.png/
http://imageshack.us/photo/my-images/259/006fp.png/
http://imageshack.us/photo/my-images/571/007us.png/
http://imageshack.us/photo/my-images/543/008cr.png/
thank you
Can you post the results of running Get-OfficeWebAppsFarm? Also, did you run all of the server prereq's and Windows Features listed above?
DeleteI had a similar problem to the screenshots you've posted. I experienced it while trying to integrate Exchange 2013 OWA with Office Web Apps. The solution in my case was to replace the default Self-Signed Certificate on the Exchange with one from my Internal CA.
DeleteHope that helps,
Lubo.
hi Tim Harrington
Deleteresult of running Get-OfficeWebAppFarm from
http://img685.imageshack.us/img685/5627/100ho.png
i am doing follow step from this page.
thank you
I have almost similar problem.I have server connnectivity and certificate problem.I have Lync2013 and office web apps server 2013. I re-create the the certificate as per the following site http://www.ucprimer.com/deploying-lync2013-web-apps-server.html.Then domain joined computers started to work perfectly, but not non-domain computers. As per the site http://blogs.technet.com/b/lyncativity/archive/2012/12/06/troubleshooting-lync-2013-powerpoint-sharing-issue-there-was-a-problem-verifying-the-certificate-from-the-server-please-contact-your-support-team.aspx,
DeleteI disable “Check for server certificate revocation” in the IE then non-domain computers are worked.
I deployed lync 2013 in lab environment every thing success while deploying . Now the problem is lync FE service is not starting , it is showing the error code:1053( windows could not start in timely fashion).
ReplyDeleteFor this deployment am using only 2GB RAM.
Please help on the same . Appreciating for the help in advance.
Can i Collacate webapps server with FE ?
ReplyDeleteYou cannot collocate the webapps server with any other Lync role.
DeleteIn lync 2013 client meetnow option is not giving any url for meeting ..What should i do.
ReplyDeleteSo, will clients need to purchase Office Web Apps in addition to Lync 2013? Is this a paid product or free?
ReplyDeleteHi! I´m getting the same error: "There was a problem verifying the certificate from the server. Please contact your support team."
ReplyDeleteBut this error only happens on Lync 2013 Clients running on non-domain joined machines. If I try to start a powerpoint presentation from a domain joined machine, it works fine.
The chain of my certificate authority is correctly installed on the non-joined machine, so, this is not the problem.
It looks like this is related with integrated authentication or something like that.
I couldn´t find the solution yet.
Any help, I appretiate. Thanks
This comment has been removed by the author.
Deletein IE uncheck the "Check for server certificate revocation" flag
DeleteI have a weird issue...
ReplyDeleteThe data:
Everything installed properly (or seems so).
My current PRODUCTION setup is based on SBS2011 (so Exchange is 2010 SP2 and PowerPoint Services are also 2010), and on a different machine I run Lync 2013 (RTM in VM) and Office Web Apps Server 2013 (RTM in VM).
I have (for now) set OWAS only for internal access.
Also everybody is still using Lync 2010 client (on Lync 2013 server) except myself that I use Office 2013 RTM (in Office 2013 client).
The issue:
If I start a presentation, I can share whatever I want (whiteboard, screen etc.) and works fine. I can also share ppt or pptx and the clients see it fine (Lync 2010 clients remember). FOR ME that I am sharing the powerpoint (and I am on Lync 2013 client), it says that I cannot see the document because of connectivity reasons! The document that I *am* sharing and others DO see!
I plan to test the same also the other way round (start from Lync 2010 client and me with Lync 2013 as conference member) and also with both clients being Lync 2010.
Any ideas?
Good day!
ReplyDeleteI have a problem "Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled."
What me doing now!?
I deploy WAC following technet.microsoft.com/.../jj204792(v=ocs.15).aspx
Thanks.
Did you follow the validation/troubleshooting steps above? Browse the Discovery URL, look at event logs.
DeleteYes, I did!
DeleteI sow URL too.
I'm have a problem yet - "Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled".
Which OS are you installing on? Did you double-check all the pre-reqs?
DeleteHi Tim,
ReplyDeleteNice post, how ever can you please let me know the below:
1. i will deploy two office web apps servers and will be load balanced by HLB, do i have to configure the internal url and external url as well.
2. As per Microsoft technet article while defining internal url you have to provide the server fqdn even if you are using more then 1 server what if i will not put server fqdn instead i will choose another name
3. our internal dns name is different then extenral one but in our internal dns server we have external domain name zone as well where owa A records are created and pointed to CAS servers, what if i will create internal and external url same will it be fine with the link
4.If i want that those users are who are logged in outside can also view ppt presentations then should i require a dedicated public ip, external certificate and DNS A record for office web apps server
5. if i will choose internal and external url different then do i have to add all office web apps server names as well as external and internal urls in the SAN name of the certificate
Thanks
Hello Salahuddin,
DeleteI've found different things while trying to achieve what you are describing:
1. Don't try to edit manually your Web configs in IIS. OWA will use its own value as soon as you restart the server.
2. Use https in your url, and not http
3. Without running the set-OfficeWebAppsFarm and specify a full FQDN for the –externalurl switch and the right certificate name for the for the –certificatename switch
4. Be sure that you have the private key with your certificate in the computer personal certificate store – otherwise, you OWA will get you an error
5. Even I can’t confirm it is required, using the same FQDN and URLs internally and externally really simplified things for me.
6. If possible try to use a public cert – maybe the same you will use in your reverse proxy
7. Be sure your reverse proxy solution is able to reach the URL that Tim provided
7. After you confirm that all setup are ok using get-OfficeWebAppsFarm, run iisreset on the OWA server
8. Be sure that your FQDN can be resolved internally and externally. Internally, pointing to the OWA. Externally, pointing to your Reverse Proxy public IP
9. Be sure that your entry in topology builder is equal to what you have defined on the OWA server
10. Be sure your FE solution is able to reach the URL that Tim provided
11. Restart the Lync Server Web Conferencing service on your FE
12. You should get the 41032 event listing all 4 field with complete URLs
Sorry, one correction: In step 7, you need to reboot the server. IIS Reset is not enough.
DeleteGreat post! Thank you. My Office WebApps server is now running to support my Lync 2013 installation (no SharePoint). A few more pieces and I can move users off of the Lync 2010 systems.
ReplyDeleteI installed the Office Web App Server and then ran the PS cmd,
ReplyDeleteNew-OfficeWebAppsFarm -InternalURL “https://devlync03.xxx.xxx.com” –CertificateName "LYNC CERT”
It completed, then when I browse to the site with hosting/discovery at the end I do not see XML, I just see:
Server Error
We're sorry. An error occurred.
We've logged the error for the server administrator.
Thoughts?
did you run the repair on the .NET as described in the blog?
DeleteThanks Tim,
ReplyDeleteI have done mine for production and did it using the same command but replaced internalurl with externalurl and published the web on TMG reverse proxy.
it's working like magic now.
Mo
Excellent guide!
ReplyDeleteHi,
ReplyDeleteI have setup the Office Web App server and I am getting the certificate verification error. I used this command:
New-OfficeWebAppsFarm -InternalUrl "https://grathlyncwa03.mydomain.group" -ExternalUrl "https://was.publicdomain.com" -CertificateName "Friendlynameofpubliccertificate" -EditingEnabled.
in order to support internal and external users. Should I use only the -external option for that?
At an earlier stage, I had set it up only for internal purpose and it was working just fine.
Thanks in advance,
Argi
Great Post, I followed it closely, and was thrilled to get 41030 and 41032 events. I had a lovely XML page at https://server.company.local/hosting/discovery
DeleteAll looked good but I was disappointed since when I try and launch a powerpoint presentation I was faced with "Some Sharing Features are unavailable due to server connectivity issues" regrettably I have been look everywhere for a result. I have read lots of forums all to no avail. Can anyone assist.
All my servers are internal, I can see instant messages and can video conference etc. I am able to share whiteboards etc, just no the Presentations. The only slight difference is that my clients are on one domain and the Lync servers (2008r2) are in another. I have full rights to both domains though.
Please help
Desperate from the UK (Bayf)
Thanks very much. In your guide you mentioned this
ReplyDelete"Note that I am only configuring an Internal URL for my lab and already have a certificate provisioned for the URL referenced"
How did you do that bit, I am convinced the issue I am having is a certificate issue.
Andy, I think you need to restart Lync Front End service in order for Presentations to start working.
DeleteHi Mohammed, I did that as a matter of course. Over the weekend I started again from the very beginning, still no joy. I follow the instructions to the letter. I restart iis, and get the XML as expected, after the Configuration I get the output as shown. Launch a presentation, still same issue.
ReplyDeleteI have been looking everywhere and tried lots of things, but still no go. I wonder if it is something really simple, that I just dont know about.
Regards
Bayf
It's Odd, make sure you're using a certificate that's domain signed and in Lync topology, the WAC server you have it set as Internal too.
ReplyDeleteTry allowing HTTP as well.
Set-OfficeWebAppsFarm –InternalUrl “https://lyncwebapp.domain.com” -CertificateName "lyncwebapp" -AllowHttp
Hi Tim
ReplyDeleteI have a lync 2013 enterprise pool with 3 front ends and have configured 2 load balanced office web apps servers. I get the 41032 message in the eventlog but no 41034 or even 41033. Any ideas?
Thanks in advance
solved it. turns out the wac servers wasnt able to find the lync front end web dns records, which in turn gave the same error on the client.
DeleteHi,
ReplyDeleteI think this post should get changed to support also the external name.
New-OfficeWebAppsFarm -InternalURL “https://labad03app01.w15lab.local” –CertificateName “Office Web Apps Certificate” should get enhanced by the -ExternalURL. Just leaving it as for internal users is not an option in my eyes as the topic is already confusing enough. Leaving it out is a dead end if you decide to later add edge features.
Despite this, it's a nice article.