Two
things.
First, you can't enforce different password policies on different OUs -
so don't even plan on it.
Second, the only time I've seen that is with a user logged onto a
downlevel client (most often 9x), trying to change from a non-complex password
which was in place prior to the complexity being enabled. Only fix I found for
that was an admin changing the password to one which met the complexity
requirements then having the user log in with that password and change to a new
one.
In
other words - its not the new password, its the old one, which is being tested
for complexity - which doesn't make sense, but that's apparently what's
happening.
Roger
--------------------------------------------------------------
Roger D. Seielstad - MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.
Roger D. Seielstad - MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.
-----Original Message-----
From: John Slack [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 10:20 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Group PolicyPeople
Can anyone point me in the right direction, I changed the domain group policy to enforce password changes on the users, I have since removed the changes to the policy. However I now have a situation where not even the administrator can change a password. It complains that the password doesn't meet the minimum requirements, even though all of the requirements have been removed. My intention was to make everyone change passwords across the Domain and then create individual OU policies once I had a clean start point.
Any suggestions on a fix will be welcome.
Regards
John Slack (VisionLogistics IT Support)
Mailto:[EMAIL PROTECTED]
www.visionlogistics.com/uk
Tel: +44 1782 652200
Fax: +44 1782 652266
