NTFS permissions

[kv102t]

I'm sure this could be done.

 

I have one folder, I wish students to be able to read/write/delete their own files but not another students in the same folder.

The folder is empty until used by a student.

 

I was thinking you had to use CREATOR OWNER, SELF or something in the permissions.

I have given all students base level Traverse folder & List Folder access.

 

I just can't get them to create a file with only their permission.

 

 

Any thoughts?

 

Many Thanks

Kyle.

[sister_annex]

I think it may just be the case of giving Creator Owner modify (which will allow them to read/write/delete a file that is already there) and give the student group the base level (what you have already) and create files/ folders - this should allow them to create the initial file and then as creator owner they will permission to do everything else

 

HTH

[kv102t]

This is what I thought, it just dosn't seem to work.

[kv102t]

I don't think the CREATE OWNER does what it sound like. I was doing some reading and it's normally used in AD for controlling objects.

[sister_annex]

OOPS my bad - I'll have another think

[Guest Guest]

Its basically the same as when you set up folder redirection. Follow this guide (minus the share permissions and redirection buit) but add any extra permission you may need.

 

Best Practice: Roaming Profiles and Folder Redirection (a.k.a. User State Virtualization)

[kv102t]

The reason this link works is when you are in AD and add the user, AD will create the home folder for the user. This folder is given the permission of the account created. This cannot be done in this scenario.

[Guest Guest]

The reason this link works is when you are in AD and add the user, AD will create the home folder for the user. This folder is given the permission of the account created. This cannot be done in this scenario.

 

All you do is on the root folder remove append and delete rights from the pupils security group. They can then create as many files as they like and as creator owner they can modify and delete them, but they can't modify or delete anyone elses.

Edited March 2, 2012 by Guest

[kv102t]

Thanks for the info, I will try this today.

[sted]

creator owner will work IF the folders exist and are created by the user (or they are assigned as the owner) creator owner cant create files in a new share as say fred/john/dave isnt the creator owner. If you add pupils group the permission for THIS FOLDER ONLY to create folders you should be ok

[kv102t]

i wanted to avoid the creating folder for each. If i did this then you wouldn't need create owner as their permission would give them all the security they need.

[kv102t]

All you do is on the root folder remove append and delete rights from the pupils security group. They can then create as many files as they like and as creator owner they can modify and delete them, but they can't modify or delete anyone elses.

 

This was the bit that make it work.

 

All working now, thanks for everyones help.