> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/server-os-deployment-guide/initial-server-setup/about-this-guide.md). # About This Guide ## EnGenius Server OS Deployment Guide This guide provides comprehensive, step-by-step instructions for setting up your EnGenius AI Server and deploying a supported operating system. It is structured into three main parts to walk you through the entire process, from initial hardware configuration to a fully operational OS. * Part 1: Initial Server Setup covers the foundational steps necessary to prepare your server. This includes connecting to the serial console, configuring essential BIOS settings, and accessing the Baseboard Management Controller (BMC) to mount installation media. * Part 2: Operating System Installation offers detailed deployment guides for three major operating systems: Windows Server, Ubuntu Server, and Red Hat Enterprise Linux (RHEL). Each chapter provides specific instructions tailored to that OS. * Part 3: Appendix provides supplementary information, including a troubleshooting guide for common issues and a glossary of key terms used throughout this manual. --- # 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://doc.engenius.ai/server-os-deployment-guide/initial-server-setup/about-this-guide.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.