Re: NTFS Drop Folder - Blocking Owner from changing files
- From: "neo [mvp outlook]" <neo@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 May 2008 15:13:17 -0700
If you are using Creator Owner in the list NTFS ACLS, remove it. Other than
that, we did run into some problems in regards to moving/copying files
between the same UNC path. Needed a patch + registry key from Microsoft to
force the operating system(s) (WinXP/Windows 2003) to recacl NTFS
persmissions. Once these things are in place, its easy to setup a blind
drop directory and use ABE to hide contents if necessary.
So out of curiosity, what operating system are you using and what have you
tried?
/neo
"FB" <FB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8278AAFB-9F39-40F6-93FF-ECF04DC4E742@xxxxxxxxxxxxxxxx
I have a complex Folder Tree with several Files/Folders and the customer
wants to create a proccess where the user puts ("drops") the file in the
folder tree and after that, the file must be innacessible.
Now is working with Write-Only NTFS Permissions on the folder tree
But the owner of the file can modify the file, and i don´t wanna that. I
want a true "drop" folder where once the file is "droped" in the folder,
the
file must be innacessible for the owner too
i´m not talking about FTP, i´m talking about a regular Share/NTFS Folder
Tree
.
- Follow-Ups:
- Re: NTFS Drop Folder - Blocking Owner from changing files
- From: Roger Abell [MVP]
- Re: NTFS Drop Folder - Blocking Owner from changing files
- From: Sebastian G.
- Re: NTFS Drop Folder - Blocking Owner from changing files
- References:
- Prev by Date: Re: Security for Event Viewer
- Next by Date: Re: NTFS Drop Folder - Blocking Owner from changing files
- Previous by thread: NTFS Drop Folder - Blocking Owner from changing files
- Next by thread: Re: NTFS Drop Folder - Blocking Owner from changing files
- Index(es):
Relevant Pages
|