you wouldn't want to set those type of password policies on a user by user basis. Those type of policies are set for the whole domain. i.e, maximum failed logins, lockout duration, etc.
These are the type of policies for everyone logging into the domain and not specific accounts logging into the domain.
I'm afraid that's the way it is with Active Directory, you can only set up password/account policies at the domain level. It's a grievance I have with AD to be honest as I, occasionally, would like to be able to have different password policies for different users.
Teknoratti, you are correct when you say that you would not want to set password policies on a user by user basis but the ability to do this on an OU would be good.
All you need in this life is ignorance and confidence; then success is sure.
- Mark Twain
I agree i've often wanted to apply stricter settings to a particular OU but it's just not possible, it's rumored to be a feature that will be included in Longhorn server but I'm not certain.
Andrew it seems you are ignoring what is being told to you here.
Password policies can only be set at the domain level. You can only have ONE password policy. Whether it is in the Computer or user portion of the GPO is irrelevent. You cannot do what you are looking to do with Windows 2003.
The reason it is in the Computer Policy is because the computer needs to block users from logging in if they don't satisfy the password requirements. In order for a user policy to take affect, the user must login.
If a user is required to change password at next login and chooses to cancel doing so, the computer will not let them log in. Were this in a user policy they would ALREADY be logged in, creating a security issue.
In beta 3 the plan is to introduce multiple passwords policies. These can be linked to individual users or security groups but currently are not planned to support OUs.
Password policies (account lockout and password specific settings like complexity) currently work at domain as well as OU level in LH build 6001. The setting is computer specific, so it relies on security filtering in the computer context and the link to the OU.
There are a couple of companies selling these - just do a search. I have been thinking about implementing one of these but have not gone back to do any real research on them yet.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.