> 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 is one of the classic friction points in a remote desktop: the document is generated on the server, but the printer is on the user's desk. 

Each mode solves that jump in a different way.

### 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 using TS Print software                      | Prints to any local printer without relying on the driver on the server | TS Print software on the user's computer        |
| Printer mapping   | Takes the user's local printers into the remote environment                                | That the user sees and prints 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 advisable to decide on printing and the connection method at the same time.

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

### Best practices

* If the printer fleet is varied or has driver issues, 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 out to all clients.

To choose the connection method, go to [Connection modes and compatibility.](/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 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/printing.md?ask=<question>&goal=<endgoal>
```

`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.