J
Jay
Guest
I have a folder containing several thousand files. Its Security
configuration is set to 'Allow inheritable permissions from parent to
propagate to this object and all child objects', and in fact all its
Permissions boxes are greyed out because it's inheriting them from its
(great-grand) parent. Most of the files created in this folder therefore
inherit permissions properly, but there are a tiny number that don't and are
causing me grief. In these cases, what happens is that the user copies a
file out from this folder to a temp folder on the desktop of the same
computer to do some work on it. By being placed in a folder on the desktop,
the file's Security settings are correctly changed to those inherited from
the Desktop because its 'Allow inheritable permissions' box is still set on.
The problem occurs when the file is then moved or copied from the desktop
back into the original folder either by dragging and dropping in Windows
Explorer or by using 'copy' or 'move' from the command line, when its
'Allow inheritable permissions' box is set off and it then exists with an
incomplete set of access permissions.
Can anybody explain why the file should lose its 'Allow inheritable
permissions' setting like this? My understanding was that If 'Allow
inheritable permissions' is set on for a folder, then any child object
created in that folder defaults to inheriting its permissions unless the
flag is specifically overridden and set off for an object, but that's
obviously and demonstrably incorrect.
Jacques
configuration is set to 'Allow inheritable permissions from parent to
propagate to this object and all child objects', and in fact all its
Permissions boxes are greyed out because it's inheriting them from its
(great-grand) parent. Most of the files created in this folder therefore
inherit permissions properly, but there are a tiny number that don't and are
causing me grief. In these cases, what happens is that the user copies a
file out from this folder to a temp folder on the desktop of the same
computer to do some work on it. By being placed in a folder on the desktop,
the file's Security settings are correctly changed to those inherited from
the Desktop because its 'Allow inheritable permissions' box is still set on.
The problem occurs when the file is then moved or copied from the desktop
back into the original folder either by dragging and dropping in Windows
Explorer or by using 'copy' or 'move' from the command line, when its
'Allow inheritable permissions' box is set off and it then exists with an
incomplete set of access permissions.
Can anybody explain why the file should lose its 'Allow inheritable
permissions' setting like this? My understanding was that If 'Allow
inheritable permissions' is set on for a folder, then any child object
created in that folder defaults to inheriting its permissions unless the
flag is specifically overridden and set off for an object, but that's
obviously and demonstrably incorrect.
Jacques