Re: Domain vs Local Security Policy
From: Paul Adare - MVP - Microsoft Virtual PC (padare_at_newsguy.com)
Date: 03/05/04
- Next message: Steven L Umbach: "Re: New company installing a server on my lan"
- Previous message: Indred Cold: "Re: Bogus Security Update?"
- In reply to: Rich: "Re: Domain vs Local Security Policy"
- Next in thread: Herb Martin: "Re: Domain vs Local Security Policy"
- Reply: Herb Martin: "Re: Domain vs Local Security Policy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 5 Mar 2004 14:48:37 -0500
In article <803201c402e6$67e28a90$a101280a@phx.gbl>, in the
microsoft.public.win2000.security news group, Rich
<anonymous@discussions.microsoft.com> says...
> This is not true. You can create a separate OU with it's
> own password policy and block the policy inheritance from
> the parent.
>
No, you're wrong, and Steven is correct. To affect domain accounts, the
_only_ place you can set account policy is at the domain level. Set it
any where else and all you're affecting is accounts in the local SAM of
any computers to which the GPO applies.
-- Paul Adare Moral indignation is jealousy with a halo. H. G. Wells, The Wife of Sir Isaac Harman
- Next message: Steven L Umbach: "Re: New company installing a server on my lan"
- Previous message: Indred Cold: "Re: Bogus Security Update?"
- In reply to: Rich: "Re: Domain vs Local Security Policy"
- Next in thread: Herb Martin: "Re: Domain vs Local Security Policy"
- Reply: Herb Martin: "Re: Domain vs Local Security Policy"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|