Re: 2003 Domain Password Policy with NT 4.0 Workstations

From: Derek Melber [MVP] (derekm_at_braincore.net)
Date: 02/12/04


Date: Wed, 11 Feb 2004 22:03:57 -0700

The only way to exclude users from adhering to the domain password policy is
to have them logon with a local user account, which is not a great idea. If
you want to have multiple password policies, the answer is two domains.

Sorry, but that is the way it works. What you propose won't work, since you
are attempting to apply a computer policy to a user. The password policy is
a computer setting and only applies to a computer object.

-- 
Derek Melber
"Rob Lowe" <none> wrote in message
news:OFrMH0N8DHA.1504@TK2MSFTNGP12.phx.gbl...
> Thanks for your prompt reply!
>
> I don't want to apply a restrictive password policy to my users still
> running Windows NT 4.0, so would the following scenario work?
>
> 1.  Modify the Default Domain Policy and remove the Account
> Policies/Password Policy settings.
> 2.  Create a new GPO object and define the Account Policies/Password
Policy
> settings here.
> 3.  Define security so that the GPO with defined Account Policies/Password
> Policy settings is only processed by security group containing user
accounts
> that have been migrated to Windows XP.
>
> If this scenario would work, should this GPO be linked before or after the
> Default Domain Policy is processed?
>
> Thanks!
>
> "Derek Melber [MVP]" <derekm@braincore.net> wrote in message
> news:eh0nEED8DHA.2676@TK2MSFTNGP10.phx.gbl...
> > Yes it would, if they are authenticating to Active Directory. Remember,
> > Account POlicies are not user or client computer based... they are DC
> based.
> > They modify the DC to allow or disallow certain passwords. It is a
filter
> on
> > the DC that forces the rules. So, if a Windows NT Workstation is joined
to
> > the AD domain, it will adhere to the Account Policy that is in place on
> the
> > domain.
> >
> > -- 
> > Derek Melber
> >
> > "Rob Lowe" <none> wrote in message
> > news:OF4B69C8DHA.2028@TK2MSFTNGP10.phx.gbl...
> > > 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: problems to install inf files under windows xp automaticially
    ... is one policy missing in xp which exists in windows 2000. ... > The Policy you can find under Security Options, ... > driver installation behavior ... Anyway first check on what account the thing runs. ...
    (comp.os.ms-windows.nt.admin.security)
  • Re: Need advice from expert
    ... Hope this will be fixed in the next release of Windows. ... >Local Security Policy applies equally to all accounts, ... >group policy is really a domain level control feature, ... This account will then not be affected by any ...
    (microsoft.public.windowsxp.security_admin)
  • 2003 Domain Password Policy on NT 4.0 Workstation
    ... I have a client in th eprocess of migrating from Windows NT 4.0 SP6 with the ... AD-aware client to Windows XP SP1. ... Windows XP since the new password policy will be discussed during training. ...
    (microsoft.public.win2000.group_policy)
  • Re: Allowing only IE and nothing else - possible?
    ... Shows the details needed to lock down a Windows 2000 system using local ... > Many of the Group Policy settings are available for the local policy on ... the link above really isn't suitable for a single two user account ...
    (microsoft.public.win2000.group_policy)
  • Re: Problems testiing GPO for password complexity on OU before changing default domain policy
    ... Account policies are only read at the domain level and you can only have one ... apply to the local machine account policy. ... The complex password policy is applied when I logon to the local machine but not when I logon with a domain user which is a member of the OU and security group within that OU. ...
    (microsoft.public.win2000.active_directory)