Hi, We have 3 main Domain Controllers and rest 10 RODC all Windows 2008 SP2. Recently we have changed our Administrator Password and after that we are facing issue like every second Administrator account is getting locked in our domain. In order to overcome we have tried few troubleshooting tips using MS Account locked out management tool like... 1. Collected the Event ID' 4629, 4644, 4776, 4771, and 4681 and identified from which computers it is getting locked. 2. Logged in to all those servers and changed it to different account under services logon. 3. After changing it was still getting locked frequency reduced, generated report for all Tasks running with Administrator account and changed the user account for all those also. But doing this, still Administrator account is getting locked on few servers among that few are domain controllers itself but can't trace anything particular what is causing the account locked. Attached below the Event Id's for more clarity... Event 1: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 7/2/2012 1:18:00 PM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: ADSBLR01.DOMAIN.LOCAL Description: An account failed to log on. Subject: Security ID: SYSTEM Account Name: ADSBLR01$ Account Domain: DOMAIN Logon ID: 0x3e7 Logon Type: 4 Account For Which Logon Failed: Security ID: NULL SID Account Name: Administrator Account Domain: DOMAIN Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc000006a Process Information: Caller Process ID: 0x178 Caller Process Name: C:\Windows\System32\svchost.exe Network Information: Workstation Name: ADSBLR01 Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2012-07-02T07:48:00.541Z" /> <EventRecordID>214431770</EventRecordID> <Correlation /> <Execution ProcessID="644" ThreadID="7308" /> <Channel>Security</Channel> <Computer>ADSBLR01.DOMAIN.LOCAL</Computer> Event 2: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 7/2/2012 12:15:44 PM Event ID: 4776 Task Category: Credential Validation Level: Information Keywords: Audit Failure User: N/A Computer: ADSAMI01.DOMAIN.LOCAL Description: The domain controller attempted to validate the credentials for an account. Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Logon Account: Administrator Source Workstation: Error Code: 0xc000006a Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /> <EventID>4776</EventID> <Version>0</Version> <Level>0</Level> <Task>14336</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2012-07-02T10:15:44.915Z" /> <EventRecordID>12697857</EventRecordID> <Correlation /> <Execution ProcessID="648" ThreadID="716" /> <Channel>Security</Channel> <Computer>ADSAMI01.DOMAIN.LOCAL</Computer> <Security /> </System> <EventData> <Data Name="PackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data> <Data Name="TargetUserName">Administrator</Data> <Data Name="Workstation"> </Data> <Data Name="Status">0xc000006a</Data> </EventData> </Event> Event 3: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 7/2/2012 12:15:44 PM Event ID: 4771 Task Category: Kerberos Authentication Service Level: Information Keywords: Audit Failure User: N/A Computer: ADSAMI01.AMICORP.LOCAL Description: Kerberos pre-authentication failed. Account Information: Security ID: AMICORP\Administrator Account Name: Administrator Service Information: Service Name: krbtgt/AMICORP Network Information: Client Address: ::ffff:10.40.12.78 Client Port: 60648 Additional Information: Ticket Options: 0x40810010 Failure Code: 0x18 Pre-Authentication Type: 2 Certificate Information: Certificate Issuer Name: Certificate Serial Number: Certificate Thumbprint: Certificate information is only provided if a certificate was used for pre-authentication. Pre-authentication types, ticket options and failure codes are defined in RFC 4120. If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /> <EventID>4771</EventID> <Version>0</Version> <Level>0</Level> <Task>14339</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2012-07-02T10:15:44.571Z" /> <EventRecordID>12697847</EventRecordID> <Correlation /> <Execution ProcessID="648" ThreadID="1548" /> <Channel>Security</Channel> <Computer>ADSAMI01.AMICORP.LOCAL</Computer> <Security /> </System> <EventData> <Data Name="TargetUserName">Administrator</Data> <Data Name="TargetSid">S-1-5-21-1084739015-3738900544-3817021857-500</Data> <Data Name="ServiceName">krbtgt/AMICORP</Data> <Data Name="TicketOptions">0x40810010</Data> <Data Name="Status">0x18</Data> <Data Name="PreAuthType">2</Data> <Data Name="IpAddress">::ffff:10.40.12.78</Data> <Data Name="IpPort">60648</Data> <Data Name="CertIssuerName"> </Data> <Data Name="CertSerialNumber"> </Data> <Data Name="CertThumbprint"> </Data> </EventData> </Event> I tired to capture the account lock out reason using ALockout.dll as described in the below link but text file is not getting generated. http://technet.microsoft.com/en-us/library/cc738772(WS.10).aspx Please let me know for any clarification or further information. Thanks,

Hi, Thanks for posting in Microsoft TechNet forums. Was the "ALockout.dll" tool installed properly? Were both the ALockout.dll and Appinit.reg files copied to the Systemroot\System32 folder? Did you run the .reg file and registrer the .dll file? If the tool can be installed, an ALockout.txt file shall be created in the Systemroot\Debug folder the next time the lock out occurs on this server. The issue can be caused by programs, service accounts or scheduled tasks which use the expired cached credentials. Regards Kevin

Hi, Thanks for posting in Microsoft TechNet forums. Was the "ALockout.dll" tool installed properly? Were both the ALockout.dll and Appinit.reg files copied to the Systemroot\System32 folder? Did you run the .reg file and registrer the .dll file? If the tool can be installed, an ALockout.txt file shall be created in the Systemroot\Debug folder the next time the lock out occurs on this server. The issue can be caused by programs, service accounts or scheduled tasks which use the expired cached credentials. Regards Kevin

Hi, tried again and it has generated the file with below mentioned text. Mon Jul 02 15:27:48 2012, PID: 7340, Thread: 7924, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - DLL_PROCESS_ATTACH Mon Jul 02 15:27:50 2012, PID: 7340, Thread: 7924, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - dll_process_detatch Mon Jul 02 15:27:57 2012, PID: 4032, Thread: 8152, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - DLL_PROCESS_ATTACH Mon Jul 02 15:28:02 2012, PID: 4032, Thread: 8152, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - dll_process_detatch Mon Jul 02 15:28:12 2012, PID: 5856, Thread: 6508, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - DLL_PROCESS_ATTACH Mon Jul 02 15:28:14 2012, PID: 5856, Thread: 6508, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - dll_process_detatch Anyone have any idea how to overcome this kind of account lock out issue. Or is there any other tool to get more detailed report. Thanks, Thanks, Vijesh Rajan

Hi, tried again and it has generated the file with below mentioned text. Mon Jul 02 15:27:48 2012, PID: 7340, Thread: 7924, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - DLL_PROCESS_ATTACH Mon Jul 02 15:27:50 2012, PID: 7340, Thread: 7924, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - dll_process_detatch Mon Jul 02 15:27:57 2012, PID: 4032, Thread: 8152, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - DLL_PROCESS_ATTACH Mon Jul 02 15:28:02 2012, PID: 4032, Thread: 8152, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - dll_process_detatch Mon Jul 02 15:28:12 2012, PID: 5856, Thread: 6508, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - DLL_PROCESS_ATTACH Mon Jul 02 15:28:14 2012, PID: 5856, Thread: 6508, Image C:\Windows\system32\regsvr32.exe,ALOCKOUT.DLL - dll_process_detatch Anyone have any idea how to overcome this kind of account lock out issue. Or is there any other tool to get more detailed report. Thanks, Thanks, Vijesh Rajan

Hi, Here are two articles which might be useful to you: Troubleshooting Account Lockout http://technet.microsoft.com/en-us/library/cc773155(WS.10).aspx Troubleshooting account lockout the PSS way http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx Also please check the problem servers to see whether they have DHCP roles or have any SQL server running. Regards Kevin

Hi, Here are two articles which might be useful to you: Troubleshooting Account Lockout http://technet.microsoft.com/en-us/library/cc773155(WS.10).aspx Troubleshooting account lockout the PSS way http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx Also please check the problem servers to see whether they have DHCP roles or have any SQL server running. Regards Kevin