Hi everyone,
I wanted to share the slide deck from a highly relevant session that just took place at Engage 2026, titled “Desktop Sovereignty: A Decision Framework Beyond Windows 11,” presented by Bill Malchisky (@bill) , Daniel Nashed, and Martijn de Jong.
What happened in the session: The panel tackled the strategic crossroads many organizations are facing with the upcoming end of support for Windows 10. Instead of defaulting to a Windows 11 upgrade, which brings new governance and hardware challenges, they discussed how public sectors in France, Germany (Schleswig-Holstein), and Denmark are actively piloting and migrating to Linux and open-source alternatives.
Where ThinLinc fits into the architecture: For our community, the most interesting part is in the Technical Appendix. ThinLinc was explicitly featured as a key architectural solution under “desktop delivery and thin-client options”.
The presentation categorized ThinLinc as a model for “Linux remote desktop / server-based computing for central delivery”. The panel used this to validate a crucial architectural point: achieving desktop sovereignty does not require every single workload to live fully on every local endpoint.
Instead, the speakers noted that controlled centralized delivery models like ThinLinc allow organizations to:
-
Securely bridge legacy Windows dependencies via published apps or VDI approaches during a phased transition.
-
Prioritize supportability and strict data locality.
-
Reduce endpoint friction while still preserving a Linux-first or hybrid operating strategy.
It is great to see ThinLinc positioned not just as a remote access tool, but as a strategic enabler for organizations looking to regain operational control and break vendor lock-in.
I’ve attached the full slide deck for you to review. The specific references to delivery models and ThinLinc can be found in the technical appendix towards the end.
Would love to hear your thoughts on how you are seeing these sovereignty discussions play out in your own deployments!
Thanks @Bill!