> 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/knowledge-base-articles/load-from-system-information.md).

# Load from system information

Use the Load from system information feature in Remote Desktop Manager to view entry configuration details on remote computers via RDP and WMI.

***The load from system information*** feature allows you to view the configuration of an entry, which is useful if you have a large number of computers.

The feature can be found by right-clicking on an entry and going to ***Properties*** – ***Asset*** – ***Load from system information***.

### Supported Linux type

* Ubuntu
* Debian

### Error Bios information

* 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.

### Error getting products information

Invalid Class WMI or WMI class is not found on Windows Server 2003. On Windows Server 2003, Win32\_Product is not enabled by default. Learn more about [Win32\_Product class](https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/aa394378\(v=vs.85\)).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/load-from-system-information.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.