> 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/how-to-articles/configure-a-vpn-with-an-existing-remote-session.md).

# Configure a VPN with an existing remote session

Link an existing RDP entry to a VPN or Devolutions Gateway in Remote Desktop Manager to launch secure remote sessions automatically.

Follow this procedure to configure and launch secure remote sessions through a VPN or Devolutions Gateway in Remote Desktop Manager.

### VPN

You must first create a VPN entry, then do the following:

1. Select the RDP entry.
2. Go in the properties of your RDP entry, under ***VPN/Tunnel/Gateway***.
3. Set ***Connect*** to ***Always connect***.
4. Set ***Type*** to ***VPN link***.
5. Go under the ***Settings (VPN link)*** tab at the top.
6. Use the ellipsis (...) button to select the ***VPN*** entry you have created.
7. Click ***Update*** to save and close the window.
8. Launch your RDP entry which will first open the VPN you have configured to establish the connection.

### Devolutions Gateway

You must first install [Devolutions Gateway](https://docs.devolutions.net/gateway), then do the following:

1. Select the RDP entry.
2. Go back in the properties of your RDP entry, under ***VPN/Tunnel/Gateway***.
3. Set ***Type*** to ***Devolutions Gateway***.
4. Go under the ***Settings (Devolutions Gateway)*** tab at the top.
5. Use the ellipsis (...) button to select the Devolutions Gateway.
6. Click ***Update*** to save and close the window.
7. Launch the RDP entry, which will first open the Devolutions Gateway to establish the connection.

#### See also

[Youtube- RDM Quick Tip - Launch remote sessions via a VPN or a Devolutions Gateway](https://www.youtube.com/watch?v=xaC_7hYE33M)<br>


---

# 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/how-to-articles/configure-a-vpn-with-an-existing-remote-session.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.