Re: Permissions (Default settings)



If you click the option to apply the permissions to child objects, all the
inheritable permissions will apply to the child objects. Explicitly applied
permissions (as opposed to inherited permissions) will be removed from the
child objects if you do this, so you'll either have to go back into the
down-level folders and add any upgraded permissions that get removed, or go
into the child objects and add the missing permissions that you would have
otherwise added at the root of the drive.

You can still modify the permissions on the root E folder and not apply them
down-level by checking that box. That way, no existing permissions will
change on the subfolders of E, but newly created folders will automatically
inherit the newly set permissions on E.


"TRI-C" <TRI-C@xxxxxxxxxxxxxx> wrote in message
news:9785224E-BE24-465D-B537-CDAC96565F2A@xxxxxxxxxxxxxxxx
Thank you. I was about to make the changes to the permissions at the root
of
the E-Disk but a message came up indicating that all other permissions
would
be replaced at all folders and subfolders. The way I understood the
message,
only the permissions that exist on the root folder would be propagated
down
to all other subfolders. I don't mind if that happens as long as the
explicit permissions on subfolders don't get removed. For example, if I
have
specific users or groups which have permissions on specific subfolders
will
they be removed if I make the change at the root (ie. E-Disk level)?

"Dave Nickason [SBS MVP]" wrote:

By default, new folders inherit the permissions of the parent folder.
Therefore, folders created on C create the permissions at the root of C.
So
if you tighten the permissions on the top-level E directory, newly
created
folders will inherit those tightened permissions.

On the Advanced tab, there's an option to propagate the permissions to
child
folders. That would let you apply tighter security to all the existing
files and folders on E, but obviously you'd want to do that very
carefully
to avoid unintended results. Also, depending on how many files and
folders,
be prepared for it to take a while.


"TRI-C" <TRI-C@xxxxxxxxxxxxxx> wrote in message
news:FEC64BA8-B170-43EF-8122-A2E16B600AB2@xxxxxxxxxxxxxxxx
Whenever I create a new directory on the C-drive on the SBS 2003
server,
there are always default permissions assigned (ie. Administrators with
all
permissions, Creator/Owner with .., Authenticated Users with ..., etc).
On
the other hand, on the other drive (say E:), whenever a new directory
is
created it is assigned the default permissions of "Everyone" with all
permissions. I was wondering how do you set the permissions of the E:
drive
to have the same permissions as the C: drive or perhaps other specific
permissions other than Everyone with Everything by default?





.



Relevant Pages

  • Re: NTFS Security Question.
    ... A subordinate object DOES not inherit the PARENT perms (in ... will assume "Nebulous" permissions that refer to the LINK ... The trick is to PROPOGATE to all FILES (not Folders and Files - that would ... Since Windows 2000 deny NTFS permission does not work ...
    (microsoft.public.windowsxp.security_admin)
  • RE: ISA 2004 REPORT FAILURE
    ... Did as you suggested and turned auditing on for the system and folders ... that is setting the wrong permissions of the folders ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: ISA 2004 REPORT FAILURE
    ... the ISA Reports still fail because ... I can change the permissions manually ... on the ISALogs and ISASummaries folders ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Personal Media Drive
    ... > much more knowledgeable about Windows than I am. ... You restrict access by assigning permissions to drives, folders and files. ...
    (microsoft.public.windows.mediacenter)
  • Re: Administrator/User security issues
    ... i have setup all the accounts, ... folders for testing the security. ... permissions but the admin. ...
    (microsoft.public.windowsxp.security_admin)