Accidentally stumbled on this and not sure what problem you're solving: not wanting to type the server name into the `mstsc.exe` window? Not having to re-type credentials across connections?
I have a few servers and workstations I tend to connect to several times a day for work, also occasionally I'll remote back to my home PC when at the office.
These connections belong to different clients and have different gateway or specific settings I like to use. Most of the issues can be resolved by simply having a dedicated folder with the `.rdp` files in them, but some of the servers I connect to have short session timeouts, which make it more difficult than it needs to be to be productive. The app launches Devolutions `mstscex.exe` which provides a 'MouseJiggler' feature which tries to keep the session active. (I've opted to pass args to the binary instead of associating Devolutions `mstscex.exe` with `.rdp` files.)
Self-managing the `.rdp` files could also mean that in the future I could implement encryption of those files to make it safer to carry around on a `USB drive` without fear of loosing it etc.
Apart from that, it's also nice to be able to launch `Meld RDP` and simply press `Ctrl+3` to connect to the 3rd connection for instance. :-)
Accidentally stumbled on this and not sure what problem you're solving: not wanting to type the server name into the `mstsc.exe` window? Not having to re-type credentials across connections?
I have a few servers and workstations I tend to connect to several times a day for work, also occasionally I'll remote back to my home PC when at the office.
These connections belong to different clients and have different gateway or specific settings I like to use. Most of the issues can be resolved by simply having a dedicated folder with the `.rdp` files in them, but some of the servers I connect to have short session timeouts, which make it more difficult than it needs to be to be productive. The app launches Devolutions `mstscex.exe` which provides a 'MouseJiggler' feature which tries to keep the session active. (I've opted to pass args to the binary instead of associating Devolutions `mstscex.exe` with `.rdp` files.)
Self-managing the `.rdp` files could also mean that in the future I could implement encryption of those files to make it safer to carry around on a `USB drive` without fear of loosing it etc.
Apart from that, it's also nice to be able to launch `Meld RDP` and simply press `Ctrl+3` to connect to the 3rd connection for instance. :-)