Return
-
Title
AD accounts not locking after bad attempts limit is reached -
Description
AD accounts not locking after bad attempts limit is reached
-
Cause
Bug 26011
* cache: The srvinfo joined domain entry was made without a timestamp, so next
call could remove it due to being 'expired'. This would be seen as requests
to AD not using one DC, instead following DNS responses and possibly random DC
for each per-process call. Noticed when users wouldn't lock out as the bad
attempts were spread amoungst various DCs -
Resolution
Upgrade to QAS 4.0.3 maintenance version. Please see the following link for a list of fixes and a link to the download:
https://support.quest.com/Search/SolutionDetail.aspx?id=SOL82767
-
Change Request
26011 -
Additional Information
Seen on QAS 4.0.3.91 version