Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Troubleshooting > No user data retrieved via WMI (Windows Server 2003)

No user data retrieved via WMI (Windows Server 2003)

Table of contents
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Feb 02, 2017

Views: 23 Votes: 0 Revisions: 2

Issue

If you are running UDT on Windows Server 2003, 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 can connect to the remote AD controller but is unable to retrieve user data. Data retrieval is blocked by an implementation of the Custom Security Descriptor (CustomSD).

Solution

  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. Click Save.
 
Last modified

Tags

Classifications

Public