Can't seem to disable Windows 7 password complexity requirements

2

So, even though this is the security policy I set for one machine:

enter image description here

When trying to set passwords they still have to be over 16 characters and meet other various complexity requirements such as having a symbol.

The image used for this machine is Windows 7 Enterprise and not part of a domain (says workgroup is WORKGROUP, though it may have been on a domain at some point when the image was created), however I can't seem to disable the password requirements.

Additionally I've tried resetting the policy using the following commands:

RD /S /Q "%WinDir%\System32\GroupPolicyUsers"

RD /S /Q "%WinDir%\System32\GroupPolicy"

gpupdate /force

to no avail.

What am I missing here that still enforces password requirements?

Jane Panda

Posted 2013-09-13T16:24:16.390

Reputation: 1 089

Are you sure the users are not logging into the domain? The fact you are not adjusting the local policies seems strange – Ramhound – 2013-09-13T16:29:27.443

So it works on this machine? Why not show us a machine where you are having issues? – Austin T French – 2013-09-13T16:29:56.100

The machines are standalone and we're given an admin account to use on them. The settings don't seem to be working on this machine, I posted the image to show that the settings say something other than what's being enforced. – Jane Panda – 2013-09-13T17:02:04.643

@Ramhound Do you know an explicit way to tell if they are on a domain? When I try to join a domain it says it's on a workgroup and the domain circle isn't checked. – Jane Panda – 2013-09-13T18:23:17.507

@Bob - Why are they part of a workgroup if they are standalone? If the password requirements match the domain then ... I have to think about one. – Ramhound – 2013-09-13T18:38:28.337

They come that way, I wasn't aware you could have a Windows machine that doesn't specify either a workgroup (e.g. WORKGROUP) or domain. – Jane Panda – 2013-09-13T21:05:33.907

@Ramhound: Technically if they are in a WORKGROUP, they are "stand alones" aka NOT part of a domain. – surfasb – 2013-09-14T03:47:50.537

@surfasb - My experience of Workgroup is hooking Windows 98/95 machines together and thus they were noot standalone. – Ramhound – 2013-09-14T12:50:56.703

I said in the question they are standalones... Regardless, the issue here is really the password complexity requirements. I listed the workgroup information in case it would help. – Jane Panda – 2013-09-14T22:25:25.607

@Ramhound those are still standalone - a workgroup is nothing more than a shared identifier between machines, it doesn't actually link anything. The fact that a workgroup exists means they're not in a domain and thus standalone for these purposes. – Collin Grady – 2013-09-15T00:03:08.290

No answers