> 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 Multi-Server Remote Desktop When a Remote Desktop environment grows to several servers, the load balancer distributes connections among them, instead of all landing on the same machine. This guide takes you from enabling it to linking the first server and leaving it operational. > #### 👍 What you get > > The balancer deployed in your multiserver environment, with at least one linked server and access to its operation options. ### Before you start * Access the admin 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.](/docs-en/productos/remote-desktop/quickstart.md) * Having more than one server in the environment. The balancer only makes sense in a multiserver environment. ### Step 1. Activate the balancer In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. Open the **Load balancer** menu **Activate** to start deployment. {/\* 📸 CAPTURE 1 · Load balancer tab · Activate button \*/} ![Load balancer section with the Activate button](https://REEMPLAZA-URL/escritorio-remoto-balanceador-01.png) ### Step 2. Configure and deploy Define the balancer options: * **Region**: the data center where it is provisioned. Use the same region where you deployed the servers. * **Network**: the network on which the balancer will work. * **Advanced options**: the balancing mode, by **connected users** or by the **server with the lowest RAM and CPU load**. Once you have it, click **Deploy**. {/\* 📸 CAPTURE 2 · balancer configuration · region, network, and advanced options \*/} ![Load balancer configuration](https://REEMPLAZA-URL/escritorio-remoto-balanceador-02.png) > #### 🚧 Same region as the servers > > Deploy the balancer in the same region as the servers in the environment. If they do not match, balancing will not work as it should. During deployment you see the connection string, a progress bar and the section **Events**, where you follow progress and review possible issues. > #### ❗️ It is billed even when stopped > > Once deployed, the load balancer is billed even if you stop it. Keep that in mind: to stop paying for it, it is not enough to stop it; you have to delete it. At the end, 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 first server With the balancer deployed but no servers assigned, click **Add Server**. In the window, select the server you are going to link and click **Add**. {/\* 📸 CAPTURE 3 · Add Server · selection of the server to link \*/} ![Linking a server to the balancer](https://REEMPLAZA-URL/escritorio-remoto-balanceador-03.png) The platform runs a series of **checks** to validate that the server is ready to connect to the balancer. If all validations come back green, click **Add**. {/\* 📸 CAPTURE 4 · server checks in green · confirm with Add \*/} ![Server checks before linking it](https://REEMPLAZA-URL/escritorio-remoto-balanceador-04.png) After a few minutes (the time varies depending on platform load), the server is added and the balancer becomes operational. From there you can manage the 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 balancer, repeat the linking with each one: **Add Server**, select, review the checks and **Add**. ### Conclusion Deploying the balancer in a multiserver environment is a short process: you activate it, configure it by choosing region, network and balancing mode, and link at least one server after its checks pass. Two things to keep in mind: that the balancer's region matches that of the servers, and that the service is billed even when stopped, so to stop paying for it you have to delete it. With one linked server and in green, the environment already distributes connections according to the mode you chose. ### Next steps * Manage the rest of the environment from [How to manage your Remote Desktop environment.](/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.](/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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-deploy-a-load-balancer-multiserver.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.