> 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/how-to-manage-local-printers.md).

# How to Manage Your Printers with the Remote Desktop Environment

Review, install, and schedule Windows updates on your Remote Desktop servers from the Updates section, without entering the server.

The environment detects each user's local printers and maps them automatically.

From the section **Printers** of the subscription you review the print service status, restart it if needed, and define how Universal Printer behaves when printing. This guide walks you through those points.

> #### 👍 What you get
>
> The print service under control: its status at a glance, the option to restart it, and the Universal Printer behavior defined for your users.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have an active Remote Desktop subscription. If you don't have one yet, set it up with the [Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/servers/quickstart.md)

### Step 1. Open the Printers section

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. Open the tab **Printers**.

![Printers section of the Remote Desktop subscription](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-9c57ffd8cda977f9ca1dbbb28a0c4a3befb44b00%2FCAPTURA%201%20%C2%B7%20pesta%C3%B1a%20Printers%20de%20la%20suscripci%C3%B3n.jpg?alt=media)

### Step 2. Check the print service status

The service status is shown with a color indicator:

* **Started**: the service is available.
* **Retrieving service status**: the system is still checking it. It is usually temporary.
* **Stopped**: the service is not available.

If the status appears as **Stopped**, or stays on **Retrieving service status** for more than 20 seconds, click **Restart**.

![Print service status and Restart button](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-76d1d53db24d90874c05f5f24d28f673cd7737bd%2FCAPTURA%202%20%C2%B7%20indicador%20de%20estado%20del%20servicio%20y%20bot%C3%B3n%20Reiniciar.jpg?alt=media)

### Step 3. Configure Universal Printer

Direct mapping of local printers comes **disabled by default**. The recommended option is to manage printing from the **Universal Printer**.

> #### 📘 Why Universal Printer
>
> Universal Printer prints with a universal driver, without having to install each printer's driver on the server.
>
> That is why it is the recommended approach over direct mapping, especially if your printer fleet is varied. The printing modes and when each one is appropriate are in [Printing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/printing.md)

From the Universal Printer tab you can:

* Define its **default behavior** when printing:
  * Show the dialog box with the user's local printers so they can choose.
  * Print directly with the user's default printer.
* **Manage the print queue** when a document blocks Universal Printer's operation.

![Universal Printer behavior and print queue](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-564b91f2abe02c24643a70b52699bba0d0808fca%2FCAPTURA%203%20%C2%B7%20Universal%20Printer%20%C2%B7%20comportamiento%20por%20defecto%20y%20cola%20de%20impresi%C3%B3n.jpg?alt=media)

> #### 🚧 If printing gets stuck
>
> When a document leaves the queue blocked and Universal Printer stops responding, unblock it from queue management.
>
> It's the first thing to check before assuming the print service is down.

### Conclusion

The Printers section gives you control of the print service without going into the server: you can see its status, restart it if it stops, and define how Universal Printer behaves, which is the recommended method because it avoids installing drivers for each printer. Two useful habits for day-to-day use: restart the service if the status remains stopped or frozen for more than 20 seconds, and unblock the queue when a document blocks printing.

### Next steps

* Check how each user connects in [Connection modes.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md)
* Manage the rest of the environment from [How to manage your Remote Desktop environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-administer-your-remote-desktop.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/how-to-manage-local-printers.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.
