> 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 (Multiserver)

Learn how to deploy an additional server in your Plenit Remote Desktop (Multiserver) environment, validate that it's operational, and review the next steps.

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

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

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

### Before you begin

* Access the administration 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 yet have one, set it up with the [Remote Desktop Quick Start.](https://docs.plenit.com/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's servers and review each one's configuration (RAM, CPU). To add a new one, click **New Server**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-db5b5cc7b21332b343896c91db6ef0f5814c6189%2FCAPTURA%201%20%C2%B7%20pesta%C3%B1a%20Servers%20%C2%B7%20bot%C3%B3n%20New%20Server.jpg?alt=media" alt="Sección Servers con el botón New Server"><figcaption><p>Servers section with the New Server button</p></figcaption></figure>

### 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's OS.
* **Compute**: 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**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-1d4026f7d1b1e2755dce3dda085c0bf347923e81%2FCAPTURA%202%20%C2%B7%20formulario%20de%20New%20Server%20con%20los%20campos%20a%20rellenar.jpg?alt=media" alt="Configuración del nuevo servidor"><figcaption><p>New server configuration</p></figcaption></figure>

> 🚧 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 [Licenses and billing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/licensing-and-billing.md)

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

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

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-96778102949f3bb06769abbb767de0002252937d%2FCAPTURA%203%20%C2%B7%20servidor%20nuevo%20operativo%20con%20indicador%20en%20verde.jpg?alt=media" alt="Servidor adicional operativo en el entorno"><figcaption><p>Additional server operational in the environment</p></figcaption></figure>

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

### Conclusion

Scaling an environment to multi-server 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 the simultaneous capacity and the billing.

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

### Next steps

* Distribute 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 [mass user load](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 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-additional-servers-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.
