Office Web Apps (OWA) deployment and licensing

Hi,
Im trying to get some info about how to eventually purchase and install Office Web Apps (View only) for all Sharepoint-users in the farm.
As from 22/10 -14 OWA is no longer available for download from Microsoft Download Center.
Source: Technet
They're redirecting users to the Volume Licensing Service Center, but the link is dead.
What i found searching is this page with lack of info: http://www.microsoftvolumelicensing.com/ProductPage.aspx?pid=387
I feel stupid, but this page says nothing to me.
Is there any obvious way to calculate the cost of OWA?
Does OWA even cost if the organization is just going to View but not edit?
From where should i get the installationpackage now when Microsoft Download Center got rid of it?
Kr,
Rasmus

Hi,
Office suite licenses(Standard or Pro Plus) are only required for those employees editing Office Web Apps documents.
The Office Web Apps are included when you purchase Office Professional Plus 2013 or Office Standard 2013 licenses and allow you to
view and edit Office files using the Office Web Apps Server.
Office client suites are licensed per device. The primary user of a device licensed for this Office software is licensed for access to the online companion Office Web Apps from any device. In these situations, the primary user is enabled for remote online
access through Office Web Apps.
thanks
diramoh

Similar Messages

SharePoint 2013 disable Save/ Share or Print option in Office Web Apps for PDF and Word Docs

Hi,
How can we disable Save/ Share or Print option in Office Web Apps for Word and PDF files.
Regards,

Rights Management Server/Service
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

SharePoint 2013 - Office Web Apps - Internal and External Use

I have successfully installed SharePoint 2013 and Office Web Apps on Azure VMs inside an Azure Virtual Network (IaaS model). Everyting is working well. However, my testing has shown that external users and internal users can't use Office Web Apps at the
same time.
Office Web Apps, installed on its own vm, accomodates an external and internal URL quite well. However, SharePoint 2013 appears to only allow one setting for WOPI Zone, either internal or external but not both. I've set the WOPI zone to Internal-HTTPS (Set-SPWOPIZone
–Zone “internal-https”). OWA works just fine if accessed from inside the Azure Virtual Network. However, if I try to access from outside the Virtual Network, from the Internet, Office Web Apps fails. The exact oppisite is also true. I can set WOPI Zone to
External-HTTPS and accessing from the Internet works fine, but accessing inside the Virtual Network fails.
Am I missing something? I, obviously, want Office Webs Apps to function properly for both internal and external users simultaneously.
I appreciate any help anyone can provide here.
Glenn

Hi Glenn,
To have both the use of Internet and Internal available to your end-users, you first need to configure AAM setting. Open Central Administration > Application Management > Configure alternate access mappings. Let's say there is an existing web application
named http://sharepoint and my end-users from local network are able to access it using the URL http://sharepoint (root site collection). Here you need to add the Internet URL by select the web application and click Edit Public URLs. Add the Internet domain
to the web application, e.g http://sharepoint.abc.com. You don't necessarily have to edit binding setting in IIS. Before continuing next steps, make sure you are able to access http://sharepoint.abc.com from the Internet while being able to access http://sharepoint
from local network (aka Internal).
On the machine where Office Web App (OWA) Server 2013 is installed, open PowerShell to add OWA module and use the following command to re-create a new OWA server farm if you've completed configuring it previously.
New-OfficeWebAppsFarm -InternalUrl "http://owa" -ExternalUrl "http://owa.abc.com" -EditingEnabled.
In this case, I'm not using SSL certificate to encrypt data over the Internet. You can use Internet-public IP of the OWA server like -ExternalUrl "http://198.xxx.xxx.xx". Add CertifcateName parameter if you want to use whether CA-issued certificate
or self-signed certificate.
On your SharePoint machine, you need to re-bind all WFE machines to WAC farm using the cmdlet New-SPWOPIBinding. Next, you need to set the WOPI zone for both internal and external.
Set-SPWOPIZone -zone "external-http"
Note: I'm not all using certificate in my guidance. But the steps to have it configured is just to add more parameter.
I've recently successfully deployed OWA multi-server farm for both internal and internet uses for two big clients. In real-world scenario, ideally OWA should be published through firewall (Forefront UAG, TMG, F5...etc). Please let me know if you still have
issues after following my steps. My email: [email protected]
Regards,
-T.s
Thuan Soldier
A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
SharePoint Vietnam |
Blog | Twitter

Exchange Office Web Apps Preview Does not work in OWA (web)

I have setup Exchange 2013, Lync 2013, SharePoint 2013, IIS as a Reverse Proxy Server, an Office Web Apps Server, etc, etc. Everything is setup to use SSl (https) and everything works great EXCEPT... Office Web Apps... and ONLY via Exchange and OWA (exchange
browser-based access).
I can login via the intranet or Internet for everything (SharePoint, Outlook, and Lync) and Office Web apps functionality works flawlessly for all... except for Exchange and OWA.
If I login in to a web-based Exchange seeion, everything works right and I can see the various attachments.
For all other scenarios, Office Web Apps works (SharePoint, Outlook, Lync, etc), but in owa (web version of Outlook) I see that Office Web Apps is triggered (I see the Office Web Apps text and the dots that indicate something is loading)... However, it just
crashes and eventually times out (see image):
If I look in the error logs for the Web Apps Server I see this:
Essentially, it looks like that owa uses a distinctly different path to load the attachments into the Web Apps Server such that the file is not found!
What is happening? Why does Exchange OWA (web version of Outlook) somehow use a different path that fails to locate attachments in Office Web Apps, but Lync, Outlook, and SharePoint (both in Intranet and Internet) work perfectly?
This is VERY frustrating. Can anyone help?
Please?
Clearly, the reverse proxy is working, the certificates are working, OAuth is working, etc. It seems there must be some variable/path that is only defined in Exchange for OWA that uses a different path for Office Web App attachments and that path is WRONG!
Please, help!
Thanks

Hi,
Thanks for sharing. It’s glad to hear the good news.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange and Office Web Apps Integration - Wrong Url to Outlook Web App port 444

Hi,
I'm trying to setup Office Web Apps integration with Exchange 2013. Office Web Apps are working fine with SharePoint 2013 and the WAC servers are listed as in a healthy state.
When trying to open an office document from OWA I get the usual "Sorry...we ran into a problem. Please try again"
However I have noticed that the URL that OWA is passing WAC is in the format: https://exchangeservername.domain.com:444/owa/[email protected]/wopi/files...
This is the backend server address! All the internal and external urls for owa, ecp, ews etc are set to https://mail.domain.com and they all seem to be working fine. Client Access and Mailbox roles are on the same server.
If I change the url to https://mail.domain.com/owa/[email protected]/wopi/files... then the office file opens correctly in Office Web Apps
How do I correct the URL that OWA is sending Office Web Apps?
Thanks!

Hi DJL,
If everything works well except open document via OWA, it seems Exchange server 2013 has been configured correctly.
Please follow me to check Office Web Apps Server settings and Integration.
OWAS settings
1. Certificate:
Come from a trusted CA, include FQDN of OWAS farm in SAN field.
Exportable private key.
Friendly name must be unique within Trusted Root Certificate Authorities store.
2. Farm:
New-OfficeWebAppsFarm with following parameters
-InternalURL is the FQDN of the server that runs OWAS
-ExternalURL is the FQDN so that OWAS can be access on the Internet
-CertificateName is the friendly name of the certificate to be used for HTTPS
3. Explore this URL https://mail.domain.com/hosting/discovery
If OWAS works well, you can see a WOPI-discovery XML file in web browser.
Integration
1. Configure OWAS URL via EMS,
Set-OrganizationConfig –WACDiscoveryEndpoint https://mail.domain.com/hosting/discovery
2. WAC stands for Web Access Components.
Check App Log the 140 and 142 Event IDs for MSExchange OWA.
142 means the discovery of the OWAS was successful, 141 means something went wrong.
3. Enable OWAS.
By default, OWA Virtual Directory is already enable WAC Viewing on both public and private computer.
Please run "Get-OwaVirtualDirectory | FL *wac* "to check whether both “WacViewingOnPublicComputersEnabled” and “WacViewingOnPrivateComputersEnabled” parameter is True.
4. Method to collect logs on OWAS.
Run following command in OWAS powershell prompt:
Get-OfficeWebAppsFarm | FL *log*
More details to refer:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-2013-office-web-apps-server-integration.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange Office Web Apps Preview Does not work in OWA. An error occurred while the document preview was being created

Hi,
I have managed to configure intergration between Office Web App server 2013 and Exchange 2013 OWA.
I have created a test users Test1 and Test 2. I have given full access on Test2 mailbox to user test 1.
When I login to owa for user test1 and preview the attachment it works fine.
However when I use "Open another mailbox" in OWA and open test2 mailbox and try to preview the attachments in test2 inbox it errors as
" An error occurred while the document preview was being created. Please try again later " as follows
I am new to office web apps server 2013 and implemented it first time. Can anyone suggest resolutions or troubleshooting ?

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Does the error appear when you directly access test 2 mailbox through OWA?
2. Check if there is 141 error in your event log.
3. Check whether Office web app server connects with Exchange server when the issue happens.
Access the URL: https://hostname/hosting/discovery
4. Grant full access permission again and check the result.
For more information about Office web app integration with Exchange, please refer to the following article:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-2013-office-web-apps-server-integration.html
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Sharepoitn 2013 - Office Web Apps Licensing

Dears,
I do have the license key with me for the office web apps 2013. The office web apps are working with our SharePoint 2013 portal without any issues. We were able to view the documents but couldn't edit the documents which are hosted in our portal.
How can i apply the license key for office web apps? do i need to execute any power shell commands? please advice.
thanks in advance,
Ammar

thanks Steven for your reply and appreciate the same.
but i need to know where exactly i should pass the licensing value as a parameter or the exact way to apply the license.
when i was searching i found the below link:
http://blogs.msdn.com/b/microsoft_press/archive/2013/02/04/from-the-mvps-installing-office-web-apps.aspx
under licensing it was mentioned like below:
Licensing
So the Office web apps farm is up and running and you have enabled editing. There is though another step before your users will be able to actually edit documents with Office Web Apps; you need to license the users for editing.
This is achieved by running a series of PowerShell commands on the SharePoint 2013 Central Administration server:
Get-SPUserLicense
$x = New-SPUserLicenseMapping -SecurityGroup <ADsecuritygroup> –License OfficeWebAppsEdit
$x | Add-SPUserLicenseMapping
Enable-SPUserLicensing
Is that correct? is anyone executed the above command?
please advice.
thanks in advance,
Ammar

Office 365 instead of Office Web Apps server?

We don't have an Office Web Apps server deployed. We'd really like to share Powerpoints in Lync with the full user experience, but we don't want to install a standalone server just for Office Web Apps since we wouldn't use it for anything else. We
use Office 365, is there a way to use an FQDN from Office 365 and point to that in topology builder as our Office Web Apps server? We area always loading PowerPoint from the cloud anyways. Is there any way to get around installing a stand alone
OWAS server?
Thanks,
Brandon

No as of today I believe that with Lync server 2013 on premise you do need office web app server on premise
Please remember, if you see a post that helped you please click ;Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Office Web Apps server / Lync server 2013

Hi I have installed a Lync 2013 Server and Office Web Apps Server. Configured Lync topology, Office Web Apps farm and certificates.
However when i start the services i get this error message in the log saying Office Web Apps discovery failed.
Event ID: 41033
Description:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
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.
Resolution:
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
Connecting to the HTTPS discovery URL is working fine, and brings up the XML-page (after i click "show all content").
The two servers are located on the same internal network, DNS resolves fine both ways, and no firewall rules blocks any connections between the two. Can anyone please help me figure this out?
Only identical problem found online is here (Invalid Uri syntax for WAC configuration):
http://blogs.technet.com/b/dodeitte/archive/2012/09/10/office-web-apps-server-amp-lync-server-2013.aspx
He resolved the problem by assigning a new OAuthTokenIssuer certificate. This however did not fix the problem in my case.
Regards
Sverre A. Veel

Hi,
In addition, please make sure you have restarted front end and office web apps server after reissuing the certificate.
Kent Huang
TechNet Community Support

Office web Apps server Lync 2013 Certificate

Hi,
I'll be installing Office web app (OWA) server with Lync 2013 std edition. External users access is disabled but federation is enabled, mean OWA will be exposed to internet as wabweb.contoso.com, the interal host name of OWA server is owa.contoso.local
Does the certificate on the on OWA server need to have owa.contoso.local and certificate principle name and wabweb.contoso.com as SAN? or only owa.contoso.local is enough?

It really depends on how you publish the server to the internet. You have some options. If you are publishing this via a reverse proxy, internally you would have a private cert with .local on it and the public name on the reverse proxy. If you are
punching a firewall hole/NAT directly to the server your best option is to use a public cert on that server directly.
That all said, personally I like to make both the internal and external farm URL the same, and use a public cert on the server (if no reverse proxy is in play). So I would actually enter the OWAS Farm as wabweb.contoso.com in topology builder, than
when creating the farm via PowerShell make that both the internal and external URL and get a certificate with a single name on it of wabweb.contoso.com.
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Office Web apps not working

Hi
All of a sudden, the office web apps is not working. I get the below issue
Could not load new WOPI Proof Keys for server XXXXX against Discovery.
Also, i could not see the Office web apps site collection feature. Please suggest.

Please share screenshot of error with ULS log details
All users face same issue?
Check if any application pool on SharePoint server or web app server is stopped?
Try to browse OWA service application. follow below for same:
http://freeit-support.com/2014/09/troubleshoot-sharepoint-service-application-website-issue-from-iis/
Check error in Office web app logs files and event viewer.
If this helped you resolve your issue, please mark it Answered

How can i check the office web app server(wac client) is calling custom WOPI host?

I am getting an error when I testing my wopi host(which is the same as
example) with Office Web app server "Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word."
1-how can find the log files of this error?
2-how can i check the office web app server(wac client) is calling my WOPI host?
I am not sure about cumunication between owa to wopi host. I actually dont know how to implement checkfile and getfile functions to wopi host for waiting for call back from owa client.
Note:I am sure that office web app server is configured true. Because i test it with sharepoint 2013 and editing and viewing is working well.

Hi,
According to your post, my understanding is that
CheckFileInfo is how the WOPI application gets information about the file and the permissions a user has on the file. It should have a URL that looks like this:
HTTP://server/<...>/wopi*/files/<id>?access_token=<token>
While CheckFileInfo provides information about a file, GetFile returns the file itself. It should have a URL that looks like this:
HTTP://server/<...>/wopi*/files/<id>/contents?access_token=<token>
There is a great article for your reference.
http://blogs.msdn.com/b/officedevdocs/archive/2013/03/20/introducing-wopi.aspx
You can also refer to the following article which is about building an Office Web Apps(OWA) WOPI Host.
http://blogs.msdn.com/b/scicoria/archive/2013/07/22/building-an-office-web-apps-owa-wopi-host.aspx
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Office Web Apps - Preview Sharepoint 2010 documents in Sharepoint 2013 Search Results

Hi,
We have a Sharepoint 2013 search site collection. The content sources for the Search service application includes some Sharepoint 2010 sites. We also have Office Web Apps server deployed. When searching for documents, the OWA preview works for all the document
in local sharepoint 2013 farm. However document preview doesn't work for documents in the sharepoint 2010 farm.
Any idea why this happens?
Regards,
Muthu

Could you please elaborate more on open url / please give us some syntax how to use that is display template?
When we use open url do we still need to install office webapps in the 2010 environment?

Opening an embedded document in office web apps

Hi,
I have a test site configured to use office web apps and it works to open documents in OWA. I have a requirement to open a powerpoint presentation embedded in page in office web apps. I used the page viewer web part to do the embedding, but the document
is not opening in office web apps. There is a prompt to open the document in the desktop version of power point. I have checked that the site is configured to open the documents in OWA by default in the site collection features.
Does anybody have a suggestion on how to fix this?
thanks
Sherazad

Hi,
According to your post, my understanding is that you want to embed a PowerPoint document which is opened in office web apps(OWA) in a page.
Here are two solution for your reference:
1.Open the document in OWA, go to File -> Share -> Embed, then copy the Embed Code and add the code into a Content Editor Web Part in the page.
2.Use Page Viewer web part to achieve it, we can get the link from the address bar after the document is opened in OWA. The link like this:
/sites/DennisSite/_layouts/15/WopiFrame.aspx?sourcedoc={D95516CC-6912-4F5B-BF13-C40286BC27A4}&file=Test.pptx&action=default
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

Office Web Apps Error

hi -
I have Office Web Apps 2013 installed and configured on my dev server. It's set to allow HTTP.
When I try to preview a Word document, the frame displays the following message:
This content cannot be displayed in a frame.
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.
According to this
link, low memory conditions can cause this error in the preview. I have checked that and we are OK with memory.
For Excel documents, I get the following error in preview:
The website cannot display the page
Most likely causes:
•The website is under maintenance.
•The website has a programming error.

HI,Seems to be issue with the connection between sharepoint and office webapp.Check the below URL to get the connection successed and work succesfully.
http://expertsharepoint.blogspot.de/2013/12/microsoft-office-web-apps-server-2013_19.html
Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Office Web Apps (OWA) deployment and licensing

Similar Messages

Maybe you are looking for