Hello Devolutions Team,
we are deploying Remote Desktop Manager for Windows centrally through Microsoft Intune and WinGet.
The current WinGet package ID is:
Devolutions.RemoteDesktopManager
This works very well for installation and upgrades.
However, there is one challenge for enterprise environments using Devolutions Server:
According to the RDM / Devolutions Server compatibility model, the first two version segments need to remain compatible. For example, when our Devolutions Server is on the 2026.3.x release branch, we need to keep all RDM clients on the 2026.3.x branch as well.
We would like to automatically deploy maintenance releases such as:
2026.3.10
→ 2026.3.12
→ 2026.3.13
→ 2026.3.x
but prevent an automatic upgrade to another release branch such as:
2026.4.x
or:
2027.x.x
With the current WinGet package ID, there is no straightforward way for an enterprise administrator to define:
"Always update to the latest available 2026.3.x release, but never automatically cross the 2026.3 branch boundary."
This makes automated update mechanisms such as WinGet AutoUpdate difficult to use safely with RDM when Devolutions Server compatibility must be maintained.
Would you consider providing an officially supported release-channel mechanism for WinGet?
Possible approaches could be:
1. Separate WinGet package IDs for supported release branches, for example:
Devolutions.RemoteDesktopManager.2026.3
Devolutions.RemoteDesktopManager.2026.4
or
2. Another officially supported mechanism that allows enterprise administrators to pin RDM to a release branch while still automatically receiving maintenance releases within that branch.
Our ideal enterprise workflow would be:
Devolutions Server: 2026.3.x
RDM clients:
Automatically update to the latest 2026.3.x version.
When Devolutions Server is deliberately upgraded to the next compatible branch, the administrator would then move the clients to the corresponding new RDM release channel.
This would make RDM much easier to manage through Microsoft Intune, WinGet, WinGet AutoUpdate, and similar enterprise software-management solutions while maintaining the required server/client compatibility.
Thank you for considering this request.
Thank you.
Best regards, Johann