Solved

Account lockout policy issue

Posted on 2013-05-21
8
462 Views
Last Modified: 2013-06-07
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!
0
Comment
Question by:Tiras25
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 7

Expert Comment

by:susguperf
ID: 39186730
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
 
LVL 54

Assisted Solution

by:McKnife
McKnife earned 500 total points
ID: 39187259
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
 
LVL 16

Expert Comment

by:ThinkPaper
ID: 39187298
***************
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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 54

Assisted Solution

by:McKnife
McKnife earned 500 total points
ID: 39187434
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
 
LVL 17

Author Comment

by:Tiras25
ID: 39188236
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
 
LVL 7

Expert Comment

by:susguperf
ID: 39188566
If that's the case, I am waiting for the solution..!!

Interesting..!!
0
 
LVL 54

Accepted Solution

by:
McKnife earned 500 total points
ID: 39188905
Yes, why not. PSOs can apply to groups and will override GPOs.
0
 
LVL 17

Author Comment

by:Tiras25
ID: 39189024
This is what I am thinking about.  Run the script every hour that would put those users in the group.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A procedure for exporting installed hotfix details of remote computers using powershell
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question