> 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/update-all-duo-apps-and-clients-by-february-2-2026-to-avoid-service-disruption.md).

# Mettre à jour toutes les applis et tous les clients Duo avant le 2 février 2026 pour éviter une interruption de service

Mettez à jour Remote Desktop Manager et Devolutions Server pour rester compatible avec le nouveau lot d'épinglage d'autorité de certification de Duo et éviter les interruptions d'authentification.

Le 2 février 2026, Duo est passé à un nouveau lot d'épinglage d'autorité de certification (AC). Par conséquent, les utilisateurs de Remote Desktop Manager et de Devolutions Server qui utilisent l'authentification Duo pourraient rencontrer des erreurs de compatibilité.

{% hint style="info" %}
Consultez la [documentation de Duo](https://help.duo.com/s/article/9451?language=en_US) pour plus de détails.
{% endhint %}

### Solution

Pour assurer la continuité du service, mettez à jour vers les versions suivantes :

* Remote Desktop Manager Windows : 2025.3.29.0 ou plus récent
* Remote Desktop Manager macOS : 2025.3.29.0 ou plus récent
* Devolutions Server : 2025.3.14.0 ou plus récent. Pour demeurer sur la version 2025.2 de Devolutions Server, mettez à jour vers 2025.2.22.0 afin d'obtenir le correctif Duo.

Cela retirera également l'avertissement affiché dans la section ***Reports*** – ***Unsupported Clients Log*** du portail Duo.


---

# 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/update-all-duo-apps-and-clients-by-february-2-2026-to-avoid-service-disruption.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.