Luke,

Try using just Logon Type:10 with the ( ) and then test the experssion with an example from the event log. Example:

Jason, thanks for the reply however I have tried this. In fact I made some progress but only on server 2k3. The above event IDs are for Server 2k8.

The logon event for 2k3 is 528, and RDP is Logon Type:10 in the description. If I do a Description = Logon Type:10 without using an expression it works perfectly. However using the same method with the Server 2008 Event IDs doesn't work. I think it's because in Server 2008 there is no longer a "Description". I have tried various expressions like

Logon Type:10, LogonType (10), (Logon Type:)(10), etc. When I do an express test some of them seem to resolve properly but the events never come through. Also, if I use the expressions "Logon Type:" without the quotes all logon types come through, if I put a number at the end like Logon Type:3, which is most of the events I don;t want to see, the events stop coming through. It must have something to do with Server 2008 and how it passes events?

I appreciate the help Jason

Luke,

Most of my servers are Windows Server 2008 R2 and I get the descriptions just fine. So, that should not be a problem. Would you be able to paste an example of the event you're trying to match the experssion on? (Omit any text for security reasons as you see fit)

Event 4624

An account was successfully logged on.

Subject:  Security ID:  SYSTEM  Account Name:  NOC-XX$  Account Domain:  XXXXXXX  Logon ID:  0x3e7

Logon Type:   10

New Logon:  Security ID:  xxxxxxx\xxxxxxx  Account Name:  XXXXXX  Account Domain:  XXXXXXXX  Logon ID:  0xbd25d20  Logon GUID:  {98762a3d-a8b0-a3d8-6ef2-3c9f113da824}

Process Information:  Process ID:  0x1808  Process Name:  C:\Windows\System32\winlogon.exe

Network Information:  Workstation Name: NOC-XX  Source Network Address: 10.0.0.10  Source Port:  16753

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

I just tried this as an expression and as a condition after Event ID = 4624, no luck, as soon as I remove the number 10 within the expression then all 4624 events come through

So if I replace the 10 with a 3 then all the Logon Type:3 events come through but only if there are the spaces. If I put in a 10 with spaces, nothing

Would you kindly post a screenshot of your config for this?

seems to be working now, no idea why, however the spaces are needed, thanks for the help Jason, greatly appreciated

Good to hear. I was just going to give you these: http://technet.microsoft.com/en-us/library/cc787567(v=ws.10).aspx

Leave it to Microsoft to put in a ridiculous amount of spaces between those two things :-)

@Luke what did you do to get it working.  I was testing it as well trying to figure it out.  I seem to be having the same problem, it never triggers.  even cut and pasted thelogon type: .. 10 from the event log itself and it still does not trigger.

Hi Paul, all I did was copy and paste the Logon Type: 10 with all the spaces

Yep I did the exact same thing but set it for Event ID 4624 for Windows 2008.  And I have yet to have it trigger

For Windows 2008, this worked for me:

Example e-mail I received:

Event Type: Audit Success
Event Source: Microsoft-Windows-Security-Auditing
Event Category: Logon
Event ID: 4624
User: Not specified
Computer: <hostname>
Description:An account was successfully logged on.

Subject:
Security ID: <SID>
Account Name: hostname$
Account Domain: domain

Logon ID: 0x3e7

Logon Type: 10

New Logon:
Security ID: <SID>
Account Name: <username>
Account Domain: <domain>
Logon ID: <loginID>
Logon GUID: <GUID>

Process Information:
Process ID: <PID>
Process Name: C:\Windows\System32\winlogon.exe

Network Information:
Workstation Name: <hostname>
Source Network Address: <Source IP>
Source Port: <Source Port>

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

I think I figured out why the event is not triggering in WUG.  WUG looks to not recieve any log events from the 2008 server even with the firewall turned off.  Now to troubleshoot that issue.

Strange.  Even the the firewall was turned off on the WUG server the service was still running.  This caused the problem.  Stopped the firewall service and the event logs started triggering.