Solved

Removing Domain Level Account Lockout Policy

Posted on 2006-11-16
12
1,339 Views
Last Modified: 2013-12-04
For some reasons I won't go into, I have removed the account lockout from the Default Domain policy.  I have done this by setting the account lockout threshold to "0" attempts.  This setting HAS replicated to my second DC, and I can see it in all areas, and on both servers.  Yet after 4 invalid login attempts by any user on the network, their account still locks out.

I have searched all over the net trying to find the cause, and can only find other people asking this same question, but with no answers.  There must be a setting that is being missed that is still enforcing this policy.

Any help would be appreciated.

Regards,

Rob
0
Comment
Question by:PC_Rob
12 Comments
 
LVL 48

Accepted Solution

by:
Jay_Jay70 earned 100 total points
ID: 17960707
the default domain controller policy probably has the settings applying
0
 
LVL 9

Author Comment

by:PC_Rob
ID: 17961715
I checked that on the PDC, and it shows the right setting.
0
 
LVL 4

Assisted Solution

by:StonewallJacoby
StonewallJacoby earned 100 total points
ID: 17961948
Over what period of time are we talking about having made these changes?  Changing the GPO on the server doesn't automatically update the workstations.  Have you run

gpupdate /force

from a command prompt on your XP Pro workstations?

If not this, then go to a workstation and run rsop.  From a command prompt on XP Pro, type mmc, then press enter.

File, Add/Remove snap-in, Add, scroll down to rsop, click add.  Close the "Add Standalone Snap-In" window.  Click OK in the Add / Remove Snap-In window.  RIght click on "Resultant Set of Policy"  Click "Generate RSoP data".  This will show you where all the GPO's on the local machine are coming from.
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 
LVL 9

Author Comment

by:PC_Rob
ID: 17965157
It has been 3 days since the change has been made on the servers.  One of the other servers I am testing with has been rebooted several times since then, and it still causes a lock out when I test it.

The server I am testing with is running Server 2000 and will not support RSoP.  I did run it on my local XP workstation, and the policy is showing correctly, yet if I type my password in wrong 4 times for testing, it locks me out.
0
 
LVL 38

Assisted Solution

by:Shift-3
Shift-3 earned 300 total points
ID: 17965422
I realize this is what you said in your first post, but just to confirm, you are setting this on the Domain Security Policy and not the Domain Controller Security Policy, correct?  Account policies only apply at the domain level; they have no effect if set on an OU.

Do you have any other GPOs applied at the domain level that might be conflicting?

Have you tried something like setting "Account lockout threshold" to 99 and "Reset account lockout counter after" to 1 minute?  This should prevent anyone from getting locked out.
0
 
LVL 38

Expert Comment

by:Shift-3
ID: 17965553
Ah, I take it back.  Apparently Account Lockout policies can apply to OUs.  I was thinking of Password Policies.
0
 
LVL 9

Author Comment

by:PC_Rob
ID: 17968334
Yes, it is actually on both the Domain controller policy and the domain security policy.

It is also on the default domain policy in AD.

Still locking out.

Thanks
0
 
LVL 9

Author Comment

by:PC_Rob
ID: 17988003
I re-verified everything, and my accounts are still locking out when I test them.  The policy is in place properly.

Any more ideas?

Thanks,

Rob
0
 
LVL 9

Author Comment

by:PC_Rob
ID: 18029940
I still never resolved this problem, but I got around it for now.

Thanks for the input.

Rob
0
 

Expert Comment

by:SHAX
ID: 23659705
I am having the same issue. I have opened a thread on expert exchange also.  The title is Account lockout policy is still being enforced after policy is removed.  I didn't know if anyone on this thread found anything out.

Thanks
0
 

Expert Comment

by:Daxtech Support
ID: 33250284
I am having same issue.   There is NO policy enabled anywhere and I have run gpupdate /force to update.  I have confirmed replication is fine between domain controllers.  Still users are locked out after three attempts.
0
 

Expert Comment

by:gwbmcse
ID: 33578203
Seems to be an epidemic... I too have this issue.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

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

No security measures warrant 100% as a "silver bullet". The truth is we also cannot assume anything but a defensive and vigilance posture. Adopt no trust by default and reveal in assumption. Only assume anonymity or invisibility in the reverse. Safe…
Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

832 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