Re: Grpedit.msc from bootable cd
- From: "Sam Hobbs" <samuel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 9 Dec 2007 13:42:49 -0800
"John John" <audetweld@xxxxxxxxxxx> wrote in message
news:eMM8OYlOIHA.4912@xxxxxxxxxxxxxxxxxxxxxxx
Sam Hobbs wrote:
It probably depends on what is meant by "stored". I know that some Group
Policies, probably most, are effective only when they are put into the
registry. It is possible to affect the effectivity of a policy by
changing only the registry. The confusion lprobably is that the policy
editor edits data from a non-registry file that administrators are more
familiar with than I. Any changes made by the policy editor will be
ineffective unless they are put into the registry.
Does that sound like an explanation of what the "Microsoft tech article"
meant?
No, Sam. The security settings are saved and applied elsewhere, I don't
believe that you can restore the logon rights by registry modifications.
Sure, security settings exist elsewhere; somewhere in the NTFS which is not
documented. Security settings are DACLs, ACEs, SIDs and other objects which
are documented. The group policy that determines security settings does not
exist in the NTFS.
.
- Follow-Ups:
- Re: Grpedit.msc from bootable cd
- From: John John
- Re: Grpedit.msc from bootable cd
- References:
- Grpedit.msc from bootable cd
- From: Marco Schlegel
- Re: Grpedit.msc from bootable cd
- From: John John
- Re: Grpedit.msc from bootable cd
- From: Marco Schlegel
- Re: Grpedit.msc from bootable cd
- From: Sam Hobbs
- Re: Grpedit.msc from bootable cd
- From: John John
- Grpedit.msc from bootable cd
- Prev by Date: Re: Need advice for best approach for root cause analysis
- Next by Date: Re: Download vs upload
- Previous by thread: Re: Grpedit.msc from bootable cd
- Next by thread: Re: Grpedit.msc from bootable cd
- Index(es):
Relevant Pages
|