> 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/es/knowledge-base/troubleshooting-articles/lost-remote-desktop-manager-configuration.md).

# Configuración de Remote Desktop Manager perdida

La configuración perdida de Remote Desktop Manager con un panel de navegación vacío se soluciona creando un nuevo espacio de trabajo SQLite vinculado al fichero connections.db existente.

Ha perdido la configuración de su espacio de trabajo SQLite en Remote Desktop Manager y su árbol de navegación aparece vacío.

### Solución

1. Cree un nuevo espacio de trabajo SQLite en ***Fichero – Espacios de trabajo - Añadir nuevo espacio de trabajo***.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Para más información, consulte <a href="/rdm/es/getting-started/workspaces/create-a-workspace.md">Crear un espacio de trabajo</a>.</p></div>
2. Haga clic en el botón de puntos suspensivos y apúntelo al fichero ***connections.db***.
3. Finalice la configuración.

Ahora debería ver sus entradas en el ***panel de navegación***.


---

# 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/es/knowledge-base/troubleshooting-articles/lost-remote-desktop-manager-configuration.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.
