Re: Protecting folder-structure against accidental alteration

Changing permissions has undesirable side-effects such as
making the creation or editing of documents impossible

Not so.
If in the NTFS permissions dialog you click Advanced, and
then you highlight a grant and click edit, then you will see that
there is a dropbox allowing to specify to what the specific
grant applies.
In your case, you would be wanting to distinguish between
grants for This folder and subfolders and for Files only.
If you do not grant delete on folders they will not get deleted,
etc.

Roger

"Ian" <Ian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7AE81634-8747-428A-8850-26F623411CDE@xxxxxxxxxxxxxxxx
We have a large data structure containing documents in hierarchical
folders.
They are mainly used by speed-typists who don't always look at the screen
whilst typing, so they are not always aware when something is going
horribly
wrong.

One of the biggest problems is that of folders being accidentally moved or
renamed from within File..Open dialog boxes of applications, when the
user's
actual intention is to find and open a document. As we all know this is
oh-so easy to do - all it takes is a slip of the mouse, or a slightly slow
double-click when opening a folder. As there is no confimation asked,
often
the user isn't even aware it's happened.

By looking at the nature of the damage I'd guess that slow-click is the
main
culprit- the users habitually type the name of a folder to navigate to it
in
the list, BUT if a folder has been unintentionally slow-clicked instead of
double-clicked, then it gets renamed instead.

We need some kind of protective measure, as the the data is suffering
gradual 'entropy' from the accumulation of mouse-slips by people who
aren't
even trying to make changes to it at the time!

I was looking for ways of either turning off move/rename from within
dialog-boxes (especially the slow-click variety of rename) or else of
using
NTFS permissions to stop renaming of the root folders in the structure.
Neither seem to be very feasible, though. Changing permissions has
undesirable side-effects such as making the creation or editing of
documents
impossible, while there seems to be no registry or policy control for the
slow-click action that does most of the damage.

Mostly XP Pro desktops, NT4 server.

Any ideas?



.

Relevant Pages

  • Re: Files and Folders
    ... If you drill into the Advanced dialog in the NTFS permissions ... You would want a modify grant that applies to ... that applies to This folder and subfolders, or even to This folder, ...
    (microsoft.public.windows.server.security)
  • Re: controlling deleting of files with NTFS
    ... Hence when on this dir you deny delete to a group, ... grant delete to a user that is in the denied group, ... have (i.e. remove delete in the advanced view in the NTFS permissions ... On the top most folder I am trying to set the ntfs security on, ...
    (microsoft.public.security)
  • Re: Prohibit renaming of folder
    ... When in the NTFS permissions dialog you would grant ... List for the folder, and grant modify on the content of the ...
    (microsoft.public.win2000.security)
  • Re: Block AOL Inst. Messenger???
    ... and usb ports are disabled in cmos if they are not needed. ... installed The other main thing to do is to tighten up ntfs permissions. ... Other folders added to the root folder since installation should probably ...
    (microsoft.public.win2000.security)
  • Re: Creating "Home" dirs via script
    ... But share access is only half the story; what NTFS permissions ... This script can be "wrapped" in another to create MANY home folders at ... If doesFolderExist = 0 then 'If Folder does not exist, ... Set ace = CreateObject ...
    (microsoft.public.windows.server.scripting)