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

# Different Printing Modes in Remote Desktop

Which printing mode (Universal Printer, TS Print, mapping, local printers) fits each connection mode to the environment.

Printing from a remote environment depends on **how each user connects**: not all printing methods work with all connection modes.

This guide relates both so you can choose correctly when setting up your users, and summarizes compatibility in a table.

### Compatibility at a glance

<figure><img src="https://files.readme.io/7052dcb0ba3240ffd8dedeec64fa34e485f4991fdcb59b5543777f645adfe360-table-er-print-compatibility.png" alt=""><figcaption></figcaption></figure>

> #### 📘 The only two incompatibilities
>
> Almost everything works together, but there are two exceptions worth remembering: **HTML5 does not support printer mapping**, and **RDP (Microsoft) does not support Universal Printer**.
>
> For those cases, choose another compatible option from the row.

### Connection modes

How the user enters the environment. You configure it in their profile, within the users section.

* **RemoteApp (Applications Launchpad)**: the applications run in the environment but are integrated with the user's computer almost as if they were local (you can move them between monitors, for example). Designed for Windows computers. Accessed through the user portal.
* **HTML5**: everything runs inside the browser. Slightly less integration with the local computer, but it's the ideal option for Mac, Linux, or Android. Also through the user portal.
* **RDP/RemoteApp Generator**: a direct connection from the user's desktop, without going through the portal.
* **RDP (Microsoft)**: a full desktop experience, with complete control over the environment. Accessed through the user portal.

### Printing methods

How the document gets from the server to the user's printer.

* **Universal Printer**: an intelligent printer driver that supports a wide range of printers. It shows a dialog box with the user's local printers or prints directly to their default one.
* **TS Print**: printing software for remote desktop environments. Requires purchasing its **specific license** and configuring it; the license is purchased through the Software Licenses subscription.
* **Printer mapping**: brings local printers into the environment using the drivers recognized by Microsoft. It is 100% dependent on that compatibility: if Microsoft recognizes the model, it shows it; if not, it does not appear.
* **Local printers**: by default, the environment shows the dialog box with the user's local printers when printing. It is compatible with all connection modes.

> #### 🚧 TS Print requires a license
>
> Unlike the others, TS Print is not available out of the box: it requires purchasing its license through the Software Licenses subscription and configuring it before use.

### Conclusion

Before deciding how a user prints, first look at how they connect: the connection mode is what limits the available printing methods.

The table clears up most questions at a glance, and you only need to remember the two exceptions (HTML5 without mapping, RDP without Universal Printer). For a mixed environment, Universal Printer is usually the safest bet because it does not depend on drivers; and if you need TS Print, plan for its separate license.

### Next steps

* Configure the behavior of Universal Printer and the service in [How to manage printers.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-manage-local-printers.md)
* Review the details of each method in [Printing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/printing.md)
* Define how each user connects in [Connection modes.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.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/printing-modes.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.
