Case
On a Windows Server (2012R2 or 2016), I want to configure a file share offering a following functionality
- some users,
publishersgroup, have a write access to the share; these users are managing and updating the content on the share - other users,
readersgroup, have a read-only access to the share; they read the content in a frequent or massive scale
The read-only permission is configured correctly on both the share level and the file system level.
Problem
The users from readers group, or namely their application, are able to open the file for reading and lock these files in the same time, preventing them from being overwritten by publishers group.
Is there any way to prevent this behaviour and achieve the desired functionality?