Skip to main content
SharePoint

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • Thank you for your answer, but what's the relationship between enforcing an enterprise license for every domain user and the issue that I am having for some of the Office extensions that can not be viewed in browser? Commented Sep 25, 2018 at 20:51
  • The error you're getting is that the current user is attempting to open the document concerned in edit mode rather than read-only mode specified by the EditingEnabled:False parameter during OOS configuration. The SharePoint licensing tells SharePoint not to attempt to open the document in edit mode in OOS, but to open it in read-only mode only instead as all domain users (in my example) now do not have a license to edit documents in OOS. Commented Sep 27, 2018 at 15:30
  • Do you know if Microsoft has published any article with all the steps you have to follow when you want to disable editing with OOS in SharePoint 2016? Commented Sep 27, 2018 at 17:54
  • In short, no, however when I needed to create the same config for a customer, I put the requirements together from a number of blog posts, including wictorwilen.se/… and sharepointeurope.com/… . The commands that I listed in my answer are the ones we used to configure their farm. Commented Sep 28, 2018 at 11:26
  • It is my understanding that to implement your solution I will need to have "Domain Users" as the only container being synchronized with SharePoint, correct? And also for licensing enforcement I will have to match the # of CALS to the # of users that are in that security group, right? Commented Oct 10, 2018 at 14:36