|
|||||||||||
|
RE: Windows 2000 password policy
From: Chris Carlson (OTG) <ccarls(at)microsoft.com>
Date: Tue Jun 24 2003 - 13:31:36 EDT
Andre, let me include a snip from the support article I included, and I have tested this: There is an exception to this rule. You can configure another account policy for an organizational unit. The account policy settings for the organizational unit affect the local policy on any computers contained within that organizational unit. For example, if a Windows 2000-based workstation is in an organizational unit named OU1, an administrator could create a Group Policy object for OU1, and specify an account policy that is different from that of the default domain policy. In this case, when a user logs on to the domain, the account policy settings from the default domain policy are in place. When a user logs on locally to the Windows 2000-based workstation, the local account policy as defined by the Group Policy object for OU1 is used.
Thanks,
From: Andre Conde Caselli [mailto:ACaselli@aliancadobrasil.com.br]
Sent: Tue 6/24/2003 8:03 AM
Hi Chris, Password policy is a domain property and can be placed only at Default domain policy or in a new policy at Domain Level.
Regards
André Conde Caselli
Comunicação corporativa da Aliança do Brasil
-----Mensagem original-----
Okay, I stand corrected on that issue, but realistically I have never seen that sort of thing in the real world. One generally does not make a system part of the domain and then use local accounts to access it. One of the first things that I look for on a security audit is local accounts on critical systems. Besides the required administrator account, the only local accounts on a machine should be service accounts required by an application running on that box that for some reason or other cannot use a domain based system account. One could also make the argument that you need local accounts to work on the system should connectivity to the domain controller be severed due to a faulty WAN link. In that instance, since W2K machines cache local credentials, a user can still log onto a system with no connectivity to the domain provided that they have successfully logged on there before. Additionally, if access to the system is critical, then a local DC can provide the necessary fault tolerance. Local accounts are much easier to compromise than domain accounts, thus my recommendation is to strictly limit them. As for the necessary administrator account, while password policies can be applied, generally, users will exempt the administrator account from regular password changes, and account lockout cannot be applied to the built-in administrator.
Jim Barrett, MCSE, CISSA, CISSP, CCNP
-----Original Message-----
>You will see the options for setting password policy in the OU GPO, but
I wouldn't necessarily say that, password policies at the OU level still apply to the local security accounts. http://support.microsoft.com/default.aspx?scid=kb;en-us;255550 -Chris Received on Tue Jun 24 15:44:47 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:31 EDT |
||||||||||
|
|||||||||||