Turn off Complex Password requirement in Windows - InSource KnowledgeCenter
Using Microsoft Windows and setting up a user account, but the software is requiring a “Complex Password” to Windows Server Set “Password must meet complexity requirements” to Disabled. There are no recommended articles. Windows cannot set the password for because: The password does not meet the password policy requirements. Check the minimum. I just setup a new Windows server with a new AD. When I create new users on this new domain. I keep getting this window: Active Directory Domain.
Windows Server 2003 Password Policy Changes
If the maximum password age is set to 0, the minimum password age can be any value between 0 and days. It is a security best practice to have passwords expire every 30 to 90 days, depending on your environment. Right-click on Passwords must meet complexity requirements.
Click Properties from the context menu. Do not remove the check from the Define this policy setting checkbox.
Select the Disabled option. This will allow less complex passwords Click the OK button.
Double-click on Minimum Password Length in the right pane. Enter a new minimum password length.
Entering Zero 0 will remove the password requirement. Click the OK button. Close the Default Domain Security Settings window. This is the case with the Account Policies for domain users.
When you have a basic Active Directory domain that's running at the Windows Server Domain Functional Level, the Account Policies for all domain users behave the exact same way they always have. The Default Domain Policy defines the password policies by default for every user in Active Directory and every user located in the local SAM on every server and desktop that joins Active Directory.
[ R2] Password does not meet complexity requirements, but they're disabled!!
There can be only one password policy for domain users using Group Policy. The password policy settings can't be extended to include additional settings without using a third-party tool or developing a custom password policy solution. It's not possible to configure a password policy for the root domain and have it "funnel" down to the other domains in the Active Directory tree.
Notice that the bullet list here is very similar to the list that was at the beginning of this article. The reason is that the Account Policy and password policy, even for Windows Server R2 domains, behave the exact same way as previous Windows and domains by default. When this occurs, it opens the door for FGPPs.Windows Server 2012 R2 Setting Active Directory User Password Policy (GPO) Tutorial
The same Active Directory domain can have multiple password policies. The result could be the following: This might sound odd, and I must agree it is. To complete the configuration of your FGPPs, you'll need to complete the following steps: