Passwords must meet complexity requirements

Updated: March 25, 2011

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2

Password must meet complexity requirements

Description

This security setting determines whether passwords must meet complexity requirements. Complexity requirements are enforced when passwords are changed or created.

If this policy is enabled, passwords must meet the following minimum requirements when they are changed or created:

  • Passwords must not contain the user's entire samAccountName (Account Name) value or entire displayName (Full Name) value. Both checks are not case sensitive:

    • The samAccountName is checked in its entirety only to determine whether it is part of the password. If the samAccountName is less than three characters long, this check is skipped.

    • The displayName is parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the displayName is split and all parsed sections (tokens) are confirmed not to be included in the password. Tokens that are less than three characters in length are ignored, and substrings of the tokens are not checked. For example, the name "Erin M. Hagens" is split into three tokens: "Erin," "M," and "Hagens." Because the second token is only one character long, it is ignored. Therefore, this user could not have a password that included either "erin" or "hagens" as a substring anywhere in the password.

  • Passwords must contain characters from three of the following five categories:

    • Uppercase characters of European languages (A through Z, with diacritic marks, Greek and Cyrillic characters)

    • Lowercase characters of European languages (a through z, sharp-s, with diacritic marks, Greek and Cyrillic characters)

    • Base 10 digits (0 through 9)

    • Nonalphanumeric characters: ~!@#$%^&*_-+=`|\(){}[]:;"'<>,.?/

    • Any Unicode character that is categorized as an alphabetic character but is not uppercase or lowercase. This includes Unicode characters from Asian languages.

noteNote
A given character can satisfy only one category. The GetStringTypeW API (http://go.microsoft.com/fwlink/?LinkId=205607) is used to test whether each character in the password is uppercase, lowercase, or alphanumeric.

To create custom password filters, see Password Filters (http://go.microsoft.com/fwlink/?LinkId=205613).

Default:

  • Enabled on domain controllers.

  • Disabled on stand-alone servers.

noteNote
By default, member computers follow the configuration of their domain controllers.

Configuring this security setting

You can configure this security setting by opening the appropriate policy and expanding the console tree: Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy\

For specific instructions about how to configure password policy settings, see Apply or modify password policy.

For more information, see:

Change History

 

Date Revision

November 15, 2010

The description was revised to be more precise and accurate. The precise attribute names were added and the character categories were updated.

November 30, 2010

The description “Far eastern” was changed to “Asian.”

Tags :


Community Content

raviking
Password Enforcement
Is it possible to create a password filter to enforce the following rules: $0At least 2 Uppercase Letters$0 $0At least 2 Lowercase Letters$0 $0At least 2 Special Characters$0 $0$0 $0 $0If it is is there an existing example of a filter that does?$0 $0$0 $0 $0What/where is documentation to guide administrator to create such a policy as above?$0 $0$0 $0 $0V/R$0 $0$0 $0 $0Jack$0 $0$0 $0 $0$0 $0 $0Hey Jack, Please update if you got any answer regarding password policy filters.$0

sgaur
Help - I want to CHANGE the complexity of password settings before I Enable it
<p>How do I set the complexity settings from the default in windows 2008 Server?<br /></p> <p>I want to enforce, 1 Uppercase AND 1 Lowercase AND 1 Number AND 1 special charater.<br /></p> <p> <br /> </p> <p>i.e. all four must be entered in password. The default is 3 out of 4.<br /></p> <p> <br /> </p> <p>Thanks</p>
Tags :

Rugero
Passwords must meet complexity requirements not defined
Does this mean password complexity is not enforced or it defers to complexity definitions included in the Passfilt file? Thanks<br />
Tags :

Thomas Lee
Clarification of content
<ul> <li> <i>Significantportion</i> is 3 or more characters</li> <li>There is fifth category of characters to be counted: All other Unicode characters</li> <li> <i>At least 6 characters in length</i> is actually requirement of Minimum Password Lenght, not complexity requirements.</li> </ul>
Tags :

Thomas Lee
Where is this setting stored?
<p>I am trying to run a report on this setting in a piece of reporting software we own. I can find the setting using a WMI call on a non-Domain controller. But I cannot find this setting on an AD controller. Is this stored in the registry somewhere? Maybe a different spot in WMI?</p>
Tags :

tobyallen
Is - a special character?
it seems that - is not counted as a special charater.<div><br /></div><div>This seems pretty odd to me.</div>
Tags :

Clarifcation of rules
Further clarification of content
If the user's entire Account Name or entire Full Name contain a delimiter such as a period and each delimited section is verified to be absent from the password - <br /><ol><li>must the delimiter itself also be absent from the password?</li><li>if one of those sections is a single character, must it still be absent from the password?</li></ol>What is the meaning of "There is no check for any character or any three characters in succession."?<br /><br />The policy manager summarizes thus "Not contain the user's account name <b>or parts of the user's full name that exceed two consecutive characters</b>." However the description in the article I'm commenting does not mention these parts or the 'two consecutive character' limit.<br /><br />thanks<br />
Tags :

Justinha
Topic is corrected
Thank you for the clarification Peter. The topic has been corrected.
Tags :

Page view tracker