Re: Sharing Tab vs. Security Tab

Tech-Archive recommends: Speed Up your PC by fixing your registry



I noticed the 'SYSTEM' account in one of the accounts inherited from the root
of D. If I block inheritance, should I give the SYSTEM account access to the
USERS folder?

What exactly does this SYSTEM account do?

"Arek Iskra [MVP]" wrote:

> "PM" <PM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:276DCBD8-C163-4469-AECA-5E10809856C1@xxxxxxxxxxxxxxxx
> >I understand the general differences between the two tabs for Windows 2000
> > Server, but would like some advice.
> >
> > I'll use a USERS share for an example. If I have d:\users, with
> > subfolders
> > under 'users' for indivudual users, should the USERS folder be shared to
> > everyone - full control? What should the security tab have in it? I
> > understand that each sub folder should NOT be shared, and the security tab
> > should have the individual account listed.
> >
> > My big question is: The security tab inherits permissions from the root D:
> > drive. Should I block this inheritance?
> >
> > Thanks
>
> Ok, the basic difference between share permissions and local (NTFS)
> permissions is that the first one applies to users accessing a resource from
> the network, while the latter one applies when the user has a direct access
> to computer (e.g. when you yourself sit in front of it).
>
> Regarding blocking/unblocking inheritance - it all depends what you are
> trying to achieve. If you want to limit access only to certain users, then
> go ahead and block it.
>
> One more thing to remember about combining share and local permissions: a
> combination of them applies where the most restrictive takes precedence. For
> example, if you give Full Control permission on the local level and Read
> permission on the share, the result for someone accessing it over the
> network will be Read access. Of course, if the person sits in front of the
> computer he will get Full Control.
>
> --
> Arek Iskra
> MVP for Windows Server - Software Distribution
>
>
>
.



Relevant Pages

  • Re: AD User Objects & Permission Inheritance
    ... I went ahead and granted the Account Operators built in group rights on the adminSDholder object according to what I want the OU admins to have. ... I went ahead and enabled inheritance on the> adminSDholder object to verify that this indeed was the cause and 60> minutes ... > later all user objects began to inherit permissions again. ...
    (microsoft.public.win2000.active_directory)
  • Re: Permissions resetting in Blocked Inheritance OUs
    ... If the ACL that is on the AdminSDHolder object is ... Delegated permissions are not available and inheritance is automatically ... "You do not have sufficient permissions in the Domain" error message occurs ... This user account is in an OU that has Blocked ...
    (microsoft.public.windows.server.active_directory)
  • Re: Permissions resetting in Blocked Inheritance OUs
    ... If the ACL that is on the AdminSDHolder object is ... Delegated permissions are not available and inheritance is automatically ... "You do not have sufficient permissions in the Domain" error message occurs ... This user account is in an OU that has Blocked ...
    (microsoft.public.windows.server.active_directory)
  • Re: Permissions resetting in Blocked Inheritance OUs
    ... Some SIDs can not be resolved on workstations such as Server Operators and Account Operators because they only have existence on the DCs. ... Now the odd SID is probably a weird ACE on the adminSDHolder object, read up on that and this will probably make more sense. ... If i leave the account for a little while and go back to it the PA's account has been replaced with an unrecognised account with just a SID and different permissions. ... I have tested with other accounts and it only seems to affect accounts that are in OU's that have blocked inheritance set in Group Policy. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Permissions resetting in Blocked Inheritance OUs
    ... Your director shouldn't have enhanced rights in the directory and that is what causes that, he should have a normal user account. ... If i leave the account for a little while and go back to it the PA's account has been replaced with an unrecognised account with just a SID and different permissions. ... I have tested with other accounts and it only seems to affect accounts that are in OU's that have blocked inheritance set in Group Policy. ...
    (microsoft.public.windows.server.active_directory)