Administrator accounts lockout

• Wednesday, February 20, 2013 1:24 PM

   

   
  

  0

  Have this Windows 7 Enterprise 64 bit client that locked both admin accounts.  Not sure what user did and event logs don't provide much help.

  Information 2/14/2013 4:08:23 AM Microsoft-Windows-Security-Auditing 4740 User Account Management "A user account was locked out.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  USS-GUBL06N$
   Account Domain:  WORKGROUP
   Logon ID:  0x3e7

  Account That Was Locked Out:
   Security ID:  S-1-5-21-1775545812-815017386-2178218503-1003
   Account Name:  buadmin

  Additional Information:
   Caller Computer Name: USS-GUBL06N"
  Information 2/14/2013 4:05:38 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  USS-GUBL06N$
   Account Domain:  WORKGROUP
   Logon ID:  0x3e7

  Logon Type:   5

  New Logon:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7
   Logon GUID:  {00000000-0000-0000-0000-000000000000}

  Process Information:
   Process ID:  0x20c
   Process Name:  C:\Windows\System32\services.exe

  Network Information:
   Workstation Name: 
   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 session is created. It is generated on the computer that was accessed.

  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 occurred. The most common types are 2 (interactive) and 3 (network).

  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

  The network 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.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - 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."
  Information 2/14/2013 4:05:38 AM Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7

  Privileges:  SeAssignPrimaryTokenPrivilege
     SeTcbPrivilege
     SeSecurityPrivilege
     SeTakeOwnershipPrivilege
     SeLoadDriverPrivilege
     SeBackupPrivilege
     SeRestorePrivilege
     SeDebugPrivilege
     SeAuditPrivilege
     SeSystemEnvironmentPrivilege
     SeImpersonatePrivilege"
  Information 2/14/2013 4:05:37 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  USS-GUBL06N$
   Account Domain:  WORKGROUP
   Logon ID:  0x3e7

  Logon Type:   5

  New Logon:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7
   Logon GUID:  {00000000-0000-0000-0000-000000000000}

  Process Information:
   Process ID:  0x20c
   Process Name:  C:\Windows\System32\services.exe

  Network Information:
   Workstation Name: 
   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 session is created. It is generated on the computer that was accessed.

  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 occurred. The most common types are 2 (interactive) and 3 (network).

  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

  The network 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.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - 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."
  Information 2/14/2013 4:05:37 AM Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7

  Privileges:  SeAssignPrimaryTokenPrivilege
     SeTcbPrivilege
     SeSecurityPrivilege
     SeTakeOwnershipPrivilege
     SeLoadDriverPrivilege
     SeBackupPrivilege
     SeRestorePrivilege
     SeDebugPrivilege
     SeAuditPrivilege
     SeSystemEnvironmentPrivilege
     SeImpersonatePrivilege"
  Information 2/14/2013 4:05:35 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

  Subject:
   Security ID:  S-1-0-0
   Account Name:  -
   Account Domain:  -
   Logon ID:  0x0

  Logon Type:   3

  New Logon:
   Security ID:  S-1-5-7
   Account Name:  ANONYMOUS LOGON
   Account Domain:  NT AUTHORITY
   Logon ID:  0x384e5
   Logon GUID:  {00000000-0000-0000-0000-000000000000}

  Process Information:
   Process ID:  0x0
   Process Name:  -

  Network Information:
   Workstation Name: 
   Source Network Address: -
   Source Port:  -

  Detailed Authentication Information:
   Logon Process:  NtLmSsp
   Authentication Package: NTLM
   Transited Services: -
   Package Name (NTLM only): NTLM V1
   Key Length:  0

  This event is generated when a logon session is created. It is generated on the computer that was accessed.

  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 occurred. The most common types are 2 (interactive) and 3 (network).

  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

  The network 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.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - 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."
  Information 2/14/2013 4:05:05 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  USS-GUBL06N$
   Account Domain:  WORKGROUP
   Logon ID:  0x3e7

  Logon Type:   5

  New Logon:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7
   Logon GUID:  {00000000-0000-0000-0000-000000000000}

  Process Information:
   Process ID:  0x20c
   Process Name:  C:\Windows\System32\services.exe

  Network Information:
   Workstation Name: 
   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 session is created. It is generated on the computer that was accessed.

  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 occurred. The most common types are 2 (interactive) and 3 (network).

  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

  The network 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.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - 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."
  Information 2/14/2013 4:05:05 AM Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7

  Privileges:  SeAssignPrimaryTokenPrivilege
     SeTcbPrivilege
     SeSecurityPrivilege
     SeTakeOwnershipPrivilege
     SeLoadDriverPrivilege
     SeBackupPrivilege
     SeRestorePrivilege
     SeDebugPrivilege
     SeAuditPrivilege
     SeSystemEnvironmentPrivilege
     SeImpersonatePrivilege"
  Information 2/14/2013 4:05:00 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

  Subject:
   Security ID:  S-1-5-18
   Account Name:  USS-GUBL06N$
   Account Domain:  WORKGROUP
   Logon ID:  0x3e7

  Logon Type:   5

  New Logon:
   Security ID:  S-1-5-18
   Account Name:  SYSTEM
   Account Domain:  NT AUTHORITY
   Logon ID:  0x3e7
   Logon GUID:  {00000000-0000-0000-0000-000000000000}

  Process Information:
   Process ID:  0x20c
   Process Name:  C:\Windows\System32\services.exe

  Network Information:
   Workstation Name: 
   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 session is created. It is generated on the computer that was accessed.

  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 occurred. The most common types are 2 (interactive) and 3 (network).

  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

  The network 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.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - 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."
  

  • Reply
  • Quote