SolarWinds UDT - No User Data Retrieved Via WMI (Windows Server 2003); UDT Not Receiving User Data from Domain Controllers; Event Code Setup

No User Data Retrieved Via WMI (Windows Server 2003)
Issue
If you are running UDT on Windows Server 2003, and setup WMI retrieval of user data
from a Active Directory domain controller outside of the local UDT server's domain,
and using an account with limited permissions, UDT is able to connect to the remote
AD controller but does not retrieve user data. Data retrieval is blocked by an
implementation of the Custom Security Descriptor (CustomSD).
Solution
The only identified workaround involves a registry edit on the domain controller, as
follows:
1.
Open RegEdit from the Run line.
2.
Locate the CustomSD key (KEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security)
3.
Add to the existing string the extra ACL: (A;;0x1;;;S-1-5-32-573).
4.
Save and exit.
UDT Not Receiving User Data from Domain Controllers
Issue
UDT credentials are managing relevant domain controllers and the credentials for
accessing them are valid. AD polling, however, is not working.
Solution
In some cases this problem has been traced to the wrong event codes being
generated on the domain controller(s). UDT cannot display any user related data
without event codes 4768/4769 and without a result code of 0x0; any other event or
result codes result in UDT ignoring the log data.
Event code setup
Use Group Policy Manager to review and edit the default local policy on the domain
controller(s). Check that the "Audit account logon events" policy is enabled on the
domain controller; since event 4768 belongs to this category.
355
No User Data Retrieved Via WMI (Windows Server 2003)