> 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-windows-updates.md).

# How to Manage Windows Updates on Remote Desktop Servers

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

The section **Updates** of the Remote Desktop subscription lets you review, install, and schedule Windows updates for your servers without having to log into each machine.

This guide covers the basic workflow and the limitations you should keep in mind before automating.

> #### 👍 What you get
>
> Your Remote Desktop servers' Windows updates reviewed, installed, and scheduled from the dashboard, with usage windows respected.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions over 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/remote-desktop/quickstart.md)

### Step 1. Review and install pending updates

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. Open the tab **Updates** and wait for the platform to review the server's pending updates. If the subscription has several servers, first choose the server in the tabs with its name: checking, installation, and configuration are done server by server.

Review the list, select the ones you want to install (all with Select all, or by category, such as Definition updates; expand each category to see what it includes), and click **Install updates**. Before installing, review the Step 2 configuration: work hours limit when the server can be restarted automatically, but they do not schedule installation.

![List of pending updates in Updates](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fsp9hA0PtWddQZMSDFopd%2Fescritorio-remoto-windows-update-01.png?alt=media\&token=e103f366-d92c-47b8-8df0-0047695534c1)

### Step 2. Configure how they are applied

In **Updates**, open **Configuration** to define the server update policy.

#### 2.1 Automatic updates

Turn **automatic updates** on or off with the Windows updates switch, depending on the policy you want to apply to the server. If you turn them off, you keep control by installing manually from Step 1; if you turn them on, it's a good idea to set the work hours first.

![Enabling automatic updates](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F3WB71B471a7GjdUS3mca%2Fescritorio-remoto-windows-update-02.png?alt=media\&token=017aaa74-f025-48a6-8d5c-cf4e8dac2060)

#### 2.2 Work hours

Define the **work hours**: the time window during which the server is in use. They are defined in Active Hours Scheduling, with the From and To fields: during that window the platform does not automatically restart the server, and outside it, it notifies connected users 5 minutes before a restart. The window is saved in the time zone configured on the server. When you're ready, click **Apply** to save the policy.

![Scheduling work hours](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FRJJ6jUN1DExsqioQACAa%2Fescritorio-remoto-windows-update-03.png?alt=media\&token=316e8d57-e6c1-4586-8981-6aafee87fd92)

> #### 📘 Define work hours before automating
>
> If you're going to enable automatic updates on a server with connected users, set the work hours first. That's what prevents a restart due to an update from cutting off a session in the middle of the workday.

### Step 3. Follow the notifications

The platform shows confirmation messages when you apply configuration changes, and notifications when a server installation or update starts. Check them to confirm that everything is moving forward as expected.

![Update notifications](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FuaPNVjg88TIlYKSC6Odz%2Fescritorio-remoto-windows-update-04.png?alt=media\&token=a7e38dec-6a71-4d11-9f60-c707c40f4d03)

### Limitations to keep in mind

Before automating, keep these restrictions in mind:

> #### 🚧 Not available on domain-joined servers
>
> This feature is not available on Remote Desktop servers joined to a domain, to avoid conflicts with existing GPOs.
>
> On those servers, updates are managed from the domain policy. If you have domain-linked users, see [How to associate a Remote Desktop user with a domain user.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-associate-an-rd-user-with-a-domain-user.md)

> #### 📘 Two more limitations
>
> The dashboard list may not exactly match the one in the server's Windows Update application, because the platform queries the service API, not the local application.
>
> And the feature does not include updates for **drivers**: those you install manually if the server needs them.

### Conclusion

Managing Windows Update from the dashboard saves you from logging into each machine: you review what's pending, install what you choose, and set a policy with work hours so automatic updates don't interrupt anyone.

The two things to remember are to define the work hours properly before automating, and that this doesn't apply to domain-joined servers or cover drivers, which are handled separately.

With that, you keep servers up to date without surprises for users.

### Next steps

* Check the Updates section regularly to spot new pending updates.
* If your servers are domain-joined, manage updates from the domain policy instead of here.
* 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-windows-updates.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.
