> 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/da/knowledge-base/troubleshooting-articles/microsoft-rdp-sessions-work-using-mstsc.exe-but-not-in-remote-desktop-manager.md).

# Microsoft RDP-sessioner virker med mstsc.exe, men ikke i Remote Desktop Manager

Microsoft RDP-sessioner, der opfører sig anderledes i Remote Desktop Manager end i mstsc.exe, diagnosticeres ved at sammenligne RDP-filer eller programversionen.

Dette emne beskriver fejlfindingstrinnene, når oprettelse af en session til en fjernvært reagerer anderledes i Remote Desktop Manager end **mstsc.exe**.

### Løsning

#### Sammenligning af vores indstillinger med en oprindelig rdp-fil

Når De bruger visningstilstanden Ekstern, opretter Remote Desktop Manager en midlertidig RDP-fil og kalder **mstsc.exe** med filen som parameter. Det kan være nyttigt at tage filen, mens den findes, og sammenligne den med en, der er oprettet med **mstsc.exe**.

1. Opret eller dupliker den session, De vil diagnosticere.
2. Sæt visningstilstanden til ***Ekstern***.
3. Start sessionen.

Filen slettes, når De lukker Remote Desktop Manager. De skal kopiere den inden da.

4. Åbn %TMP%\RDM, og kopiér Deres fil til en anden mappe.
5. Åbn filen i den editor, De foretrækker, og sammenlign den med en fil, der er oprettet med **mstsc.exe**.

#### Start af rdp-sessioner er langsom sammenlignet med den oprindelige rdp

Vi har isoleret problemet, og vi har rettet det ved at ændre Deres RDP-programversion til RDP 6.0 eller 7.0 under ***Fil – Indstillinger – Typer – Fjernskrivebord***.


---

# 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/da/knowledge-base/troubleshooting-articles/microsoft-rdp-sessions-work-using-mstsc.exe-but-not-in-remote-desktop-manager.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.