Computer Account Logon

Question

Hi, i have a quick question. How often does a "computer account" (not to confused with a user logon) logon against a DC? I've been reviewing security logs and i've noticed quite frequent computer account logins (4624). Those logon events do not correlate to the "lastLogon" value of the Computer Account object

Subject:
 Security ID: NULL SID
 Account Name: -
 Account Domain: -
 Logon ID: 0x0

Logon Type: 3

New Logon:
 Security ID: Domain\PC-102$
 Account Name: PC-102$
 Account Domain: Domain
 Logon ID: 0x61fe8f7ee
 Logon GUID: {86e8f2f4-eb16-50e6-0470-11525ea0d275}

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

Network Information:
 Workstation Name:
 Source Network Address: 192.168.253.66
 Source Port: 37776

Detailed Authentication Information:
 Logon Process: Kerberos
 Authentication Package: Kerberos
 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.

Answer 1

Hi Daizy,

Ok i retested this. You're right. The "LastLogon" value is updated when GPupdating or rebooting. The Gpupdate and Reboot also generates a 4768 "Kerberos Authentication Service" event for the Computer object. When a user logs on, then i get a 4768 "Kerberos Authentication Service" event for the User object AND a 4624 "Logon" event for both the User And Computer object. If the user provides wrong credentials, then i only get a 4771 "Kerberos Authentication Service" event for the User object. All the mentioned event are on the DC of course. Is that what im supposed be seeing? Can you elaborate on the 4624 event log for the Computer object?

I wish Microsoft has this documented somewhere...

Answer 2

Hi,
Is that what im supposed be seeing?

>>Yes, I think it is right.

Can you elaborate on the 4624 event log for the Computer object?

For computer object, I understand: it is the time that domain computer connected to DC and computer needs DC authenticate to the computer credential and this authentication is successful.

Answer 3

Hi,
If this question has any update or is this issue solved? Also, for the question, is there any other assistance we could provide?

Best Regards,
Daisy Zhou

Answer 4

Hi
How are things going on your end? Please keep me posted on this issue.
If you have any further questions or concerns about this question, please let us know.
I appreciate your time and efforts.

Best Regards,
Daisy Zhou