Timeline for Error when opening in browser some ext (.docx, .docm, .xlsx, .pptx) using Office Online Server on-prem linked with SharePoint 2016 on-prem
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2018 at 15:58 | comment | added | Andy Dawson | As for the number of CALs, you should (of course) have the correct number of CALs of the correct type available for your users. Microsoft reserve the right to audit you for license compliance at any point. A lack of CALs does not stop a user being given access to SharePoint and using it, however It's up to you to ensure you're in compliance. | |
| Oct 10, 2018 at 15:57 | comment | added | Andy Dawson | You can use whatever group you have available that is suitable for your purposes. If you have an 'all company staff' group that contains all of the users that you need to apply this to, then use that. I used 'domain users' in my example as that was a convenient group that contained all of the users in the organisation. | |
| Oct 10, 2018 at 14:36 | comment | added | MLC | 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? | |
| Sep 28, 2018 at 11:26 | comment | added | Andy Dawson | 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. | |
| Sep 27, 2018 at 17:54 | comment | added | MLC | 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? | |
| Sep 27, 2018 at 15:30 | comment | added | Andy Dawson | 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. | |
| Sep 25, 2018 at 20:51 | comment | added | MLC | 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? | |
| Sep 25, 2018 at 16:25 | history | answered | Andy Dawson | CC BY-SA 4.0 |