It depends which policy you are trying to edit ?!?

Some of the XP/2000 have the 3 options.

Have you tried running secpol.msc and looking at the settings you have
there.

Once you have set a policy from Not Defined you can only select enable or
disable, unless you reload the policy files from a clean build

-----Original Message-----
From: matthew patton [mailto:pattonme (at) yahoo (dot) com [email concealed]]
Sent: 20 October 2005 21:57
To: focus-ms (at) securityfocus (dot) com [email concealed]
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?

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

[ reply ]