Hi Buz.... thanks for your input, this is very true, and also as the
original poster has pointed out this is where they are trying to set the
policy, so it should all work ..... right?
The original issue is that they are setting password complexity at the
Domain Level in the Default Domain Policy and they can still set non complex
passwords, but they can also set other policies in the same Default Domain
Policy such as password expiration which does apply.
On the face of it this shows that the DD policy is getting applied, however
there would appear to be a problem with the complexity setting.
Since you can set a password policy anywhere you like it just doesn't get
applied at a domain level, it gets applied to the machine that is recieving
the policy, and will apply to the machine's local accounts database and not
the Domain one and also, I have come across issues in the past where a
conflicting setting in the DDC policy or another policy that applies to the
Domain Controllers has led to an inconsistant Password policy in the Domain.
Setting no override maybe a quick way to enforce the settings set in the DD
Policy as a troubleshooting step.
Any other suggestions that may help with the original problem?
Thanks
Jody