> 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/gateway/getting-started/devolutions-server.md). # Devolutions Server Configure Devolutions Gateway for a Devolutions Server deployment, covering initial setup, Remote Desktop Manager integration, farms, and rulesets. This section covers how to bring Devolutions Gateway into a Devolutions Server deployment and configure it for day-to-day use. If you're setting up a gateway for the first time, [Devolutions Gateway configuration with Devolutions Server](/gateway/getting-started/devolutions-server/devolutions-gateway-configuration-with-devolutions-server.md) walks through the available installation methods and how to link the gateway to your Devolutions Server instance, while [Devolutions Gateway configuration in Remote Desktop Manager](/gateway/getting-started/devolutions-server/devolutions-gateway-configuration-in-remote-desktop-manager.md) covers pointing your sessions through it once it's in place. Once a gateway is running, [Devolutions Gateway farms](/gateway/getting-started/devolutions-server/devolutions-gateway-farms.md) cover grouping multiple gateways together for load balancing and high availability, and [Gateway ruleset configuration in Devolutions Server](/gateway/getting-started/devolutions-server/gateway-ruleset-configuration-in-devolutions-server.md) covers restricting and segmenting network access without needing a separate gateway instance. --- # 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/gateway/getting-started/devolutions-server.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.