> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/wmi-troubleshooting.md).

# WMI troubleshooting

{% hint style="info" %}
Note that remote tools in RDP sessions will not work in Remote Desktop Manager if you do not have WMI. Consult this [guide on remote WMI](https://msdn.microsoft.com/en-us/library/aa389290.aspx).
{% endhint %}

In our environment, we basically run winrm quickconfig on all our machines. For those not joined to a domain, we also add them to the TrustedHosts list. For machines not joined to a domain, there is an added difficulty. If you are using the IP address instead of the host name, it definitely offers a few challenges.

A good strategy is to get remoteWMI to work, then integrate it in Remote Desktop Manager. We like to use [WMIC](https://msdn.microsoft.com/en-us/library/aa394531\(v=vs.85\).aspx).

{% hint style="info" %}
Please contact us at <service@devolutions.net> for more assistance.
{% endhint %}

### Problem 1

Access denied error.

#### Solution

Make sure that the user account has the necessary permissions to access a computer remotely. See [Securing a Remote WMI Connection (Windows)](https://docs.microsoft.com/fr-fr/windows/win32/wmisdk/securing-a-remote-wmi-connection?redirectedfrom=MSDN#setting_dcom_security_to_allow_a_user_to_access_a_computer_remotely).

You can also find troubleshoot tips in [WMI Troubleshooting (Windows)](https://docs.microsoft.com/en-us/windows/win32/wmisdk/wmi-troubleshooting?redirectedfrom=MSDN).

### Problem 2

Error getting products informations.

#### Solution

Invalid Class WMI or WMI class not found on Windows Server 2003. On Windows Server 2003, Win32\_Product is not enabled by default.

### Problem 3

Testing from a remote computer.

#### Solution

The WMIC command is used to test if you have access to the machine through WMI. You need to enter the following command: `wmic /NODE:"ComputerName" bios get serialnumber`

Below is an example with other credentials: `wmic /NODE:"ComputerName" /user:"username" /password:"password" bios get serialnumber`

### Problem 4

Load from System Information does not work. Error getting Bios information.

#### Solution

This error can have several origins. Please validate the following:

* Sessions must be RDP.
* The station must be on the same domain.
* The credentials must be in the ***Tools*** section of the session and be accurate.
* Test the WMI requests directly from the station to see if the communication is working.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/wmi-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.