Gateway Updates via Agent
Hi @paulcdejesus ,
Thanks for your interest. Here are the docs that cover updating Devolutions Gateway on Windows:
Overview of the three update methods (DVLS web interface, DVLS Console, auto-updater script): https://docs.devolutions.net/gateway/getting-started/devolutions-server/devolutions-gateway-configuration-with-devolutions-server
Updating remote Gateways and farms via Devolutions Agent, including the “Devolutions Gateway Updater” feature it needs: https://docs.devolutions.net/agent/
Bulk update in the Devolutions Server web interface (Administration – Devolutions Gateway): https://docs.devolutions.net/server/web-interface/administration/modules/gateway/
PowerShell auto-updater script, as an alternative without the Agent: https://docs.devolutions.net/powershell/devolutions-gateway-powershell/powershell-auto-updater-script-for-devolutions-gateway geometry dash
Docker deployments are upgraded by pulling the new image, since the methods above don’t apply to containers: https://docs.devolutions.net/gateway/getting-started/devolutions-gateway-configuration-in-docker
The Agent’s updater module also updates the Agent itself, so keeping it current is the best way to stay compatible with newer Gateway versions.
Best regards,
Stephan
@Stephan Haupt
Thank you, Stephan, for sharing these helpful documentation links and detailed instructions. I really appreciate your time and support!
Gateway Updates via Agent
Hey guys,
i just have a hypothetical question. when running our updates automatically via the agents, if said updates should fail.
talking about windows server btw, how is the gateway going to behave? or is this something that can vary from not working anymore to update simply does not get installed etc.
reason for the question is, we search the right time window to let the update run, without for example soft locking our emergency team out of access on 3:00 am.
maybe you guys have had some experiences in the past.
Best Regards,
Fabian
@Fabian-NeidlThanks for sharing this discussion. Updating gateways through the agent seems like a useful approach, especially when managing multiple devices. I think clear documentation about update procedures, compatibility, and possible connection issues would help users avoid unnecessary downtime. Has anyone tested this method across different gateway versions?