> 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/es/knowledge-base/knowledge-base-articles/hp-ilo-entries.md).

# Entradas HP iLO

Compare las entradas HP iLO y HP iLO (web) en Remote Desktop Manager para acceder a la consola remota de un servidor o a un panel de gestión basado en web.

Las entradas ***HP iLO*** y ***HP iLO (web)*** a veces se confunden entre sí, a pesar de contar con funciones y funcionalidades diferentes. Para ayudar a diferenciarlas, los tipos de entrada se encuentran en secciones distintas de la ventana ***Añadir nueva entrada*** (***Conexiones remotas*** y ***gestión y supervisión remotas***, respectivamente).

### HP iLO

Las entradas ***HP iLO*** permiten acceder a la consola remota HP iLO específica de un servidor, otorgando control remoto sobre el servidor independientemente de su sistema operativo o estado de funcionamiento.

### HP iLO (web)

Las entradas ***HP iLO (web)*** actúan como una sesión de panel personalizada y mejorada para las páginas de gestión de HP iLO. Los usuarios también pueden acceder a consolas remotas desde ahí, aunque con una experiencia más limitada que si se abrieran directamente mediante una entrada HP iLO.


---

# 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/es/knowledge-base/knowledge-base-articles/hp-ilo-entries.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.