> 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/knowledge-base/knowledge-base-articles/hp-ilo-entries.md). # HP iLO entries Compare HP iLO and HP iLO (web) entries in Remote Desktop Manager for accessing a servers remote console or a web-based management dashboard. ***HP iLO*** and ***HP iLO (web)*** entries are sometimes mistaken for one another despite boasting different features and functionalities. To help differentiate them, the entry types are located in different sections of the ***Add new entry*** window (***Remote connections*** and ***remote management and monitoring*** respectively). ### HP iLO ***HP iLO*** entries allow access to a server’s specific HP iLO remote console, granting remote control over the server regardless of its operating system or operating state. ### HP iLO (web) ***HP iLO (web)*** entries act as customized, enhanced dashboard session for HP iLO management pages. Users can access remote consoles from there as well, only with a more limited experience than if they were opened using an HP iLO entry directly. --- # 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/knowledge-base/knowledge-base-articles/hp-ilo-entries.md?ask=&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.