Why is Group Policy Limited to specific keys?
- From: "BenHanson" <bjh45964@xxxxxxxxx>
- Date: 15 Sep 2006 13:18:54 -0700
I've always failed to understand why Group Policy couldn't be used with
any registry key, the way it is used with the built-in ADM templates?
I know, I can create custom adm templates that will modify the registry
a la NT policies which tatoo the registry. But why can't they be
overlayed just like the real "policies?" I've always assumed the
overlaying was done in memory, e.g. loading keys under Group Policy in
place of the real key, thus leaving the previous setting in HKLM, or
HKU untouched. Why can't they do this with any key?
.
- Follow-Ups:
- Re: Why is Group Policy Limited to specific keys?
- From: Mark Heitbrink [MVP]
- Re: Why is Group Policy Limited to specific keys?
- Prev by Date: Re: GPO Password Policy is applied but not working
- Next by Date: Re: Why is Group Policy Limited to specific keys?
- Previous by thread: Force default printer through group policy
- Next by thread: Re: Why is Group Policy Limited to specific keys?
- Index(es):
Relevant Pages
|
Loading