I read a lot about strange and unexpected behavior about acl inheritance when folders are moved inside the same volume.
I have a problem similar to this one:
microsoft-move-file-acl-problem
In my case only a user is affected and any effort to reproduce the problem with another user on other folders with similar acls was vain.
My setup:
Windows server 2016 with shared folders
Windows 10 client accessing the folders
\myserver\myshare\bossfolder\restricted has limited access and only the boss has full control
\myserver\myshare\bossfolder\toProcess has limited access to the boss (full control) and another windows group
When the boss moves folders with files from restricted to toProcess these folders don't inherit the acl from toProcess, so the users in the group cannot work there.
This behavior is the same described in the linked post but it is almost 5 years old and I'm very surprised it is not solved.
Besides, as stated above, any effort to reproduce the problem with other users on other folders (setting the acl accordingly) was useless.
It seems I'm missing something…
Best Answer
After investigations and tests here are the results.
The share permission was Modify. Comparing with other shares on other servers where security permissions were inherited after file and folder move I put share permission to Full.
Now when my test user moves folders within the share from his client computer the security permissions of the destination folder are applied.