> 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/clear-cache-of-dell-idrac-entries-in-remote-desktop-manager.md).

# Vider le cache des entrées Dell iDRAC dans Remote Desktop Manager

Videz le cache des entrées Dell iDRAC dans Remote Desktop Manager à partir des paramètres de session Site Web de Microsoft Edge et de Google Chrome.

Le contrôleur Integrated Dell Remote Access Controller (iDRAC) assure une gestion sécurisée des serveurs sur place et à distance, ce qui permet aux administrateurs TI de déployer, de mettre à jour et de surveiller les serveurs PowerEdge en tout temps, où qu'ils soient. Le vidage du cache des entrées iDRAC peut être effectué pour Google Chrome et Microsoft Edge dans Remote Desktop Manager, puisqu'il est lié au même code.

1. Dans Remote Desktop Manager, allez à ***Fichier – Paramètres – Types – Sessions – Site Web***.
2. Dans les sections Microsoft Edge et/ou Google Chrome, cliquez sur ***Vider le cache***.
3. Une fenêtre contextuelle s'ouvre pour confirmer que le cache des entrées Dell iDrac a été vidé. Cliquez sur ***OK*** pour fermer la fenêtre.
4. Cliquez sur ***Enregistrer***.

Le cache des entrées Dell iDrac a été vidé.


---

# 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/clear-cache-of-dell-idrac-entries-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.