Users can connect to RemoteApp programs rather than a whole desktop. Personal desktops are assigned to users on basis and maintain state over time. Pooled desktops are shared between multiple users and all changes a user makes are typically rolled back when the user logs off. Users can subscribe to all their RemoteApp programs and desktops which are then listed in their local Start menu. The list is automatically updated as items are added or deleted.
A single system tray icon enables users to see all their remote connections. The user can disconnect all or individual connections using this icon. This improves the quality of the video and ensures that video and audio are always in sync. You can redirect audio recording devices such as microphones on the client computer. This is ideal for applications like Windows 7 voice recognition and applications that record audio. Remote Desktop Services now includes true multi-monitor support for up to 16 monitors.
It is not compatible with Aero Glass support. In an earlier version 0. This makes it easier to track all active connections and if necessary disconnect one by killing its process. We also wanted to avoid javascript libraries whenever possible and reasonable , to avoid useless and countless dependencies and keep the code low profiled. Javascript is a powerful language, constantly evolving, and I have fun learning and harnessing it. We had to rely on XmlHttp requests, long polling and divs HTML 4 , with of course different implementations in different browsers no typescript back then.
IE was still widely used at this time, so we wanted our PoC to run on the first version that supported XmlHttp, namely IE6 to add even more difficulty!
That said, that was before SignalR was available to abstract and simplify network communication automatic and transparent switching of protocols in case one of them is not available or fails. If Myrtille were to start today, I would of course make use of it in addition to a few other libraries.
Another thing I would do would be to use. NET core and the latest new stuff, in order to take Myrtille forward in the future and also have it on multiple platforms using xfreerdp on Linux, for example. This is planned in fact, and I could use some help for it any contribution is welcome! Among the upcoming features, file transfer is the next improvement goal. Microphone support is also planned. Maybe also smart cards after that.
A separation of the Myrtille gateway and services is also planned, for an easier configuration of the gateway into a DMZ, and further enhance the security the installer will allow to select the module to be installed; currently this must be done manually.
Still about security, I would like to offer another 2FA out of the box probably Google Authenticator. Regarding the user interface, I think Myrtille also needs a little visual rework. The login page, the toolbar will be redesigned with better flat styles, colors and icons. Myrtille already have a Docker image, but there are some limitations regarding print and audio. I will also look into that. Responsiveness is the key to a good user experience.
I tried hard to chase for every millisecond I could save in the roundtrip workflow. Whenever possible, I try to parallelize the processing. The user inputs and display updates, for example, are asynchronous. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen.
Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback.
0コメント