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

# CyberArk demande une raison de connexion après la mise à jour de Remote Desktop Manager

Corrigez une invite Raison de connexion indésirable sur les sessions CyberArk après une mise à jour de Remote Desktop Manager en ajustant les paramètres utilisateur de CyberArk.

Après la mise à jour de Remote Desktop Manager, les utilisateurs sont parfois confrontés à une invite ***Reason (Optional)*** indésirable lors du lancement d'entrées de session CyberArk. Bien que cela se produise dans Remote Desktop Manager, le paramètre doit être désactivé dans CyberArk.

### Solution

1. Dans CyberArk, ouvrez les propriétés des paramètres utilisateur pour les composants de connexion concernés (p. ex., PSM-RDP).
2. Définissez les valeurs ***Visible*** et ***Required*** à ***No***, puis enregistrez vos modifications.
3. Enregistrez vos modifications.
4. Redémarrez Remote Desktop Manager ou actualisez l'espace de travail qui contient l'entrée problématique.


---

# 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/fr/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.