Jump to content

Windows file Permissions


Recommended Posts

Guest mathhewj@hotmail.com
Posted

We are running Windows Server 2000 (SP4) for file sharing, and have

come across a problem with permissions.

 

If I create a folder (Test_Folder) on the server and assign a group

(Write_Group) with the following permissions to the folder:

 

List Folder Contents

Read

Write

 

And then using the Advanced button to Apply these permissions via the

method "This Folder Only".

 

Next we have a few files that are in the Test_Folder, but I only want

members of the Write_Group to be able to write to one of the files

(notes.txt). So I assign the Group (Write_Group) with the following

permissions on the file notes.txt:

 

Modify

Read & Execute

Read

Write

 

This should allow the members of Write_Group to edit and change the

file notes.txt under the Test_Folder, but not to be able to edit or

change the other files in the Test_Folder. However it doesn't, the

users in the Write_Group can rename the notes.txt file. But opening

this in word and making changes it will not allow the document to be

saved stating that the folder does not have write permissions!

 

If I then change the method the permissions are applied to the

Test_Folder to "This Folder and Files" (keeping the same permissions

set), then the users in the Write_Group can save changes to the file,

but they can then also make changes to the other files in the

Test_Folder.

 

Can anyone shed some light on what maybe causing this?

 

Cheers.

  • Replies 3
  • Created
  • Last Reply

Popular Days

Guest SBS Rocker
Posted

Re: Windows file Permissions

 

What a big hassle to try to apply permissions to individual files within the

same folder. Create another folder and move the file you want to allow

modify permissions to. Then create two security groups. Call it something

like Test-folder Users-M for modify and Test_Folder Users-RW.

 

 

 

<mathhewj@hotmail.com> wrote in message

news:0dc169da-414e-4578-ab5f-e50ebf26db55@e4g2000hsg.googlegroups.com...

> We are running Windows Server 2000 (SP4) for file sharing, and have

> come across a problem with permissions.

>

> If I create a folder (Test_Folder) on the server and assign a group

> (Write_Group) with the following permissions to the folder:

>

> List Folder Contents

> Read

> Write

>

> And then using the Advanced button to Apply these permissions via the

> method "This Folder Only".

>

> Next we have a few files that are in the Test_Folder, but I only want

> members of the Write_Group to be able to write to one of the files

> (notes.txt). So I assign the Group (Write_Group) with the following

> permissions on the file notes.txt:

>

> Modify

> Read & Execute

> Read

> Write

>

> This should allow the members of Write_Group to edit and change the

> file notes.txt under the Test_Folder, but not to be able to edit or

> change the other files in the Test_Folder. However it doesn't, the

> users in the Write_Group can rename the notes.txt file. But opening

> this in word and making changes it will not allow the document to be

> saved stating that the folder does not have write permissions!

>

> If I then change the method the permissions are applied to the

> Test_Folder to "This Folder and Files" (keeping the same permissions

> set), then the users in the Write_Group can save changes to the file,

> but they can then also make changes to the other files in the

> Test_Folder.

>

> Can anyone shed some light on what maybe causing this?

>

> Cheers.

Guest mathhewj@hotmail.com
Posted

Re: Windows file Permissions

 

On 4 Dec, 16:37, "SBS Rocker" <nore...@NoDomain.com> wrote:

> What a big hassle to try to apply permissions to individual files within the

> same folder. Create another folder and move the file you want to allow

> modify permissions to. Then create two security groups. Call it something

> like Test-folder Users-M for modify and Test_Folder Users-RW.

>

> <mathh...@hotmail.com> wrote in message

>

> news:0dc169da-414e-4578-ab5f-e50ebf26db55@e4g2000hsg.googlegroups.com...

>

>

>

> > We are running Windows Server 2000 (SP4) for file sharing, and have

> > come across a problem with permissions.

>

> > If I create a folder (Test_Folder) on the server and assign a group

> > (Write_Group) with the following permissions to the folder:

>

> > List Folder Contents

> > Read

> > Write

>

> > And then using the Advanced button to Apply these permissions via the

> > method "This Folder Only".

>

> > Next we have a few files that are in the Test_Folder, but I only want

> > members of the Write_Group to be able to write to one of the files

> > (notes.txt). So I assign the Group (Write_Group) with the following

> > permissions on the file notes.txt:

>

> > Modify

> > Read & Execute

> > Read

> > Write

>

> > This should allow the members of Write_Group to edit and change the

> > file notes.txt under the Test_Folder, but not to be able to edit or

> > change the other files in the Test_Folder. However it doesn't, the

> > users in the Write_Group can rename the notes.txt file. But opening

> > this in word and making changes it will not allow the document to be

> > saved stating that the folder does not have write permissions!

>

> > If I then change the method the permissions are applied to the

> > Test_Folder to "This Folder and Files" (keeping the same permissions

> > set), then the users in the Write_Group can save changes to the file,

> > but they can then also make changes to the other files in the

> > Test_Folder.

>

> > Can anyone shed some light on what maybe causing this?

>

> > Cheers.- Hide quoted text -

>

> - Show quoted text -

 

Yes it would work in the way you described. I didn't really want to

have to create a new folder just for one file. This will probably come

up again on various folder/files, and then I will be creating more

folders just holding one or two files creating a messy folder

structure.

 

It may seem like nit picking but I would of thought that the NTFS

permissions would of worked as described, as the user should have all

the permissions they need. Is this a design feature of NTFS

permissions? Or a bug?

Guest SBS Rocker
Posted

Re: Windows file Permissions

 

Well if you really undertand how NTFS work and how to apply them then you

can see how this is going to create kaos and more work. What happens when

you have say three groups of 2 or 3 people each who need different access to

10 of the 50 files you have in one folder? Or how when a new employee comes

on board and your boss tells you they need the same access as Joe Blow and

Joe Punk? How are you going to know where to grant this new person access?

You just can't copy one of the joe's profile because they are not in groups

where they have been granted access to. If they belonged to groups the the

new employee will be a member of the same groups if you copy a profile or

you can just look at joe Blow's profile and see what groups he belongs to.

Also when Joe Blow leaves and you decide to delete his account they when you

view permissions it will not remove them but will leave all that SID garbage

information. yu also can't use inheritance so each and every file needs to

be manually applied ntfs permissions. So many other reasons I can get into

as to why but I guess you have your own way. Good luck.

 

And you won't run into the issues you are having now. Reread your post. here

is your problem. And sorry I don't have thje time to get into a longer

discussion as to why.

"And then using the Advanced button to Apply these permissions via the

method "This Folder Only".

 

<mathhewj@hotmail.com> wrote in message

news:e629c0e1-f9a4-4558-ae54-0c72cb9e40a4@o42g2000hsc.googlegroups.com...

> On 4 Dec, 16:37, "SBS Rocker" <nore...@NoDomain.com> wrote:

>> What a big hassle to try to apply permissions to individual files within

>> the

>> same folder. Create another folder and move the file you want to allow

>> modify permissions to. Then create two security groups. Call it something

>> like Test-folder Users-M for modify and Test_Folder Users-RW.

>>

>> <mathh...@hotmail.com> wrote in message

>>

>> news:0dc169da-414e-4578-ab5f-e50ebf26db55@e4g2000hsg.googlegroups.com...

>>

>>

>>

>> > We are running Windows Server 2000 (SP4) for file sharing, and have

>> > come across a problem with permissions.

>>

>> > If I create a folder (Test_Folder) on the server and assign a group

>> > (Write_Group) with the following permissions to the folder:

>>

>> > List Folder Contents

>> > Read

>> > Write

>>

>> >

>>

>> > Next we have a few files that are in the Test_Folder, but I only want

>> > members of the Write_Group to be able to write to one of the files

>> > (notes.txt). So I assign the Group (Write_Group) with the following

>> > permissions on the file notes.txt:

>>

>> > Modify

>> > Read & Execute

>> > Read

>> > Write

>>

>> > This should allow the members of Write_Group to edit and change the

>> > file notes.txt under the Test_Folder, but not to be able to edit or

>> > change the other files in the Test_Folder. However it doesn't, the

>> > users in the Write_Group can rename the notes.txt file. But opening

>> > this in word and making changes it will not allow the document to be

>> > saved stating that the folder does not have write permissions!

>>

>> > If I then change the method the permissions are applied to the

>> > Test_Folder to "This Folder and Files" (keeping the same permissions

>> > set), then the users in the Write_Group can save changes to the file,

>> > but they can then also make changes to the other files in the

>> > Test_Folder.

>>

>> > Can anyone shed some light on what maybe causing this?

>>

>> > Cheers.- Hide quoted text -

>>

>> - Show quoted text -

>

> Yes it would work in the way you described. I didn't really want to

> have to create a new folder just for one file. This will probably come

> up again on various folder/files, and then I will be creating more

> folders just holding one or two files creating a messy folder

> structure.

>

> It may seem like nit picking but I would of thought that the NTFS

> permissions would of worked as described, as the user should have all

> the permissions they need. Is this a design feature of NTFS

> permissions? Or a bug?


×
×
  • Create New...