Active Directory - Password Policy Requirements- Failing

Hello All;

Windows 2003 Enterprise Server
New Install after a [error: 0x00002e1] and could not recover from it.
ERD - Went bad, so their was no way of recovery, even after following all
adviced
Information fount thru-out the internet.

(The following information is as it was before)
I have gone into [Group Policy Object Editor]
And set up the [Password Policy] to the following:

Enforced Password History [not defined]
Maximum Password age [not defined]
Minimum Password age [not defined]
Minimum Password Length [not defined]
Password must meet complexity requirements [disabled]
Store passwords using reversible encryption [disabled]

In the "Active Directory" [Users] New [User]
The Username(s) and Password(s) have the same "First [4] characters"
Thus the reason for setting: Password must meet complexity requirements
[disabled]
When clicking [Finish] to Create the User.
I receive:
================================================== ===============
Windows cannot set the password for user name because:
The password does not meet the password policy requirements.
Check the minimum password length, password complexity and password history
requirements.
================================================== ===============

I even rebooted the Server after making the changes to the "Password Policy"
to
See if that would allow me to create the users, and no go.

The Username(s) and Password(s) are the same as before.
And all users use the "First [4] Characters" for Username & Password.

Any information on why this is doing this, I would really truely appreciate
it.

Thanks all;
Wayne

Try these settings..

Enforced Password History [0]
Maximum Password age [0]
Minimum Password age [30]
Minimum Password Length [0]
Password must meet complexity requirements [disabled]
Store passwords using reversible encryption [disabled]

Then set them back to how you want them ie

Enforced Password History [not defined]
Maximum Password age [not defined]
Minimum Password age [not defined]
Minimum Password Length [not defined]
Password must meet complexity requirements [disabled]
Store passwords using reversible encryption [disabled]

Hope that helps
KIWI


"Wayne& Carr" <> wrote in message
news:...
> Hello All;
>
> Windows 2003 Enterprise Server
> New Install after a [error: 0x00002e1] and could not recover from it.
> ERD - Went bad, so their was no way of recovery, even after following all
> adviced
> Information fount thru-out the internet.
>
> (The following information is as it was before)
> I have gone into [Group Policy Object Editor]
> And set up the [Password Policy] to the following:
>
> Enforced Password History [not defined]
> Maximum Password age [not defined]
> Minimum Password age [not defined]
> Minimum Password Length [not defined]
> Password must meet complexity requirements [disabled]
> Store passwords using reversible encryption [disabled]
>
> In the "Active Directory" [Users] New [User]
> The Username(s) and Password(s) have the same "First [4] characters"
> Thus the reason for setting: Password must meet complexity requirements
> [disabled]
> When clicking [Finish] to Create the User.
> I receive:
> ================================================== ===============
> Windows cannot set the password for user name because:
> The password does not meet the password policy requirements.
> Check the minimum password length, password complexity and password
> history
> requirements.
> ================================================== ===============
>
> I even rebooted the Server after making the changes to the "Password
> Policy"
> to
> See if that would allow me to create the users, and no go.
>
> The Username(s) and Password(s) are the same as before.
> And all users use the "First [4] Characters" for Username & Password.
>
> Any information on why this is doing this, I would really truely
> appreciate
> it.
>
> Thanks all;
> Wayne
>
>

Hello ["KIWI"];

Figured it out. (What of them things that make you go "hummmm")

The "Minimum Password Length" [10]
The [10] is the minimum amount that the password length will be.
I was setting it to [14] and then to [undefined]
And it was not taking the Length of [10]
Which is the character count of the password.

Basically, I was thinking [Maximum] when it is [Minimum]

Just something that I over looked, a BIG over look.

Thanks for your post, as it is what made me "Pay more attention" to what
I was doing.

Take Care
Wayne