RE: security policy 'not specified' option

From: Laura A. Robinson (larobins_at_bellatlantic.net)
Date: 10/21/05

  • Next message: Thor (Hammer of God): "Re: security policy 'not specified' option"
    Date: Fri, 21 Oct 2005 14:49:48 -0400
    To: "'Tyson Leslie'" <Leslie.Tyson@colteng.com>, "'matthew patton'" <pattonme@yahoo.com>, <focus-ms@securityfocus.com>
    
    

    Actually, you can configure NTFS permissions via Group Policy.

    Laura

    > -----Original Message-----
    > From: Tyson Leslie [mailto:Leslie.Tyson@colteng.com]
    > Sent: Thursday, October 20, 2005 6:05 PM
    > To: matthew patton; focus-ms@securityfocus.com
    > Subject: RE: security policy 'not specified' option
    >
    > If the settings conflict, the domain policy will overwrite
    > the local policy settings. If you have made weird policy
    > changes on a workstation that you want to undo, you can use
    > the Security Configuration and Analysis tool to re-establish
    > the original security settings. I don't think it will reset
    > NTFS permissions though...
    >
    > Tyson.
    >
    > -----Original Message-----
    > From: matthew patton [mailto:pattonme@yahoo.com]
    > Sent: Thursday, October 20, 2005 2:57 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?
    >
    > --------------------------------------------------------------
    > ----------
    > ---
    > --------------------------------------------------------------
    > ----------
    > ---
    >
    >
    > --------------------------------------------------------------
    > -------------
    > --------------------------------------------------------------
    > -------------
    >

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


  • Next message: Thor (Hammer of God): "Re: security policy 'not specified' option"

    Relevant Pages

    • Re: scripted logon
      ... Why can't you launch all the scripts from a Group Policy based Logon script. ... Here's the policy settings (I sure hope word wrap doesn't mess it up too ... Windows Components/Windows Installer ...
      (microsoft.public.windows.terminal_services)
    • Re: GPO Update Problem (SYSVOL access via UNC)
      ... Server Security and Auditing Policy ... This list only includes links in the domain of the GPO. ... The settings in this GPO can only apply to the following groups, users, ...
      (microsoft.public.win2000.group_policy)
    • Re: GPO Update Problem (SYSVOL access via UNC)
      ... > Server Security and Auditing Policy ... > This list only includes links in the domain of the GPO. ... > The settings in this GPO can only apply to the following groups, users, ...
      (microsoft.public.win2000.group_policy)
    • Re: GPO Update Problem (SYSVOL access via UNC)
      ... >> Server Security and Auditing Policy ... >> The settings in this GPO can only apply to the following groups, users, ... >> Windows Firewall: Allow file and printer sharing exception Enabled ...
      (microsoft.public.win2000.group_policy)
    • Re: having problems getting security options to work in group policy
      ... Make sure you are applying these settings at the proper level. ... Domain Security Policy would apply to all other domain computers, ...
      (microsoft.public.windows.group_policy)