Securing a Common Folder

This article was previously published under Q186496
This article has been archived. It is offered "as is" and will no longer be updated.
Some applications do not have the flexibility for users to specify theirhome directory or some other private directory for saving files. Also, anadministrator may want to use a common directory for related files. Ineither of these cases, the administrator may want to secure the files inthe common directory. For example, if you want to secure a common folder sothat only the user who created a file or administrators can view the file,you can set the NTFS permissions on the common folder to:
   Administrators   Full Control   Creator/Owner    Full Control				
Any files that are created in or copied into the common folder will inheritthe default folder permissions, so that only admininstrators and the ownerof a file can access that file.

In a Terminal Server environment, if only Terminal Server Clients willaccess this common folder, only NTFS permissions need to be set. If thefolder is shared for network access, then the share permissions can be setto:
   Everyone   Full Control				
When both share-level permissions and NTFS permissions are specified for afolder, whichever set of permissions is most restrictive will apply. Inthis case, the NTFS permissions are more restrictive, and a file could onlybe accessed by administrators and the user who created and owns the file.

Article ID: 186496 - Last Review: 11/03/2013 00:25:00 - Revision: 3.0

  • kbnosurvey kbarchive kbinfo KB186496