> 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-additional-servers-multiserver.md).

# How to Deploy Additional Servers in Your Remote Desktop Environment (Multi-Server)

When a Remote Desktop environment needs more capacity, you don't have to rebuild it: you add another server and the environment becomes multiserver.

This guide covers deploying the new server from the panel and checking that it is up and running.

> #### 👍 What you get
>
> An additional server deployed and running in your Remote Desktop environment, ready to share the load with the rest.

### Before you start

* Access the admin panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have a Remote Desktop environment already active. If you don't have one yet, set it up with the [Remote Desktop Quick Start.](/docs-en/productos/remote-desktop/quickstart.md)
* Have users available in the organization to associate them with the environment and the applications.

### Step 1. Open the servers section

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and go into the environment subscription. From **Summary** you have the summary of users, applications, events and servers. Open the tab **Servers**, where you can see the environment servers and review each one's configuration (RAM, CPU). To add a new one, click **New Server**.

{/\* 📸 SCREENSHOT 1 · Servers tab · New Server button \*/}

![Servers section with the New Server button](https://REEMPLAZA-URL/escritorio-remoto-servidor-adicional-01.png)

### Step 2. Configure the new server

In the window, define the server's characteristics:

* **Server name**: the server name. The platform suggests a random one, but it is best to follow an agreed naming convention to make management easier.
* **Concurrent Users**: the number of users who will be able to use the environment simultaneously.
* **Region**: the region where it is deployed (for example, Spain or France).
* **Operating system**: the server OS.
* **Computing**: the computing capacity (CPU and RAM).
* **Disk**: the disk.
* **Standard network**: the standard network.

Under these options, the dropdown **Advanced options** shows the advanced network options. When you're done, click **Deploy server**.

{/\* 📸 SCREENSHOT 2 · New Server form with fields to fill in \*/}

![New server configuration](https://REEMPLAZA-URL/escritorio-remoto-servidor-adicional-02.png)

> 🚧 Concurrent Users affects billing
>
> The number of concurrent users you assign to the server affects what is billed. Size it according to the real usage peak, not excessively. 
>
> How to estimate that peak is in [Licensing and billing.](/docs-en/productos/remote-desktop/details/licensing-and-billing.md)

### Step 3. Check that the server is operational

During deployment you will see progress notices, and the new server appears with the status **deploying**. When it finishes, a notification pops up and the server appears as **operational**, with its indicator in green.

{/\* 📸 SCREENSHOT 3 · new server operational with green indicator \*/}

![Additional server operational in the environment](https://REEMPLAZA-URL/escritorio-remoto-servidor-adicional-03.png)

> #### 📘 While it is "deploying"
>
> The server takes a little while to be ready. Wait for the final notification and for the indicator to turn green before starting to assign users to it or linking it to the load balancer.

### Conclusion

Scaling an environment to multiserver means deploying one more server with the resources you need and waiting for it to go from "deploying" to green. The field to watch is Concurrent Users, because it determines both simultaneous capacity and billing.

With the server operational, the natural next step is to distribute the load among the servers with a load balancer.

### Next steps

* Distribute the connections among servers with the [load balancer](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Productos/servicios-cloud-escritorio-remoto/servicios-cloud-escritorio-remoto-how-to/servicios-cloud-escritorio-remoto-balanceador-carga/README.md).
* Register or assign users in bulk with the [bulk user upload](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Productos/servicios-cloud-escritorio-remoto/servicios-cloud-escritorio-remoto-how-to/servicios-cloud-escritorio-remoto-carga-masiva-usuarios/README.md).
* Review how to size by concurrent users in [Licensing and billing](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Productos/servicios-cloud-escritorio-remoto/servicios-cloud-escritorio-remoto-how-to/servicios-cloud-escritorio-remoto-licencias-facturacion/README.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-additional-servers-multiserver.md?ask=<question>&goal=<endgoal>
```

`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.