Re: Grpedit.msc from bootable cd
- From: John John <audetweld@xxxxxxxxxxx>
- Date: Sun, 09 Dec 2007 07:24:44 -0400
Sam Hobbs wrote:
"Marco Schlegel" <no@xxxxxxxx> wrote in message news:%23FRaM8MOIHA.4752@xxxxxxxxxxxxxxxxxxxxxxx
On a working Windows XP machine snap the registry then do the changes in the Group Policy then re-snap the registry then do a compare for the differences between the two snaps. This registry snap & compare technique is almost like a closely guarded trade secret, I don't give it out everyday!
Hi John
In a Microsoft tech article I read that the group policy security settings are not stored in the registry :-(
Is that not true?
Regards
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.
John
.
- Follow-Ups:
- Re: Grpedit.msc from bootable cd
- From: Sam Hobbs
- 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
- Grpedit.msc from bootable cd
- Prev by Date: Re: Magnifying Window
- Next by Date: Re: Magnifying Window
- Previous by thread: Re: Grpedit.msc from bootable cd
- Next by thread: Re: Grpedit.msc from bootable cd
- Index(es):
Relevant Pages
|
Loading