2

A customer has a farm with multiple web apps, one of which is accessible anonymously. Office Web Apps is installed on the farm. On the anonymous site, Word documents open in the browser viewer, but the 'Open in Word' button is disabled. In addition, there is no Send to -> Download option on the library items. The customer would like the default behavior on the anonymous site to be similar to any other website: Word documents are downloaded where the user may open them locally. Is it possible to disable Office Web Apps for this web application or site collection only?

Note we have disabled the OWA site collection feature, and experimented with variations of that and 'OpenInClient' but Word documents still open in OWA for anonymous users, regardless of any setting on those two.

Improve this question
7
  • I don't know the answer, but maybe you should disable OWA until this is sorted due to licences. Afaik every user that uses OWA needs to have an Office licence, if not MS might not be to happy about this setup :)
    – Anders Aune
    Feb 17, 2012 at 20:10
  • By "disable the OWA site collection feature" do you mean the Open Documents in Client Applications by Default feature?
    – David Lozzi
    Feb 17, 2012 at 20:57
  • Had the same problem, even after deactivating the OWA feature and enabling the openinclient feature, OWA was still the default. PS, licensing is not really a problem, anyone who owns an Office license gets an OWA license with it. So if you have Office on your own computer, technically you are allowed to use OWA too :-D
    – Colin
    Feb 18, 2012 at 2:44
  • Yeah, everyone that has Office, but how can you guarantee this when its anonymous access? Probably it wont be an issue, companies usually sorts it out before MS comes on a visit for counting.
    – Anders Aune
    Feb 19, 2012 at 1:22
  • 1
    "anyone who owns an Office license gets an OWA license with it" If you read the license terms, I believe it's anyone with an "Enterprise" Office license gets an OWA license. Not all Office licenses are created equal.
    – webdes03
    May 24, 2012 at 0:25

3 Answers 3

Reset to default
1

I did test this the other day, I had to run a PowerShell-script to get it deactivated right. 

$webAppsFeatureId = $(Get-SPFeature -limit all | where {$_.displayname -eq "OfficeWebApps"}).Id 
$singleSiteCollection = Get-SPSite -Identity http://<site_name> 
Disable-SPFeature $webAppsFeatureId -Url $singleSiteCollection.URL

It did throw an error when I first tried to deactivate from the GUI. You could try this, not sure if it will work in your case.

Improve this answer
2
  • This will deactivate the feature, but in some cases, Office Web Apps will still attempt to display the document even with the feature disabled. Specifically if SP is unable to use client integration- as in anonymous sites and non IE browsers.
    – Daniel
    Mar 20, 2012 at 17:58
  • This script appears on a TechNet page, I'm not sure which is the original source ;) technet.microsoft.com/en-us/library/ee837418(v=office.14).aspx
    – shufler
    Nov 12, 2014 at 23:13
0

From the site collection perspective, you can disable the Office Web Apps Feature. This will disable the functionality for the site collection.

Improve this answer
1
  • 2
    That's essentially what the powershell script Anders provided does. But, as noted there, even with that feature disabled, documents can open in the browser. This is especially a problem in anonymous sites or with non-ie browsers where SharePoint cannot detect Office.
    – Daniel
    Jul 2, 2012 at 14:37
0

I have the same issue with Custom List attachments. Setting the feature OpenInClient on only makes IE to open documents in local application, but Chrome still tries to open WOPI pages.

I fixed this issue by using javascript (In the list item view form -> Edit Page -> Edit Webpart -> JS Link) to remove the attachment links' onmousemouse and onclick so it does not redirects to WOPI server:

var attachmentTable = document.getElementById('idAttachmentsTable');
      jQuery('tr a', attachmentTable).each(function(index, ele: HTMLAnchorElement) {
        ele.removeAttribute('onmousedown');
        ele.removeAttribute('onclick');
      });
Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.