> 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/faq.md).

# Frequently Asked Questions

Each answer links to the concept, guide, or reference where the detail is.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What it is and how it is billed</strong></td><td>What the environment is, its parts, the two subscriptions, and billing by concurrent users.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/concepts/how-we-bill-you.md">How We Bill You</a></td></tr><tr><td><strong>Users and connection</strong></td><td>What each user sees, how they connect, permissions, bulk onboarding, and 2FA.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md">Connection Modes</a></td></tr><tr><td><strong>Printing</strong></td><td>Printing options and why they depend on the connection mode.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/details/printing.md">Printing</a></td></tr><tr><td><strong>Environment backup</strong></td><td>How the backup is made and restored, and what it really protects.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/environment-access.md">Access to the Environment</a></td></tr></tbody></table>

### What it is and how it is billed

<details>

<summary>What is Remote Desktop?</summary>

It is a centralized, remote, and secure work environment: your users access their applications and desktop from anywhere and any device, and you offer it to your client as a service managed by you. The applications and data live in the environment, not on the local devices. More in [What is Remote Desktop?.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/what-it-is.md)

</details>

<details>

<summary>What makes up an environment?</summary>

Three components within a subscription: the Windows servers that serve the sessions (hosts), the users you give access to, and the applications you publish. You start with one server and grow to a multi-server setup when the load requires it.

</details>

<details>

<summary>Why are two subscriptions created?</summary>

When the environment is created, two subscriptions are automatically generated that work together: the Remote Desktop subscription (users, permissions, connection modes, applications, and licenses) and the Servers subscription (the underlying host, with scaling, reboots, firewall, and backups). You do not create them separately; they form a single environment. The details are in [The environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/environment.md)

</details>

<details>

<summary>How is it billed?</summary>

By concurrent users: those who can have a session open at the same time, not the total number of people registered. You can give access to more users than connect at the same time and size it according to the peak. For example, 50 employees, of whom at most 20 are connected at once, need 20 licenses. More in[ Licensing and billing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/licensing-and-billing.md)

</details>

<details>

<summary>What do I manage and what do you manage?</summary>

You manage the users and access, the applications, the environment data, the operating system of the hosts (updates with the Windows Updates feature in the control panel, and antivirus), and the environment configuration. We manage the infrastructure it runs on, the data center, and the management tools in the control panel.

</details>

### Users and connection

<details>

<summary>What does a user see when they log in?</summary>

You decide it per user: the Applications Launchpad (they see and open only the applications you publish for them, without a desktop) or the full desktop (a Windows desktop, as if it were their own computer). More in [Connection modes.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md)

</details>

<details>

<summary>How do users connect?</summary>

Three ways: RemoteApp (the applications integrate with the user's computer almost like local ones, designed for Windows), HTML5 (everything runs in the browser, ideal for Mac, Linux, or Android), and direct connection (RDP or RemoteApp without going through the portal). Which one fits each user is in [Connection modes.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md)

</details>

<details>

<summary>What permissions can I give?</summary>

Two levels: User (works with their applications and desktop) and Administrator (with Windows administrator permissions within the environment: install software, change settings, and manage the server).

</details>

<details>

<summary>Can I onboard users in bulk?</summary>

Yes, onboarding supports bulk upload as well as individual creation, and you can associate each user with a domain user. You have it in [The environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/environment.md)

</details>

<details>

<summary>Can I protect access with two-factor authentication?</summary>

Yes, you can enable two-step verification (2FA) per user from the Remote Desktop subscription.

</details>

### Printing

<details>

<summary>What printing options are there?</summary>

Universal Printer (universal driver, without installing the manufacturer's driver on the server), TS Print (redirects the job to the local computer with TS Print software), and printer mapping (brings the user's local printers into the environment). The details are in [Printing](https://docs.plenit.com/docs-en/productos/remote-desktop/details/printing.md).

</details>

<details>

<summary>Why does printing depend on how the user connects?</summary>

Because not all connection methods redirect local devices in the same way: a browser session (HTML5) does not expose local printers in the same way as a RemoteApp client. That is why it is best to decide on printing and the connection method at the same time, and to test with a pilot user before rolling it out to the entire client.

</details>

<details>

<summary>Which option should I choose if the printer fleet has driver issues?</summary>

If the fleet is varied or problematic, consider Universal Printer or TS Print before direct mapping, since they do not depend on the manufacturer's driver on the server.

</details>

### Environment backup

<details>

<summary>How do you back up a Remote Desktop environment?</summary>

It is managed from the associated Servers subscription, using the same backup model as the Servers product. For the concept, go to Backup and data protection; the environment's own data is in [Backup.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/backup.md)

</details>

<details>

<summary>Where do I restore a copy of the environment?</summary>

From the Servers subscription, in the Backup subsection: you choose the disk and the restore point, and the disk is restored on the server.

</details>

<details>

<summary>Does the backup guarantee that the service remains available?</summary>

No. A backup lets you return to a previous point, but it does not prevent downtime while you restore. It is your safety net, not a high-availability mechanism.

</details>

### Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quick Start</strong></td><td>Deploy your first environment step by step.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand the service design decisions.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides for setting up and managing Remote Desktop.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/how-to.md">How to</a></td></tr><tr><td><strong>Details</strong></td><td>The environment, licensing, and printing.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/details.md">Details</a></td></tr></tbody></table>


---

# 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/faq.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.
