Event Details
User Activity->Policy Changes->InTrust Plug-in for Active Directory->Failed Change Attempts->EventID 19 - Failed attempt to create Group Policy Object.
EventID 19 - Failed attempt to create Group Policy Object.
 Sample:
Event Type:     Warning
Event Source:   ITAD GPO Changes
Event Category: None
Event ID:       19
Date:           10/29/2009
Time:           07:06:50
User:           RESEARCH\DKrane
Computer:       DC1
Description:    
Failed attempt to create Group Policy Object.
	Client Computer : 10.0.0.2
	GPO GUID : {580BE62E-B15E-4EAE-81BA-0E1EDA8463D6}
	Failure Type : Access denied
	Request ID : {B5550854-415D-444F-8E2E-AF947C00F837}
===========================
Description template:
===========================
Failed attempt to create Group Policy Object.
   Client Computer : %3
   GPO GUID : %1
   Failure Type : %4
   Request ID : %2
Log Type: Windows Event Log
 Uniquely Identified By:
Log Name: InTrust for AD
Filtering Field Equals to Value
Source ITAD GPO Changes
EventId 19
Field Matching
FieldDescriptionStored inSample Value
When At what date and time a user activity originated in the system. DateTime 10.10.2000 19:00:00
Who Account or user name under which the activity occured. User RESEARCH\Alebovsky
What The type of activity occurred (e.g. Logon, Password Changed, etc.) "Attempt to create Group Policy Object" Attempt to create Group Policy Object
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. Client Computer 10.0.0.2
Severity Specify the seriousness of the event. "High" High
WhoDomain -
WhereDomain -
Policy Name The name of the affected policy. -
GPO Name The name of GPO where some policy was changed GPO GUID {580BE62E-B15E-4EAE-81BA-0E1EDA8463D6}
Value Before The policy value before the change -
Value After The policy value after the change -
Result Successful or Failed "Failed" Failed
Failure Reason The reason why the change request failed Failure Type Access denied
Comments
You must be logged in to comment