> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-deploy-a-load-balancer-multiserver.md).

# How to Deploy a Load Balancer in Remote Desktop Multiserver

Distribute connections across several servers in a multi-server environment by deploying the load balancer and linking the servers

When a Remote Desktop environment grows to several servers, the load balancer distributes connections among them instead of them all landing on the same machine.

This guide takes you from enabling it to linking the servers and getting it up and running.

> #### 👍 What you get
>
> The load balancer deployed in your multiserver environment, with at least one linked server and access to its operation options.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have an active Remote Desktop subscription. If you don't have one yet, set it up with [the Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md)
* Have more than one server in the environment. The load balancer only makes sense in a multiserver environment.

### Step 1. Activate the load balancer

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and open the environment subscription. Open the **Load balancer** tab and click **Activate** to start deployment.

![Load balancer section with the Activate button](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FJHfOE7X5Zp5V9HtP5cUV%2Fescritorio-remoto-balanceador-01.png?alt=media\&token=48640349-d250-4905-a8ca-ea539936dea8)

### Step 2. Configure and deploy

Define the load balancer options:

* **Location**: the data center where it is provisioned. It can be different from the servers' data center.
* **Select the network**: the network the load balancer will use.
* **Advanced options**: the load balancing mode: **For small number of connected users** (by number of connected users) or **Due to lower CPU and RAM occupancy** (based on lower CPU and RAM usage).

When you're ready, click **Deploy**.

![Load balancer configuration](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fyfx04VfEbLBzt9EDCFGl%2Fescritorio-remoto-balanceador-02.png?alt=media\&token=5315ad9b-1cf1-43d1-b37d-8a9654114423)

During deployment you will see the connection string, a progress bar, and the **Events**section, where you can follow the progress and review any issues.

> #### ❗️ It is billed even when stopped
>
> Once deployed, the load balancer is billed even if you stop it. Keep this in mind: to stop paying for it, it's not enough to stop it; you have to delete it.

When finished, you have the load balancer with its operational options: **Stop** (stops it), **Restart** (stop and start) and **Delete** (removes it from the environment).

### Step 3. Link the servers

With the load balancer deployed, in the Load balancer tab go to the **Select servers** section and select the servers you want to link to the load balancer.

![Select servers section of the load balancer](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F1ZFiD81hMrG5z3l4Y2Bi%2Fescritorio-remoto-balanceador-03.png?alt=media\&token=e386ad54-5023-42e2-baba-1e6c4a9d6927)

When you select each server, the platform performs a small **check** to validate that it has the same configuration as the rest of the cluster servers.

After a few minutes (the time varies depending on platform load), the servers are added and the load balancer becomes operational. From there you can manage the load balancer (restart, stop, or delete), check the server, add another one, or change the operating mode.

> #### 📘 Add more servers whenever you want
>
> To add more servers to the load balancer, select them in **Select servers**. Each server goes through its own check when you select it.

### Conclusion

Deploying the load balancer in a multiserver environment is a short process: you activate it, configure it by choosing the location, network, and load balancing mode, and link the servers, which go through a check when selected.

Keep in mind that the service is billed even when stopped, so to stop paying for it you must delete it.

With the servers linked, the environment now distributes connections according to the mode you chose.

### Next steps

* Manage the rest of the environment from [How to manage your Remote Desktop environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-administer-your-remote-desktop.md)
* Review how to size by concurrent users in [Licensing and billing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/licensing-and-billing.md)


---

# 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.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-deploy-a-load-balancer-multiserver.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.
