> 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/how-to-articles/hide-the-legacy-security-removal-warning-box-in-remote-desktop-manager.md).
# Ocultar el cuadro de advertencia de eliminación de seguridad heredada en Remote Desktop Manager
Edite manualmente el fichero de configuración de Remote Desktop Manager con un editor de texto para ocultar el cuadro de advertencia sobre la eliminación de la seguridad heredada.
{% hint style="danger" %}
La seguridad heredada ha quedado obsoleta y se eliminará por completo a partir de la versión 2023.3 de Remote Desktop Manager. Consulte [Desactivar la seguridad heredada en Remote Desktop Manager](/rdm/es/knowledge-base/how-to-articles/disable-legacy-security-in-remote-desktop-manager.md).
{% endhint %}
El cuadro de advertencia no se puede ocultar de forma permanente en la interfaz, pero existe una solución manual.
1. Cierre Remote Desktop Manager.
2. Vaya a la barra de búsqueda de Windows y escriba **%localappdata%**. Pulse Intro o haga clic en el resultado.
3. Vaya a **Devolutions\RemoteDesktopManager\RemoteDesktopManager.cfg**.
4. Edite **RemoteDesktopManager.cfg** con su editor de texto preferido.
5. Añada las siguientes líneas al fichero:
```
true
true
```
6. Guarde el fichero.
7. Abra Remote Desktop Manager.
El cuadro de advertencia sobre la eliminación de la seguridad heredada debería estar ahora oculto.
---
# 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/how-to-articles/hide-the-legacy-security-removal-warning-box-in-remote-desktop-manager.md?ask=&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.