Here I have a folder (E:\projects, which is also shared via the network) with several hundred folders like E:\projects\project1, E:\projects\project2, E:\projects\project3.... Each of these folders contains several subfolders and files. Currently all users have full permissions on all files and folders.
I want to change it so that the folder level of e.g. E:\projects\project1 must not be deleted. The users shouldn't be allowed to delete the folder E:\projects\project1, but they should be able to do what they want with its content.
Currently I'm failing to express this to Windows' permission system. When I'm in E:\projects and deny the permission "delete" for subfolders, it does this recursively. But this is exactly what I don't want to have. Only the folder structure exactly one level below E:\projects should get this.
Does anyone have a hint for this?
In response to Thecleaner:
I'm afraid this doesn't work as intended. The user is still able to delete this folder. Currently I'm trying this solution: granting the user group the permission to "traverse folder/execute file", "list folder/read data", "read attributes", "read extended attributes" and "read permissions" - only for this folder. "Delete" and "delete subfolders and files" is denied for this group. Then I added another permission for this group which gives full access only for subfolders and files. This results in the behaviour that the users can still move the folder E:\projects\project1 to another place. But why? I don't get it...
The user is a member of the following groups in the AD:
Domänen-Benutzer, Entwicklung, EAGLE, mup_com, archive, projecte, CPUWIN_mup, MP, Remote Web Workplace Users, Benutzer von Windows SBS-Remotewebzugriff, Windows SBS-Faxbenutzer, Konten für die Windows SBS-Ordnerumleitung, All Users, Windows SBS-Linkbenutzer