Re: Is every user a member of Users?

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 01/05/05

  • Next message: Roger Abell: "Re: Is every user a member of Users?"
    Date: Tue, 4 Jan 2005 22:24:10 -0700
    
    

    lusrmgr.msc run at a cmd prompt (as you refer to
    c:\winnt should I assume this is Windows 2000?)
    lets you see the group structure in all existing detail.

    Originally Users only held accounts. Later MS invented
    Interactive and Authenticated Users and nested these
    within. This was as much as anything a response to the
    fact that the OS had grown in ways such that if an account
    was not a member of Users then things would fail in an
    interactive login. It is not just the NTFS permissions in
    the system folders, but also a matter of permissions on the
    COM components and registry keys, where some grants are
    to the Users group.

    I think historically the intent was to have Guests, Users,
    and Administrators with these three being allowed a tiered
    increase in capability. However, thing were IMO not kept
    fully clean, and for all practical purposes the distinction
    between Guest and any Users member began lost and also
    impossible for interactive login. In large part this was a
    response to MS observing the common (and reasonable)
    practice of removing the default grants to Everyone (which
    used to allow Guest to function interactively).

    By the way, although it looks like a group in the icon used,
    System is best thought of not as a group but as an account.
    I think it is treaded as a group because in a stand-alone install
    the Local System account (which is used to fire up most of the
    core components/services of the OS) is System, but once the
    machine is joined to a domain then the domain\Machine$
    account also is System.

    Aside from accounts and normal groups, you will find some
    "group-like" predefined principals used (Interactive, Network,
    Authenticated Users, Creator Owner, etc.) whose membership
    you cannot adjust. These are like place-holders which get
    substitiuted with the "then current" account if the criteria of
    the place being held are satisfied. If I have logged in as UserX
    at the keyboard, then UserX actually appears in the security
    access checks where Interactive is seen when viewing the
    definitions, etc..

    -- 
    Roger
    "Les Desser" <NewsDump1@dessergroup.com> wrote in message
    news:T30y9wGOMo2BFA+A@dessergroup.onetel.co.uk...
    > In article <e8tCduf8EHA.3820@TK2MSFTNGP11.phx.gbl>, Roger Abell
    > <mvpNOSpam@asu.edu> Mon, 3 Jan 2005 18:23:36 writes
    >
    > >The membership in the Users group is only exactly what is shown when
    > >you view it. Now, in a default scenario you will see that Interactive
    > >and Authenticated Users are nested within Users.
    >
    > Please do you have any pointers as to where I can see this on the system
    > or at least read about it.
    >
    > > Due to these any account that logs in locally or any account that is
    > >authenticated (respectively) will become a Users member during that
    > >login/usage. These groups do not have to be nested within Users, but
    > >when removed one does need to understand what they have been enabling
    > >so that the parts of that which are needed can be provided.
    >
    > More reading - groan! :)
    >
    > I am just a starter on the Windows security front, but as I see it:-
    >
    > Users is a sytem group (like SYSTEM) (I wonder if I can delete it) and
    > it should not be possible to assign anyone to this group.  What strange
    > mind thought up a structure that allows me to remove membership of a
    > user from a specific group, but the user still remains (in 99.99% of the
    > time) a member via a hidden route.
    >
    > Also, why does Windows put every newly created user explicitly into the
    > Users group? - and thereby totally confuse poor punters like me.
    > -- 
    > Les Desser
    > (The Reply-to address IS valid)
    

  • Next message: Roger Abell: "Re: Is every user a member of Users?"

    Relevant Pages

    • Re: Program starts up for all users
      ... > member has their own account. ... > computer and it automatically loads on startup. ... > significantly increasing startup time and creating annoying windows to ... Log into each user's account and start AIM. ...
      (microsoft.public.windowsxp.basics)
    • Re: Share Permissions and Security Groups
      ... >> storage on a member server. ... >> If the account is in no group that directly or indirectly has been ... >> resources that are controlled and add the groups of principals ... > From your comments I ensure that each Project Folder NTFS does not inherit ...
      (microsoft.public.security)
    • Re: Is every user a member of Users?
      ... "Les Desser" wrote in message ... > member of Users when they are anyway a member of ... An account is automatically added to users as a part of the ... if you do not let INTERACTIVE and/or Authenticated Users ...
      (microsoft.public.win2000.security)
    • mssbsssr/sbsmonacct causing audit failure
      ... it first checks if the user account sbsmonacct exists, ... It is a member of Domain Users, Enterprise Admins, and by implication Users ... a member of either the Remote Operators group or the Domain Power Users ... This happens because on SBS 2003, the "Deny log on locally" policy ...
      (microsoft.public.windows.server.sbs)
    • User cant access OWA or RWW
      ... New staff member aboard; heading out on a business trip so I'm walking her through the process of accessing her email and desktop remotely. ... Keeps getting the note that either her login or password are bad. ... I then used the Add User wizard in Server Management to create a new account for her. ... User not allowed to logon at this computer ...
      (microsoft.public.windows.server.active_directory)