When you say that you want your machines to inherit the "domain setting", you
have to have those machines only process a "default domain" policy, otherwise,
there could be other policies which add order of inheritance into the equation.
You have to find out which policy actually causes a setting to be set. Use the
Resultant set of Policies approach to find out what that is.
Also, if you have a doubt about what setting a machine might have, standardize
your "local computer policies" that is, those policies which apply to a machine
before it joins a domain.
Slawek
-----Original Message-----
From: matthew patton <pattonme@yahoo.com>
Sent: Oct 20, 2005 3:56 PM
To: focus-ms@securityfocus.com
Subject: security policy 'not specified' option
Some time back I used a security policy editor that had 3 options:
enabled, disabled, and 'unset'. By not setting it either way, the
machine inherited the domain settings. Unfortunately the standard
system policy editors shipped with 2K/2K3/XP don't appear to have that
3rd option which means now I've got all kinds of machine running with
who knows what setting and ignoring the domain policy. And once you've
selected en/disabled via the radio box, there isn't a way to unset it.
How do I dig myself out of this?
I probably can play Registry Magic and accomplish what I need but I
could have sworn I had a tool that would let me do what I used to be
able to do.
any ideas?
---------------------------------------------------------------------------
---------------------------------------------------------------------------
________________________________________
PeoplePC Online
A better way to Internet
http://www.peoplepc.com
---------------------------------------------------------------------------
---------------------------------------------------------------------------
