Re: Trouble Assigning Folder Permissions

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 09/04/04


Date: Sat, 4 Sep 2004 11:45:53 -0400

Tom E. Pinkerton wrote:
> Friends,
>
> I'm relatively new to Windows Server 2003, and obviously
> there is a big piece of the security picture that I am
> missing. :-)
>
> At the school where I work, we have Windows Server 2003
> Standard running our internal network. On that server, I
> have a shared folder called "Apps" where I am storing the
> student-accessible applications and related files that are
> made available to them over the network. Within that apps
> folder, there is a folder called "KBPRO" for our
> Keyboarding Pro software, and under that a folder
> called "Students" where all student performance data is
> stored.

In Win2003, share permissions are everyone=read only by default. Change this
to Full Control for each share.

Personally, for your setup, I'd set them all up as separate folders at the
same level - and then set up the shares and NTFS permissions appropriately.

For example:
D:\APPS shared as APPS (or APPS$ for a hidden share)....NTFS permissions=
administrators & system=full control, users=whatever they need

D:\ KBPRO shared as KBPRO (or with the $) - same thing for NTFS permissions

D:\STUDENTS shared as STUDENTS/$ - administrators/system=full control,
users=modify

Then use a login script to map drives to these shares -

net use x: \\server\share /persistent:no

The advantage of hidden shares is that nobody can browse them.

>
> In order for the software to work properly, student
> accounts need to have full read/write access to
> the "Students" folder and everything under it.
> Unfortunately, regardless of how I try to set the
> appropriate security permissions, everyone except
> administrators receives an "access denied" error message
> when they attempt to write to the folder, or any folder on
> the network for that matter. They can read the folders
> just fine, but they can't write to them.
>
> I have tried assigning "Full Control" permissions for
> the "Students" folder to the Users group, to the Domain
> Users group, to the Everyone group, to the Students group
> that all students are members of, and even to an
> individual user account. None of these had any effect. As
> a test, I even tried giving the Everyone group "Full
> Control" access to the entire data partition. Even that
> did not allow anyone to write to any folder on that drive.
>
> Does anyone have any thoughts on what I might be missing
> here?
>
> Thanks!
>
> =Tom=



Relevant Pages

  • Re: Folder Permissions
    ... The issue of folder permissions is not clear to me at all. ... The expensive book I bought on Windows Server 2003 seems ... Inheritence for the subfolder's subfolders ...
    (microsoft.public.windows.server.general)
  • Re: Folder Permissions
    ... The issue of folder permissions is not clear to me at all. ... The expensive book I bought on Windows Server 2003 seems ... Inheritence for the subfolder's subfolders *is* enabled, so any NTFS permissions on share1 will exist on any subfolder/files therein. ...
    (microsoft.public.windows.server.general)
  • Re: folder permissions in a lab
    ... >is there a way th configure folder permissions on a network share so the word ... Make sure the accountused by the students do NOT have ... Right-click the folder, select Sharing & Security, and go to the ... the student group and click the Edit button. ...
    (microsoft.public.word.docmanagement)
  • Re: Limiting Limited Access Accounts.
    ... Go to properties/security/advanced and remove the permissions ... Create a local group and name it students. ... permissions on any program folder or stand alone executable you do not want ...
    (microsoft.public.windowsxp.security_admin)
  • Re: password a folder??
    ... That definitely needs to be done using permissions at server level: ... student's data folder password protected so that students couldn't open ... :> You were never able to password protect folders from Word! ...
    (microsoft.public.word.newusers)