11

Case

On a Windows Server (2012R2 or 2016), I want to configure a file share offering a following functionality

  • some users, publishers group, have a write access to the share; these users are managing and updating the content on the share
  • other users, readers group, 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?

Michał Sacharewicz
  • 549
  • 8
  • 25
  • If you are connecting mac to the windows file share, here is one possible solution: https://www.acronis.com/en-us/mobility/mac-windows-compatibility/ – I'm Root James Mar 01 '19 at 18:52
  • I am using exactly this feature with one specific file - it is updated by a script, and even if a user has this file opened, the script can overwrite it, since the user has only read access to the file. Did you check the permissions on the files inside the folder? Maybe the permissions are not inherited correctly. – Tobias Nov 06 '19 at 15:08

1 Answers1

0

Can you see the open files via net files on the server?

If so, you could try using net file <ID> /close.

I would also try replacing an open file via copy /Y, that way our could check if only the publishers application behaves like this.

Robert
  • 93
  • 1
  • 3
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Dec 31 '21 at 17:44
  • There is no "publisher application" involved, just a pure file overwrite. Closing file connections won't solve the issue as clients are rapidly reconnecting to the files. – Michał Sacharewicz Jan 03 '22 at 19:22