> Well, being a MCSE does not mean I know everything

or that colaberation
> with others is not a useful and efficient means for solving a problem. It
> is
I know (and agree) ... I was just joshing with ya :-)) There are many naive
users here; with (ahem) naive questions. So it's a pleasure to get an
interesting question, from a skilled user.
> The problem with granting read-only access is that I am part of other
> groups
> that have more access - such as Authenticated users and Users. Since
> granted
> permissions combine, that still does not protect my files.
It might take a bit of tweaking to find the right combination of
permissions. The original question was "is there an ACL editor?" and I
answered: Yes, icacls. But as to how you would actually *use* icacls - well,
that is left as an exercise for the reader :-)
Often it would be sufficient just to not grant the Delete right, without
necessarily specifically Denying it. But note that, if users don't have the
Delete permission on a file, they can still delete it,if they have the
Delete Subfolders And Files permission on the parent directory. On the whole
I suspect you're going to haveto kill inheritance from the parent directory.
My personal preference is to avoid Denying rights unless
absolutelnecessary - denied rights tend to cause many weird and unexpected
permissions errors (in my experience). Better just to not grant the right.
An alternative to icacls is SubinACL:
http://www.microsoft.com/downloads/d...displaylang=en
It's pretty similar, but -
- can configure ACLs on many types of object, besides just file system; and
- has some better handling for SDDL strings (see
http://www.microsoft.com/technet/com...mt/sm1105.mspx)
Good luck with it,
--
Andrew McLaren
amclar (at) optusnet dot com dot au