> 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-two-rd-session-hosts.md).

# Single Farm with Two RD Session Hosts

This scenario can be implemented by an organization that needs to load-balance published applications and desktops between two RD Session Hosts. For high availability, a secondary RAS Connection Broker and RAS Secure Gateway should be installed on the second server.

<figure><img src="https://content.gitbook.com/content/jRndoUJVjRrmCN0WR7H6/blobs/vTL9KKl6P45lQXkNXK8y/singlefarmwithtwordsessionhosts.png" alt="Single Farm with Two RD Session Hosts"><figcaption></figcaption></figure>

## **Installation Notes**

The components on the primary RD Session Host (where the primary RAS Connection Broker is installed) are installed using the Parallels RAS installer (standard installation).

The components on the secondary RD Session Host are push-installed from the RAS console.


---

# 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-two-rd-session-hosts.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.
