Account lockout policy issue

I am having a software conflict with Active Directory lockout policy.  External users are login through the web site.  If the account policy enabled their accounts get locked out. Something weird how software reacts on that.  However, the issue is inconsistent.
What's the better way to test this?  Create test users and put into test OU or need test Security Groups? I think OU is easier to put test users there/ Not sure if possible to link that policy into that OU.
Please advise.
Thank you!
LVL 17
Tiras25Asked:
Who is Participating?
 
McKnifeCommented:
Yes, why not. PSOs can apply to groups and will override GPOs.
0
 
Sushant GulatiConsultantCommented:
You know the answer. Create a test OU, link that particular policy, add the user in that OU and test it and see what difference you will see.

Was there any change happened in your environment?
Was this working before? Or is the first time you are testing it?

What happens if the test account gets a domain admin privilege and then test it with enabled linked policy?

You can also use Account Lockout Status tool and keep this handy. Choose the domain and the name of the user to see the status of the user's account.

If this falls again then go ahead and check with the application vendor. I am not sure which application and how the users are logging in.

Let me know if anything else is required.

Good Luck..!!
~SG~
0
 
McKnifeCommented:
No, he does not know the answer :)
The account lockout policy is applied at the DC - not at the user themselves or at the users' computers - no testing possible unless you have a test domain.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
ThinkPaperIT ConsultantCommented:
***************
What's the better way to test this?  Create test users and put into test OU or need test Security Groups? I think OU is easier to put test users there/ Not sure if possible to link that policy into that OU.
*************

Easier to test by isolating the external users and putting the "external test" users in a different OU. And yes - you can apply GPO to an OU. But the first thing you should check is your account policy. You should also be looking at the authentication. Something's gotta be failing somewhere for the accounts to lockout. I'm thinking it could be a kerberos issue.
0
 
McKnifeCommented:
Sorry, but you are also misleading him. The account lockout policy cannot be applied to a test OU but only to the DC's OU because we are talking about domain users whose account info is kept only at the DCs.
0
 
Tiras25Author Commented:
Correct. This is what I understand.  The account lockout policy cannot be applied to a separate OU. However, even after testing successfully on test Domain I don't feel comfortable enabling on Production Domain.  
I am thinking implementing granularity by Security Group. Users in the Security Group will be enabled.  Does that sound good?
0
 
Sushant GulatiConsultantCommented:
If that's the case, I am waiting for the solution..!!

Interesting..!!
0
 
Tiras25Author Commented:
This is what I am thinking about.  Run the script every hour that would put those users in the group.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.