Currently all new folders created on our server
allow "everyone" full control. Consequently we have had a
folder deleted accidentally. I have gone in and changed
the permission to deny "delete subfolder and files", but
everyone can still delete. If I deny "delete" no one can
delete, but they also can't save anything. All I want to
do is to allow administrators to delete and all other
users to be able to write to and save things on the
server, but not delete them. Thanks for any suggestions.

If you do not have Delete permission or Delete Subfolders and files on a file or folder, you can delete it if you are granted Delete Subfolders and Files permissions on the parent folder.

Try not setting it to deny, both Delete Subfolders and Files and Delete permissions, and just leave it unchecked. This needs to be done from the parent folder down. This should allow users to still create folders and files but not delete them.

I have done this also and still am getting the same
results. In some cases it tells the user that the folder
is read-only, though when I check the folder, it is not
marked as such.


>-----Original Message-----
>If you do not have Delete permission or Delete Subfolders
and files on a file or folder, you can delete it if you
are granted Delete Subfolders and Files permissions on the
parent folder.
>
>Try not setting it to deny, both Delete Subfolders and
Files and Delete permissions, and just leave it
unchecked. This needs to be done from the parent folder
down. This should allow users to still create folders and
files but not delete them.
>
>.
>

If this is setup as folder and all subfolders the following permissions:
Administrator-Full -control

Everyone-Read & Execute
-List Folder Contents
-Read
-Write

And set the shared permissions as everyone full-control. Users can read write and execute but will not be able to delete.
This should work as you need it to.


----- (E-Mail Removed) wrote: -----

I have done this also and still am getting the same
results. In some cases it tells the user that the folder
is read-only, though when I check the folder, it is not
marked as such.


>-----Original Message-----
>If you do not have Delete permission or Delete Subfolders
and files on a file or folder, you can delete it if you
are granted Delete Subfolders and Files permissions on the
parent folder.
>>Try not setting it to deny, both Delete Subfolders and
Files and Delete permissions, and just leave it
unchecked. This needs to be done from the parent folder
down. This should allow users to still create folders and
files but not delete them.
>>.
>

The read-only folder is a red herring - it's actually a tri-state checkbox
and when it's grayed out and checked it really means it's in a neutral
state. It also doesn't really set the attribute on the folder. It's only
used to push the attribute down to its child (grandchild, etc.) files.
--
Drew Cooper [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


<(E-Mail Removed)> wrote in message
news:0a8e01c3db73$42b6e3f0$(E-Mail Removed)...
> I have done this also and still am getting the same
> results. In some cases it tells the user that the folder
> is read-only, though when I check the folder, it is not
> marked as such.
>
>
> >-----Original Message-----
> >If you do not have Delete permission or Delete Subfolders
> and files on a file or folder, you can delete it if you
> are granted Delete Subfolders and Files permissions on the
> parent folder.
> >
> >Try not setting it to deny, both Delete Subfolders and
> Files and Delete permissions, and just leave it
> unchecked. This needs to be done from the parent folder
> down. This should allow users to still create folders and
> files but not delete them.
> >
> >.
> >

One other note: "write data" will still allow users to overwrite data in the
file, so there's still a chance for data loss.
--
Drew Cooper [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"fred" <(E-Mail Removed)> wrote in message
news:BE097A53-6178-49B4-983D-(E-Mail Removed)...
> If this is setup as folder and all subfolders the following permissions:
> Administrator-Full -control
>
> Everyone-Read & Execute
> -List Folder Contents
> -Read
> -Write
>
> And set the shared permissions as everyone full-control. Users can read
write and execute but will not be able to delete.
> This should work as you need it to.
>
>
> ----- (E-Mail Removed) wrote: -----
>
> I have done this also and still am getting the same
> results. In some cases it tells the user that the folder
> is read-only, though when I check the folder, it is not
> marked as such.
>
>
> >-----Original Message-----
> >If you do not have Delete permission or Delete Subfolders
> and files on a file or folder, you can delete it if you
> are granted Delete Subfolders and Files permissions on the
> parent folder.
> >>Try not setting it to deny, both Delete Subfolders and
> Files and Delete permissions, and just leave it
> unchecked. This needs to be done from the parent folder
> down. This should allow users to still create folders and
> files but not delete them.
> >>.
> >

Shared permissions are not available, my drive is NTFS.
Any other suggestions???

>-----Original Message-----
>If this is setup as folder and all subfolders the
following permissions:
>Administrator-Full -control
>
>Everyone-Read & Execute
> -List Folder Contents
> -Read
> -Write
>
>And set the shared permissions as everyone full-control.
Users can read write and execute but will not be able to
delete.
>This should work as you need it to.
>
>
> ----- (E-Mail Removed) wrote: ----
-
>
> I have done this also and still am getting the same
> results. In some cases it tells the user that the
folder
> is read-only, though when I check the folder, it is
not
> marked as such.
>
>
> >-----Original Message-----
> >If you do not have Delete permission or Delete
Subfolders
> and files on a file or folder, you can delete it if
you
> are granted Delete Subfolders and Files permissions
on the
> parent folder.
> >>Try not setting it to deny, both Delete Subfolders
and
> Files and Delete permissions, and just leave it
> unchecked. This needs to be done from the parent
folder
> down. This should allow users to still create
folders and
> files but not delete them.
> >>.
> >
>.
>