5/17/11

How to Run the Windows Domain Default Password

Password policy settings can be configured to fit security and authentication standards for a given domain. The general procedure for making modifications, as Microsoft recommends, is to create a new Group Policy object and leave the Default Domain Policy intact. However, if modifications have been made to the Default Domain Policy, you will have to manually configure these settings to fit the criteria for default state. This change of settings can be accomplished through the Active Directory Users and Computer snap-in, which is available if your system runs Exchange management tools.
    • 1

      Click "Start" > "All Programs" > "Microsoft Exchange" > "Active Directory Users and Computers." The "Active Directory Users and Computers" console opens up.

    • 2

      Right-click the root container that corresponds to the domain that needs to run the default password (It is noted by a ".com" extension). Choose "Properties" from the drop-down menu.

    • 3

      Select the "Group Policy" tab, select "Default Domain Policy" from the "Group Policy Object Links" list, and click the "Edit" button. The "Group Policy Object Editor" window opens up.

    • 4

      Expand "Computer Configuration" > "Windows Settings" > "Security Settings" > "Account Policies" and click "Password Policy." A list of policies displays on the right pane.

    • 5

      Double-click "Enforce Password history." A "Properties" window opens up. Enter the default value "24" in the "Keep password history for" item, click "Apply" and "OK."

    • 6

      Double-click the remaining policy items in the list, and modify each according to the following default values below:

      Enter "42 days" for the "Maximum password age" policy.

      Enter "1 day" for the "Minimum password age" policy.

      Enter "7 characters" for the "Minimum password length" policy.

      Choose "Enabled" for the "Password must meet complexity requirements" policy.

      Choose "Disabled" for the "Store password using reversible encryption" policy.

  • No comments: