Re: Setting Password must meet complex requirements
From: Brian Komar (bkomar_at_nospam.identit.ca)
Date: 07/22/05
- Next message: Roger Abell: "Re: Lost security tools"
- Previous message: Lars Olaussen: "Re: EAL / ITSEC Security accreditation of Windows XP"
- In reply to: Angus: "Setting Password must meet complex requirements"
- Next in thread: Angus: "Re: Setting Password must meet complex requirements"
- Reply: Angus: "Re: Setting Password must meet complex requirements"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 22 Jul 2005 06:56:08 -0500
In article <36A7E217-4C33-475E-BED2-581EC791973A@microsoft.com>,
Angus@discussions.microsoft.com says...
> I enabled 'Password must meet complex requirements' on my Windows 2003 server
> on a test policy with a test user. All the other Password settings work, but
> 'Password must meet complex requirements' does not. I can type to user name,
> all numbers, all letters - it basically doesn't do what I read it was
> supposed to do.
>
> I ran gpupdate on the server. Using Windows 2003 SP1 - all patches current
> as of July 1.
>
> Any hints on what I did wrong?
>
> Thanks
>
This policy, in a domain environment, must be applied at the domain
level to affect domain accounts. If you linked the GPO (or applied a
local policy), this will only affect accounts in the local SAM database
of the computer.
Brian
-- == Brian Komar MVP - Windows - Security http://www.identit.ca/blogs/brian
- Next message: Roger Abell: "Re: Lost security tools"
- Previous message: Lars Olaussen: "Re: EAL / ITSEC Security accreditation of Windows XP"
- In reply to: Angus: "Setting Password must meet complex requirements"
- Next in thread: Angus: "Re: Setting Password must meet complex requirements"
- Reply: Angus: "Re: Setting Password must meet complex requirements"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|