> 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/cyberark-prompts-for-reason-to-connect-after-remote-desktop-manager-update.md).

# CyberArk solicita un motivo para conectarse tras actualizar Remote Desktop Manager

Corrija una solicitud no deseada de motivo de conexión en sesiones de CyberArk tras una actualización de Remote Desktop Manager ajustando los parámetros de usuario de CyberArk.

Tras actualizar Remote Desktop Manager, los usuarios se encuentran a veces con una solicitud no deseada ***Reason (Optional)*** al iniciar entradas de sesión de CyberArk. Aunque esto ocurre en Remote Desktop Manager, la opción debe desactivarse en CyberArk.

### Solución

1. En CyberArk, abra las propiedades de los parámetros de usuario de los componentes de conexión correspondientes (p. ej., PSM-RDP).
2. Establezca los valores ***Visible*** y ***Required*** en ***No*** y guarde los cambios.
3. Guarde los cambios.
4. Reinicie Remote Desktop Manager o actualice el espacio de trabajo que contiene la entrada problemática.


---

# 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/cyberark-prompts-for-reason-to-connect-after-remote-desktop-manager-update.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.