> 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/how-to-articles/disable-legacy-security-in-remote-desktop-manager.md).

# Désactiver l'ancienne sécurité dans Remote Desktop Manager

Désactivez l'ancienne sécurité et les groupes de sécurité dans Remote Desktop Manager après avoir d'abord migré les permissions existantes vers les groupes d'utilisateurs.

{% hint style="danger" %}
L'ancienne sécurité et les groupes de sécurité sont obsolètes et seront complètement retirés à partir de la version 2023.3 de Remote Desktop Manager.Avant de désactiver l'ancienne sécurité, il est conseillé de configurer les ***Groupes d'utilisateurs***. Voir [Migrer des groupes de sécurité vers les groupes d'utilisateurs](/rdm/fr/knowledge-base/how-to-articles/migrate-from-security-groups-legacy-to-user-groups.md).
{% endhint %}

Suivez les étapes ci-dessous pour désactiver l'***Ancienne sécurité*** dans Remote Desktop Manager.

1. Naviguez vers l'onglet ***Administration*** dans Remote Desktop Manager.
2. Sous la section ***Paramètres***, sélectionnez ***Paramètres système***.
3. Allez dans ***Gestion des coffres – Paramètres de sécurité – Sécurité*** et désactivez ***Utiliser l'ancienne sécurité***.
4. Cliquez sur ***Ok*** pour appliquer les modifications et fermer la fenêtre.


---

# 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/how-to-articles/disable-legacy-security-in-remote-desktop-manager.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.