[German]It seems there is a strange issue within Windows Server 2016 and Windows Server 2019. Sometimes NTFS permissions are getting removed for a parent folder, if a subfolder is deleted.
German blog reader Robert R. informed me about this issue, that has been observed on Windows Server 2016 and Windows Server 2019. The issue has been discussed at this Technet forum thread:
NTFS permission removed when deleting a subfolder
I do have a very strange issue with my file server. Let me first describe the infrastructure.
OS: Windows Server 2016
Roles: File and Storage Services
Type: Member of a 2016 Domain
On the file server I do have to following structure/permission:
The NTFS permissions to those folders is like that:
CREATOR OWNER – Full control – Subfolders and files only
SYSTEM – Full control – This folder, subfolders and files
Administrators – Full control – This folder, subfolders and files
L_NTFS_J_R – Read & execute – This folder only
L_NTFS_J_ZZZ_R – Read & execute – This folder only
L_NTFS_J_ZZZ_DIMS_R – Read & execute – This folder, subfolders and files
L_NTFS_J_ZZZ_DIMS_W – Modify – This folder, subfolders and files
L_NTFS_J_ZZZ_Wagenbuch_R – Read & execute – This folder, subfolders and files
L_NTFS_J_ZZZ_Wagenbuch_W – Modify – This folder, subfolders and files
So far I think this is nothing special, now here is my issue:
When I delete the “Wagenbuch” or the “DIMS” folder this does remove the group “L_NTFS_J_ZZZ_R” from the “ZZZ” folder AND does remove the group “L_NTFS_J_R” from the “ANWDTest” folder… and I do have absolutly no idea why this is happening.
Does anyone see an error in the setup or did face similar issues? I am totally lost here, even no idea where to start searching.. Google did also not help at all.
The affected user has published a video demonstrating this issue. Here is a 2nd Technet forum thread discussing this issue. And at reddit.com is also a thread with a broader explanation. After I’ve published the German article, I also received feedback from a user, that one of several Windows Server 2016 shows this behavior. The thread poster wrote, that Microsoft has confirmed this issue and is working on a fix. BTW: Update KB4467684 won’t fix it.