> 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/concepts/what-it-is.md).

# What Is Remote Desktop?

What a Remote Desktop environment is, how it fits into your customer's day-to-day, what you manage and what we manage, and how it's billed

Remote Desktop is a centralized, remote, and secure work environment. Your users access their applications and their desktop from anywhere and on any device, and you offer it to your client as a service managed by you.

### How it fits

The client no longer depends on local machines with everything installed. Applications and data live in the environment, and each employee accesses their workstation from the office, from home, or on the move, with the same experience. You decide what each user sees, which applications they use, and how they connect.

### What makes up an environment

A Remote Desktop environment brings together three pieces within a subscription:

* **Servers (hosts)**: one or more Windows servers that serve the sessions. You start with one and scale to multi-server when the load requires it.
* **Users**: the people in the organization you give access to, each with their connection mode and permissions.
* **Applications**: the software you publish in the environment and assign to each user.

### Two subscriptions for one environment

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-f320699b6b1f407dc687b31016c58a37e487b597%2Fdiagram-dos-suscripciones-er.png?alt=media" alt=""><figcaption></figcaption></figure>

* **Remote Desktop Subscription**: you manage users, permissions, connection modes, applications, and concurrent access licenses.
* **Server Subscription**: you manage the server underneath, with the tasks inherent to Servers: upgrades, restarts, firewall, and backups.

You centralize the day-to-day from the Remote Desktop card in the dashboard.

### What you manage and what we manage

Remote Desktop is a managed service, but the division is clear

| You manage                                                                                         | We manage                                                                              |
| -------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Users and access                                                                                   | The infrastructure on which the environment runs: virtualization, storage, and network |
| Applications you publish                                                                           | The data center and its physical security                                              |
| Environment data                                                                                   | The management tools integrated into the dashboard                                     |
| Server operating system: updates (with the Windows Updates feature in the dashboard) and antivirus |                                                                                        |
| Environment configuration: connection modes, permissions, and printing                             |                                                                                        |

> #### 📘 You handle the operating system
>
> As in Servers, the operating system of the hosts is your responsibility. We make the task easier with tools in the dashboard (for example, Windows Updates), but you decide and apply the OS updates and protection.

### How it's billed

Remote Desktop is billed by **concurrent users**: the number of users who can have a session open at the same time, not the total number of registered users. You can give access to more people than those who connect at the same time and size it according to that peak.

### Where to follow

* How your users connect: [Connection modes and permissions.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/connection-modes.md)
* How you register users and publish applications: [Users and applications.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/users-and-applications.md)
* How you choose the resources for the environment: [Size your environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/size-your-environment.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/concepts/what-it-is.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.
