> 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 Update Updates on Remote Desktop Servers The section **Updates** of the Remote Desktop subscription lets you review, install, and schedule your servers' Windows updates without having to log into each machine. This guide covers the basic flow and the limitations to keep in mind before automating. > #### ๐Ÿ‘ What you get > > Your Remote Desktop servers' Windows updates reviewed, installed, and scheduled from the panel, respecting usage hours. ### Before you start * 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.](/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 **Updates** and wait for the platform to review the pending updates on the subscription's servers. Review the list, select the updates you want to install, and click **Install updates**. The installation runs with the configuration you define in the next step. {/\* ๐Ÿ“ธ SCREENSHOT 1 ยท Updates section ยท pending list and Install updates button \*/} ![Pending updates list in Updates](https://REEMPLAZA-URL/escritorio-remoto-updates-01.png) ### Step 2. Configure how they are applied In **Updates**, open **Settings** to define the server update policy. #### 2.1 Automatic updates Turn **automatic updates** on or off according to 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 configure working hours first. {/\* ๐Ÿ“ธ SCREENSHOT 2 ยท Settings ยท enable/disable automatic updates \*/} ![Enabling automatic updates](https://REEMPLAZA-URL/escritorio-remoto-updates-02.png) #### 2.2 Working hours Define the **working hours**: the time window when the server is in use. During those hours automatic updates are not installed, so you avoid reboots and interruptions in users' sessions. Once set, click **Apply changes** to save the policy. {/\* ๐Ÿ“ธ SCREENSHOT 3 ยท Settings ยท working hours window and Apply changes \*/} ![Scheduling working hours](https://REEMPLAZA-URL/escritorio-remoto-updates-03.png) > ๐Ÿ“˜ Define working hours before automating > > If you're going to enable automatic updates on a server with connected users, first configure the working hours. This is what prevents an update reboot from cutting off a session in the middle of the workday. ### Step 3. Follow the notifications The platform shows confirmation messages when you apply changes to the configuration, and notifications when a server installation or update starts. Review them to confirm that everything is moving forward as expected. {/\* ๐Ÿ“ธ SCREENSHOT 4 ยท confirmation and update process notifications \*/} ![Update notifications](https://REEMPLAZA-URL/escritorio-remoto-updates-04.png) ### Limitations to keep in mind Before automating, keep these restrictions in mind: > #### ๐Ÿšง Not available on domain-joined servers > > This functionality 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-associated users, you can see it in[ How to associate a Remote Desktop user with a domain user.](/docs-en/productos/remote-desktop/how-to/how-to-associate-an-rd-user-with-a-domain-user.md) > #### ๐Ÿ“˜ Two other limitations > > The panel list may not exactly match the Windows Update application on the server, because the platform queries the service API, not the local application. > > And the functionality does not include updates of **drivers or controllers**: these are installed manually if the server needs them. ### Conclusion Managing Windows Update from the panel saves you from logging into each machine: you review what's pending, install what you decide, and set a policy with working hours so automatic updates don't interrupt anyone. The two things to remember are to define the working hours well before automating, and that this does not apply to domain-joined servers nor does it cover drivers, which are handled separately. With that, you keep the servers up to date without surprises for users. ### Next steps * Review the Updates section periodically to detect 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.](/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 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/how-to/how-to-manage-windows-updates.md?ask=&goal= ``` `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.