If these audit settings enabled as failure we will get the following event id If these audit settings enabled as Success we will get the following event idsĤ624: An account was successfully logged onĤ647: User initiated logoff in the case of Interactive and RemoteInteractive (remote desktop) logons
Windows server 2008 security event viewer logon windows 7#
Subcategory: Logoff – ( In 2008 r2 or Windows 7 and later versions only) Subcategory: Logon – ( In 2008 r2 or Windows 7 and later versions only) In 2008 r2 and later versions and Windows 7 and later versions, this Audit logon events setting is extended into subcategory level.Ĭategory: Audit logon events (Logon/Logoff) The event 4624 is controlled by the audit policy setting Audit logon events. This will be 0 if no session key was requested. Key length indicates the length of the generated session key. Package name indicates which sub-protocol was used among the NTLM protocols. Transited services indicate which intermediate services have participated in this logon request. Logon GUID is a unique identifier that can be used to correlate this event with a KDC event. The authentication information fields provide detailed information about this specific logon request. Workstation name is not always available and may be left blank in some cases. The network fields indicate where a remote logon request originated. The New Logon fields indicate the account for whom the new logon was created, i.e. The most common types are 2 (interactive) and 3 (network). The logon type field indicates the kind of logon that occurred. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The subject fields indicate the account on the local system which requested the logon. It is generated on the computer that was accessed. This event is generated when a logon session is created. – The “anonymous” logon has been part of Windows domains for a long time–in short, it is the permission that allows other computers to find yours in the Network Neighborhood Event ID 4624 null sid An account was successfully logged on.
– The reason for the no network information is it is just local system activity. – Event 4624 null sid is the valid event but not the actual user’s logon event. After I have googled, I found following things Since it seams the entries for anonymous logon, I had started to analyze whether it has legitimate reason or it is filling up as unwanted. I have several of security log entries with the event 4624 followed shortly by an event 4634.