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).
Related Reference
New to ADSelfService Plus?
Related Articles
Configuring non-admin user account for WMI monitoring
By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...Setting WMI access through Active Directory and Group Policy Object for non-admin user
In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...Windows Monitoring - FAQ
This Knowledge Base article provides answers to frequently asked questions related to Windows Server monitoring through WMI. The articles are categorized based on the monitoring lifecycle to help you quickly identify the relevant troubleshooting ...Troubleshooting Basic WMI Connection
Troubleshoot Basic WMI connectivity If you're using Applications Manager version 15470 or above, navigate to Admin > Self Help Tools and select the monitor type to troubleshoot the issue. Click here for more details. If you encounter an error in the ...Unable to Retrieve Data Through WMI Mode
Overview This article provides troubleshooting steps to identify and resolve data collection failures for Windows monitors configured in WMI mode. If one or more metrics are not being collected, the steps in this article will help determine whether ...