Limitations when monitoring Network Drives via WMI in Windows Monitors
Overview
When monitoring Windows systems via WMI, mapped network drives may not appear under Monitor Details → Disk Tab → Disk Utilization. This is because mapped drives are associated with a specific user's login session, and WMI queries executed under a different user context may not detect them. This behavior is expected due to the session-specific nature of mapped drives in Windows.
Limitation Details
Mapped network drives are linked to the user who sets them up during their login session. As a result:
- WMI queries executed under a different context (e.g., system account, service account, or administrator account) will not have access to drives mapped by another user.
- Even if the original user is logged in and the drive remains active, WMI typically cannot retrieve the drive details unless executed in the same user context.
Recommended Actions
To retrieve mapped network drive information via WMI:
- Run in User Context: Execute the WMI query using the same user account that mapped the network drive, since drive mappings are specific to a user session.
- Ensure User Is Logged In: Make sure the user is currently logged in, as mapped drives may not persist after logout.
- Grant Minimum Permissions: The user only needs read access to the network share; Full Control is not required for querying.
- Verify Drive Mapping: Before running the query, confirm that the drive is actively mapped (e.g., by using the net use command).
New to ADSelfService Plus?