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

# CyberArk richiede un motivo per connettersi dopo l'aggiornamento di Remote Desktop Manager

Risolva un prompt indesiderato Motivo della connessione nelle sessioni CyberArk dopo un aggiornamento di Remote Desktop Manager modificando i parametri utente di CyberArk.

Dopo l'aggiornamento di Remote Desktop Manager, gli utenti si trovano talvolta di fronte a un prompt indesiderato ***Reason (Optional)*** all'avvio delle voci di sessione CyberArk. Sebbene ciò si verifichi in Remote Desktop Manager, l'impostazione deve essere disabilitata in CyberArk.

### Soluzione

1. In CyberArk, apra le proprietà dei parametri utente per i componenti di connessione pertinenti (ad esempio, PSM-RDP).
2. Imposti entrambi i valori ***Visible*** e ***Required*** su ***No***, quindi salvi le modifiche.
3. Salvi le modifiche.
4. Riavvii Remote Desktop Manager o aggiorni lo spazio di lavoro che contiene la voce problematica.


---

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