Q

Can we have more than one password policy?

We have certain high-risk areas in our organization that would like to have their passwords expire at a more rapid rate than the rest of the organization (30 days vs. 90 days). My research has yielded some conflicting results, but I think that this cannot be accomplished easily (or at all) within a domain. Is there a straightforward way to accomplish this? Thanks.
As you have discovered, there can only be one password policy for a domain. Whatever you set for the password expiration will be in effect for all users, with the exception that you can set an account to not expire at all. There are two possible solutions to this problem.

First, you could create a separate domain for the high-risk areas, which would have other advantages as well, as they could manage other differences (length of password, history, account lockout, etc.). Second, while there is only one enforceable password expiration policy per domain, there is no reason they cannot procedurally insist on their group passwords being changed at whatever schedule. They also could write scripts to check...

on this and possible e-mail users who failed to follow the policy, or make some other change that would be effective in enforcing the policy. Of course, they might also write custom software to enforce more frequent password changing.

This was first published in April 2003

Dig deeper on User passwords and network permissions

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchVirtualDesktop

SearchWindowsServer

SearchExchange

Close