New answers tagged file-server
It was not the users were not able to delete their files, but they were not able to send those files to the Recycle Bin! From the perspective of the FSRM, the users were trying to MOVE files from one location to another, WRITING them in a location which was forbidden, not allowing that. Actually deleting the files (caps+delete) works flawless.
In order to create a true “shared-nothing” failover file server you can use a free Starwind solution https://www.starwindsoftware.com/starwind-virtual-san-free. Basically it can do the same that Windows Server 2016 will do later but unfortunately only in the Datacenter edition. Starwind can do it already even with a free Hyper-V 2012 server ...
Because this is only a testing environment have you considered creating several shared VHDX disks and using them to create a Clustered Storage Space? that way you can add more disks to the storage space to increase capacity as needed.
Apparently you can take the shared VHDX offline (the shares will be unavailable), either by shutting down the clustered guests or by unmounting it, and then change the size of the VHDX and then bring it back online (or boot the guests). A few web searches have turned up people writing and agreeing that that's the only way to do it. There's one such ...
I have experienced a similar problems two months ago, this thread may be helpful to you. I would first check if this happens for all files or only files that are owned by the user (change the owner to see if it still persists), as suggested by Daniel. I would then try to set the permissions as described in the other thread, but using the detailed ...
Top 50 recent answers are included