2003 Domain Password Policy with NT 4.0 Workstations

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Rob Lowe (none)
Date: 02/10/04


Date: Tue, 10 Feb 2004 17:41:59 -0600

My client is in the process of migrating from Windows NT 4.0 SP6 with the
AD-aware client to Windows XP SP1.

We would like to apply a more stringent password policy to the domain to
force periodic password changes, retaining password history and requiring
complex passwords.

The question is: Would application of this password policy to all
Authenticated Users in the domain apply to users logging on from a Windows
NT Workstation? (I believe that they would not since GPO's should not be
processed by Windows NT computers, but I'm just looking for validation).

Cheers!
-Rob



Relevant Pages

  • Re: Limiting Ability to Join Domain
    ... Microsoft MVP - Windows NT Server ... They can add maximum 10 workstations ... > Authenticated Users group by default. ... >> Microsoft MVP - Windows NT Server ...
    (microsoft.public.windows.server.setup)
  • Re: Limiting Ability to Join Domain
    ... Windows 2000 grants the "Add workstations to domain" privilege to the ... Authenticated Users group by default. ...
    (microsoft.public.windows.server.setup)
  • Re: Password policy
    ... Password policies must be set at the domain level. ... Windows 2003 as well. ... > the password policy, and link it to domain controllers. ... > replicate to all domain computers. ...
    (microsoft.public.win2000.security)
  • RE: Please Help
    ... Domain Controllers container, and then click Properties. ... and then add Everyone and Authenticated Users. ... Windows XP Security Homepage: ... Windows 2000 Security Homepage: ...
    (microsoft.public.windowsxp.security_admin)
  • Re: windows new users?
    ... the Authenticated Users group and the Interactive Users group are added to the Users group on Windows Server 2003 computers. ... A member of the Interactive Users group, whose credentials are trusted, can log on to the server interactively. ... automatically a member of the the interactive group, remove this account and no one will be able to logon locally. ...
    (microsoft.public.windowsxp.setup_deployment)