Hi Hilary_Braun
We at Accops have been delivering virtual app and virtual desktop feature for last 10+ years. We integrated mstsc activeX dll in our desktop app for Windows, providing centralized policy-based controls on how users can connect with Microsoft remote desktop services, running on-prem or on Azure or just any Windows machine running anywhere. We extended the MSTSC virtual channels by building value add features so that our global customers can keep users on virtual desktop infra.
Our customers are majorly based in India, MEA and Japan, including many Japanese universities.
Recently we posted an issue with Windows app for macOS where the Windows App is not supporting launching the client with a URI scheme which RemoteDesktopApp on macOS does.
Another issue we were hit with on macOS is about the custom URI scheme support on macOS. Currently Accops uses Microsoft's custom URI schema for RemoteDesktopApp directly from the browser to seamlessly connect to AVD virtual desktops. This is not yet supported on Windows App, leaving thousands of students not being able to seamlessly use AVD via Accops's ICT lab virtualization solution.
https://learn.microsoft.com/en-us/azure/virtual-desktop/uri-scheme
I highly recommend Microsoft to:
- Make the Windows App expose all features via APIs, for ISVs like us to enhance the VDI experience
- Make all features work in Windows App before EOL of Mstsc.exe
Vijender Yadav
CTO @ Accops