How to automatically inherit permission entries on child objects?

[Synapse Syndrome]

I am using Send To to copy files to a folder on another machine, but the
permissions are not being inherited from the parent folder at the
destination. I never really understood how NTFS file permissions get
inherited without dooing it manually on whoel folders at a time. Any
pointers?

Cheers

ss.

 

[Rick \Nutcase\ Rogers]

Hi,

Right click the parent folder, choose properties. On the security tab click
the advanced options. The option to inherit permissions is on the first
(permissions) tab.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Synapse Syndrome]

Hi,

Right click the parent folder, choose properties. On the security tab
click the advanced options. The option to inherit permissions is on the
first (permissions) tab.

Yes thanks, I know that, but that's what I was referring to when I meant
doing it manually. When new files are Sent To this folder they do not
inherit the permissions until I do this operation, and I was wondering how I
to make the entries automatically descend to all child objects.

ss.

 

[Synapse Syndrome]

Yes thanks, I know that, but that's what I was referring to when I meant
doing it manually. When new files are Sent To this folder they do not
inherit the permissions until I do this operation, and I was wondering how
I to make the entries automatically descend to all child objects.

I think this has got something with Audit Policies possibly? I'm not sure
how to copy the permission entries from the Permissions tab to the Auditing
tab, if that is what's required here.

ss.

 

[Roger Abell [MVP]]

You may now be going down the wrong avenue. The auditing and the
permissions settings are separate (the SACL and DACL respectively).
What you are dealing with is the way things happen when a file is
moved to a new location, i.e. inherited permissions may not be seen
immediately on the result. For this reason I often avoid anything that
may be doing a move and instead use a copy and when needed this
is followed by a delete of the original.

 

[Synapse Syndrome]

You may now be going down the wrong avenue. The auditing and the
permissions settings are separate (the SACL and DACL respectively).
What you are dealing with is the way things happen when a file is
moved to a new location, i.e. inherited permissions may not be seen
immediately on the result. For this reason I often avoid anything that
may be doing a move and instead use a copy and when needed this
is followed by a delete of the original.

When I am using Send To, the files *are* being copied though. The
destination is another drive on another computer. They are actually going
to an IIS website folder, but they can't be viewed on the web until the
anonymous web use account is added to the file permissions.

But I would normally be using a copy command rather than a move normally for
any other files on my network, as that would screw up the created and
modified dates which would leave everything in a complete mess to navigate.

ss.

 

[Synapse Syndrome]

When I am using Send To, the files *are* being copied though. The
destination is another drive on another computer. They are actually going
to an IIS website folder, but they can't be viewed on the web until the
anonymous web use account is added to the file permissions.

But I would normally be using a copy command rather than a move normally
for any other files on my network, as that would screw up the created and
modified dates which would leave everything in a complete mess to
navigate.

I should have said that it screws up the Created date only, not Modified.

But I find it hard to believe that NTFS security permission can't be
automatically enforced on any new child objects. There must be a way to do
this?

ss.

 

[Roger Abell [MVP]]

I should have said that it screws up the Created date only, not Modified.

But I find it hard to believe that NTFS security permission can't be
automatically enforced on any new child objects. There must be a way to
do this?

The only way I have found is with manual intervention.
It is not often that the inherited permissions do not show but when
this does happen one needs to trigger (an artificial and then reversed)
change in the ACL up at the inheritance root.