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

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.

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

📘 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.
Register or assign users in bulk with the mass user load.
Review how to size by concurrent users in Licensing and billing.
Last updated
Was this helpful?

