Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to meet password requirements

Status
Not open for further replies.

compuveg

IS-IT--Management
Dec 3, 2001
307
US

We've got Microsoft's 'password complexity' turned on.

The problem is that sometimes we can try to change a password, fulfilling all FOUR of the requested character types, and it STILL says we're not meeting the requirements of the password policy.

Any ideas?
 
What are the requirements, are you meeting the length? If you are then make the password harder, easy ones arent allowed. for insance, try something like "Pro94DieS" an see if it takes that, most will unless you have it really complex.

---------------------------------------
 
Well, above the 'password complexity' setup Microsoft allows us, I'm also requiring 8 characters. That's it.

If you don't know this, you probably can't help me, ut here's Microsoft's definition of the 'complexity requirements' GPO...

MicrosoftHelpFile said:
Password must meet complexity requirements Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy

Description
Determines whether passwords must meet complexity requirements.

If this policy is enabled, passwords must meet the following minimum requirements:

Not contain all or part of the user's account name
Be at least six characters in length
Contain characters from three of the following four categories:
English uppercase characters (A through Z)
English lowercase characters (a through z)
Base 10 digits (0 through 9)
Nonalphanumeric characters (e.g., !, $, #, %)
Complexity requirements are enforced when passwords are changed or created.

To create custom password filters, see the Microsoft Platform Software Development Kit and the Microsoft Technet.

 

Yep, I kept running the GPO until we just decided that we would do weekly password audits to enforce the complexity requirements 'manually' instead of turning on the complexity requirements in the default domain GPO. We still on occasion get users who are told their passwords don't meet complexity requirements, which is just hilarious. I'm glad Microsoft's security functions work so well that they even try to do the job after they're turned off.
 
I've found that if you use a password that contains a "likeness" to previous passwords, or a likeness to the username, it fails. How Microsoft determined the likeness rules is beyond me. The old Welcome1! seems to work everytime. Do you know if the user is starting off with the first few letters of the username?

Something else to check, are they using a password used in the past? I know, that is usually a different error, but it is Microsoft.....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top