> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-reference-architecture/v21/deployment-scenarios/parallels-ras-deployment-scenarios/single-farm-with-one-rd-session-host.md).
# Single Farm with One RD Session Host
This scenario uses a single RD Session Host for publishing applications and desktops. SSL and User Portal are enabled by default with a self-signed server certificate. The server certificate should be trusted by client devices. Enterprise certificate or third-party trusted Certificate Authority can be used for external access (for details, please see the [**SSL Certificates**](/landing/ras-reference-architecture/v21/port-reference-and-ssl-certificates/ssl-certificates.md) section).
## **Installation Notes**
All server Parallels RAS components are installed using the Parallels RAS installer (standard installation).
Single server deployment is not recommended for production environments, as it does not provide high availability of service. Such deployment should be used for test or developer environments.
---
# 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.parallels.com/landing/ras-reference-architecture/v21/deployment-scenarios/parallels-ras-deployment-scenarios/single-farm-with-one-rd-session-host.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.
