-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ADUserChangesDetailed Event ID 5139 reporting issues #68
Comments
The definition of 5139 says: Fields = [ordered] @{
'Computer' = 'Domain Controller'
'Action' = 'Action'
'OperationType' = 'Action Detail'
'Who' = 'Who'
'Date' = 'When'
'ObjectDN' = 'User Object'
'AttributeLDAPDisplayName' = 'Field Changed'
'AttributeValue' = 'Field Value'
# Common Fields
'RecordID' = 'Record ID'
'ID' = 'Event ID'
'GatheredFrom' = 'Gathered From'
'GatheredLogName' = 'Gathered LogName'
} The problem comes from expecting ObjectDN when actually for 5139 it's OldObjectDN and NewObjectDN.
While it's an easy fix for 5139 itself but ADUserChangeesDetailed focuses on 5136, 5137, 5139, 5141 and I wonder how to approach it to not break it for other events that most likely target ObjectDN |
I believe this fix should do it. Based on the logic of |
Awesome, thank you for the quick response! I will give the changes a go and report back later today. |
Yep, it works perfectly now. Thank you! |
When using Find-Events to generate a report from ADUserChangesDetailed it doesn't report anything in User Object, Field Changed, and Field Value fields.
If I use Get-Events to find the event on the DC manually it generates the fields as it's supposed to, so the data is there it's just not showing in the output table. This is specifically for event 5139.
The text was updated successfully, but these errors were encountered: