Click to Rate and Give Feedback
TechNet
TechNet Library
Windows
Windows Server
Windows Server 2003
Product Help
Security
Account Policies
Password Policy
 Passwords must meet complexity requ...

  Switch on low bandwidth view
Passwords must meet complexity requirements

Updated: April 30, 2009

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

Password must meet complexity requirements

Description

This security setting determines whether passwords must meet complexity requirements.

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

  • Not contain the user's entire Account Name or entire Full Name. The Account Name and Full Name are parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the Account Name or Full Name are split and all sections are verified not to be included in the password. There is no check for any character or any three characters in succession.

  • Contain characters from three of the following five categories:

    • English uppercase characters (A through Z)

    • English lowercase characters (a through z)

    • Base 10 digits (0 through 9)

    • Non-alphabetic characters (for example, !, $, #, %)

    • A catch-all category of any Unicode character that does not fall under the previous four categories. This fifth category can be regionally specific.

ImportantImportant
Complexity requirements are enforced when passwords are changed or created.

To create custom password filters, see the Microsoft Platform Software Development Kit and TechNet on the Microsoft Web site.

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 as such: 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:

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Clarification of content      Peter Wawa   |   Edit   |   Show History
  • Significaunt portion is 3 or more characters
  • There is fifth category of characters to be counted: All other Unicode characters
  • At least 6 characters in lenght is actually requirement of Minimum Password Lenght, not complexity requirements.
Tags What's this?: Add a tag
Flag as ContentBug
Topic is corrected      Justinha   |   Edit   |   Show History
Thank you for the clarification Peter. The topic has been corrected.
Tags What's this?: Add a tag
Flag as ContentBug
Further clarification of content      Clarifcation of rules   |   Edit   |   Show History
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 -
  1. must the delimiter itself also be absent from the password?
  2. if one of those sections is a single character, must it still be absent from the password?
What is the meaning of "There is no check for any character or any three characters in succession."?

The policy manager summarizes thus "Not contain the user's account name or parts of the user's full name that exceed two consecutive characters." However the description in the article I'm commenting does not mention these parts or the 'two consecutive character' limit.

thanks
Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker