You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your script which avoided me having to delve too deep in SDDL :)
When using the script to set audit rules for "Read Property" on two specific attributes of an AD object with the -AttributeGUID parameter, the script overwrite the first one with the second one instead of adding both.
Using $Acl.AddAuditRule($AuditRuleObject) instead of $Acl.SetAuditRule($AuditRuleObject) on line 272 correctly adds two rules, but I don't know the impact on other use cases.
Example:
I want to add an audit rule on attributes member and memberOf of AdminSDHolder (which is not possible via GUI because AdminSDHolder is of type container and this type does not have these attributes). These rules will be propagated by SDProp to e.g. Domain Admins (group) or Administrator (user).
Hello,
Thanks for your script which avoided me having to delve too deep in SDDL :)
When using the script to set audit rules for "Read Property" on two specific attributes of an AD object with the
-AttributeGUID
parameter, the script overwrite the first one with the second one instead of adding both.Using
$Acl.AddAuditRule($AuditRuleObject)
instead of$Acl.SetAuditRule($AuditRuleObject)
on line 272 correctly adds two rules, but I don't know the impact on other use cases.Example:
I want to add an audit rule on attributes
member
andmemberOf
ofAdminSDHolder
(which is not possible via GUI becauseAdminSDHolder
is of type container and this type does not have these attributes). These rules will be propagated by SDProp to e.g. Domain Admins (group) or Administrator (user).Instead, when adding the rules with
$Acl.AddAuditRule($AuditRuleObject)
:The text was updated successfully, but these errors were encountered: