Event Details
User Activity->Object Access->Active Directory Object Access->Windows 2000-2003->EventID 566 - Object Operation [Win 2003] - Failure
EventID 566 - Object Operation [Win 2003] - Failure
 Sample:
Event Type:     SuccessAudit
Event Source:   Security
Event Category: Directory Service Access
Event ID:       566
Date:           10/26/2009 12:00:00 AM
Time:           07:31:44
User:           NT AUTHORITY\SYSTEM
Computer:       DC1
Description:    
Object Operation:

	Object Server:	DS

	Operation Type:	Object Access

	Object Type:	{f30e3bc2-9ff0-11d1-b603-0000f80367c1}

	Object Name:	{8f3699fe-ab4e-4f57-ae1e-f5e37d55dbc5}

	Handle ID:	-

	Primary User Name:	DC1$

	Primary Domain:	RESEARCH

	Primary Logon ID:	(0x0,0x3E7)

	Client User Name:	DC1$

	Client Domain:	RESEARCH

	Client Logon ID:	(0x0,0x60FA64)

	Accesses:	Write Property
			

	Properties:
	Write Property
		{771727b1-31b8-4cdf-ae62-4fe39fadf89e}
			{bf967a76-0de6-11d0-a285-00aa003049e2}
	{f30e3bc2-9ff0-11d1-b603-0000f80367c1}


	Additional Info:	

	Additional Info2:	

	Access Mask:	0x20
Log Type: Windows Event Log
 Uniquely Identified By:
Log Name: Security
Filtering Field Equals to Value
OSVersion Windows 2003
Category DS Access
Source Security
EventId 566
Type Failure Audit
Field Matching
FieldDescriptionStored inSample Value
When At what date and time a user activity originated in the system. DateTime 12/14/2009 6:59:09 AM
Who Account or user name under which the activity occured. Client User Name DC1$
What The type of activity occurred (e.g. Logon, Password Changed, etc.) "AD Object Access Exercised" AD Object Access Exercised
Where The name of the workstation/server where the activity was logged. Computer DC1
Where From The name of the workstation/server where the activity was initiated from. - 10.10.10.10
Severity Specify the seriousness of the event. "High" High
WhoDomain Client Domain RESEARCH
WhereDomain -
Result Successful or Failed "Failed" Failed
Object Name Object Name {8f3699fe-ab4e-4f57-ae1e-f5e37d55dbc5}
Object Type Object Type {f30e3bc2-9ff0-11d1-b603-0000f80367c1}
Whom -
Comments
You must be logged in to comment