> 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/details/environment.md). # Environment A Remote Desktop environment runs on Windows servers in our infrastructure. Here are its query details. To understand the concept and decide how to set it up, go to [What is Remote Desktop?](/docs-en/productos/remote-desktop/concepts/what-it-is.md) ### What an environment includes An environment brings together five pieces. These are them, and where you manage each one. | Component | What it is | Where it is managed | | ------------- | --------------------------------------------------------------------- | --------------------------- | | Server (host) | Windows server that provides user sessions | Servers subscription | | Users | People with access, each with their connection method and permissions | Remote Desktop subscription | | Applications | Software published in the environment and assigned to each user | Remote Desktop subscription | | Licenses | Maximum number of users with an open session at the same time | Remote Desktop subscription | | Load balancer | Distributes sessions among servers in a multi-server environment | Remote Desktop subscription | ### The two subscriptions When we set up an environment, we create two subscriptions that work together. The division is simple: what the user sees and uses lives in one, and the server underneath lives in the other. > #### 📘 Do not create them separately > > The two subscriptions are generated at the same time when the environment is set up. You work with each one depending on the task, but they form a single environment. #### In the Remote Desktop subscription | Task | Detail | | ----------------- | --------------------------------------------------------------------------------------------- | | Users | Individual registration or bulk upload, and association with a domain user (Active Directory) | | Permissions | User or Administrator (the latter with Windows administrator permissions) | | Connection method | Application Launchpad or full desktop, per user | | Applications | Publish from the Marketplace or install via console, and assign them to users | | Licenses | Define the maximum number of concurrent users | | 2FA | Enable two-step verification per user | #### In the Servers subscription | Task | Detail | | --------- | ------------------------------------ | | Resources | Increase vCPU, RAM, and host disk | | Server | Restart and operate the host | | Network | Firewall, ports, and VPN | | Backup | Environment backups and restoration | | Scaling | Additional servers and load balancer | | Templates | Create and reuse server templates | ### Operating system The host is a **Windows Server** and maintenance is your responsibility. To make things easier, the panel includes **Windows Updates**, with these capabilities. | Windows Updates | Available | | -------------------------------------- | ----------------- | | Check updates | Yes | | Install updates | Yes | | Automate and schedule by working hours | Yes | | Pause updates | Yes | | Drivers | Not managed by it | | Servers joined to a domain | Not available | ### Architecture An environment grows with you: start with one server and add capacity when the load calls for it. | Topology | When it fits | Requires | | ------------ | ------------------------------------- | ----------------------------------------- | | One server | Starting point for most environments | Nothing extra | | Multi-server | More users or more load | One additional server and a load balancer | | Templates | Repeatable deployments across clients | A template created from a server | To translate users and applications into resources, go to [Size your environment.](/docs-en/productos/remote-desktop/concepts/size-your-environment.md) ### Resources and resizing The host resources are sized in the Servers subscription, where you have the specifications and storage in detail. What is useful to know at a glance. | Resource | Operation | Availability | | ------------ | --------- | --------------------------- | | vCPU and RAM | Increase | No downtime (see Servers) | | Disk | Increase | Direct | | Disk | Reduce | Manual process (not direct) | * Host specifications and storage: [Technical features (Servers).](/docs-en/productos/servers/details/technical-specs.md) ### Best practices * Size by the peak number of concurrent users, not by the total number of registered users: you pay for and measure simultaneous sessions. * If you set up similar environments for several clients, create a server template and reuse it so you do not have to repeat the configuration. * Plan the disk reduction in a maintenance window, because it is a manual and not immediate process. ### Known limitations | Limitation | Detail | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | Reduce disk | Increasing disk is direct, but reducing it requires a manual process (create a new disk, clone it, and set it as the system) | | Windows Updates in domain | The panel functionality is not available on servers joined to a domain | | Drivers | Windows Updates does not manage device drivers | --- # 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/details/environment.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.