The minimum password length setting decides the shortest password Windows will accept for an account. On many small office servers it is still at the factory value, which can be zero. Our advice is simple: set the minimum password length on your Windows Server to 15 characters. This post explains why 15, how to check what your server allows today, and exactly where to change it, including the catch on older servers that stop at 14.
What Windows allows out of the box
Microsoft documents these defaults for the Minimum password length policy:
| Type of server | Default minimum length |
|---|---|
| Stand-alone server (a workgroup machine, which is how most office Tally servers are set up) | 0 characters |
| Member server in a domain (from the Default Domain Policy) | 7 characters |
| Domain controller | 7 characters |
Zero means Windows will accept an account with no password at all. Windows does stop blank passwords from being used over the network by default (the “Accounts: Limit local account use of blank passwords to console logon only” setting), but a one-letter password is not blank, and Remote Desktop will accept it. Seven characters is not much better: a seven-character password made from a word and a year is near the top of every guessing list.
Why 15 characters
The US National Institute of Standards and Technology rewrote its password rules in 2025. NIST SP 800-63B-4 (section 3.1.1.2) says a password used on its own, with no second factor, must be at least 15 characters long. A password used only as part of multi-factor sign-in can be shorter, but never under 8. Most office servers reached over Remote Desktop have no second factor, so 15 is the number that applies.
The same document drops several rules that people still treat as best practice:
- No forced character mixes. Verifiers “SHALL NOT” demand a mix of upper case, numbers and symbols. Those rules push people towards predictable patterns such as a capital first letter and “@123” at the end.
- No forced change every 30 or 90 days. Change a password when there is a sign it has leaked, not on a calendar.
- Block the common and the breached. New passwords should be checked against a list of known, commonly used or leaked passwords.
- Allow long passwords and password managers. At least 64 characters should be allowed, and pasting from a password manager should work.
Length matters because of how passwords are actually broken. Over Remote Desktop, attackers guess online, working down lists of common passwords and patterns. If they get hold of the server’s stored password hashes, they guess offline on their own hardware, where nothing slows them down. In both cases each extra character multiplies the work, and a long passphrase of four or five unrelated words pushes it out of reach far more reliably than a short password with a symbol in it. Patterns like “Firm@2026” or “Tally@123” are what not to use: they meet the old complexity rules and are among the first things guessing tools try.
Check your current setting
Open Command Prompt or PowerShell on the server and run:
net accounts
Look for the line “Minimum password length”. This shows the rule for local accounts on that machine. If the server is joined to a domain, run the version below as well, because domain accounts follow the domain’s policy, not the local one:
net accounts /domain
Set 15 on a stand-alone server (Server 2022 or newer)
Windows historically capped this setting at 14. Newer versions can go higher, but only after you switch on a second setting called “Relax minimum password length limits”. Microsoft’s support article on minimum password length enforcement explains the change. The Group Policy path is:
Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy
- Sign in to the server as an administrator, press Windows + R, type
secpol.mscand press Enter. (On a stand-alone server, Local Security Policy edits the same settings as the path above.) - Go to Account Policies, then Password Policy.
- Open Relax minimum password length limits, choose Enabled and click OK.
- Open Minimum password length, enter 15 and click OK.
- Run
net accountsagain and confirm the new value. No restart is needed.
While you are there, you can leave “Password must meet complexity requirements” as it is if your IT vendor depends on it, but it is no longer what makes a password strong. Length and avoiding known-bad passwords do that.
On Server 2016 or 2019: 14 is the ceiling
Windows Server 2016 and 2019 can audit passwords longer than 14 characters but cannot enforce a minimum above 14; enforcement needs Windows Server version 2004 or later, according to the Microsoft article linked above. On those servers, set the minimum to 14 and ask staff to use passphrases of 15 characters or more anyway. The quickest way is:
net accounts /minpwlen:14
Windows Server 2016 also reaches the end of extended support on 12 January 2027. If your office server still runs it, the move to a newer version is due anyway; see why regular software updates matter.
If your server is in a domain
net accounts changes the password rules for local accounts on the machine where you run it. It does not change the rule for domain accounts. Those come from the Default Domain Policy on your domain controllers, and if you run net accounts on a domain controller, the Group Policy setting overwrites your change at the next policy refresh. To change the domain rule:
- On a domain controller, open Group Policy Management.
- Right-click Default Domain Policy and choose Edit.
- Go to
Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Password Policy. - Enable Relax minimum password length limits, then set Minimum password length to 15. Above 14 only works when every domain controller runs Server 2022 or newer; with older domain controllers, set 14.
Windows does not check new passwords against a list of leaked ones on its own. For domain accounts, Microsoft Entra Password Protection (a paid Microsoft Entra feature) can add a banned-password list; ask your IT vendor if you run a domain.
What changes for your staff
Raising the minimum does not lock anyone out. Existing passwords keep working; the new rule applies the next time each person sets a password. If you want everyone on the new rule now, tick “User must change password at next logon” for each account in Local Users and Groups (lusrmgr.msc) and give staff a day’s notice. Tell them a passphrase is fine, spaces included, and that writing it into a password manager beats writing it on a sticky note.
Length is one layer, not the whole wall
- Unique passwords. A 15-character password that is also used on a shopping site will turn up in someone else’s breach. See credential stuffing.
- Account lockout. It slows guessing, but the built-in Administrator is exempt on Server 2022 and older unless “Allow Administrator account lockout” is on. See account lockout policy.
- Do not leave Remote Desktop open to the internet. Put it behind Guard Secure Access, a VPN or an IP allow-list, as explained in how to restrict RDP access safely. Then a guessed password alone is not enough to reach the server.
- A second factor wherever you can. See two-factor authentication.
How Prixl Warden checks this
The password policy is one of the 29 checks in the Prixl Warden security audit, alongside account lockout, Remote Desktop exposure and the firewall. Warden’s audit flags anything under 10; we recommend 15. Warden also watches the server’s sign-in logs and emails you about brute-force patterns, both fast floods and slow, low-and-slow campaigns, so you see when someone is testing your passwords. The security audit guide shows where to find the result.
Start your 30-day free trial to run the audit on your own server.

