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

# Printing

Printing modes in the environment and their compatibility depending on the connection path.

Printing is one of the classic points of friction in a remote desktop: the document is generated on the server, but the printer is on the user's desk.

Each mode handles that step differently.

### Modes

| Mode              | How it works                                                                               | What problem it solves                                                    | Requires                                        |
| ----------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------- | ----------------------------------------------- |
| Universal Printer | Prints with a universal driver, without installing the manufacturer's driver on the server | Avoids installing and maintaining printer drivers in the environment      | Printer compatibility with the universal driver |
| TS Print          | Redirects the print job to the local computer via TS Print software                        | Prints to any local printer without depending on the driver on the server | TS Print software on the user's computer        |
| Printer mapping   | Brings the user's local printers into the remote environment                               | So that the user can see and print to their usual printers                | That the connection method supports mapping     |

### Why the connection method matters

The technical reason is that 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, so the mode that works in one case may not be available in another.

That is why it is best to decide on printing and the connection method at the same time.

For example: a user connecting via HTML5 from a Mac usually relies on a solution that does not depend on the local driver, while a user with a Windows client has more options for direct mapping.

### Best practices

* If the printer fleet is varied or has driver problems, consider Universal Printer or TS Print before direct mapping.
* Define printing together with the user's connection method, not afterward.
* Test printing with a pilot user before rolling it out to the entire client base.

To choose the connection method, go to [Connection modes and compatibility.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/connection-modes.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/details/printing.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.
