Moving over
What it takes
Keep the official client for RemoteApp and Azure Virtual Desktop; bring the plain machines over, where having the shell in the same window pays for itself immediately.
Microsoft's client does RDP properly, and so does Vandle - on a native surface, in the same window as everything else. The difference is what sits beside the desktop: the shell, the files and the web interface for that same machine.
Credit where it is due
The official client handles multi-monitor, RemoteApp and gateway scenarios that third-party clients quietly get wrong, and the protocol work behind it is first rate.
What changes
Side by side
| Aspect | Windows App and Microsoft Remote Desktop | Vandle |
|---|---|---|
| Protocols | RDP | RDP beside SSH, SFTP, WebDAV, the web and local shells |
| Inventory | One list of PCs and workspaces | One record per machine, one row per protocol |
| Routing | Gateway configuration | A route object per connection or per folder |
| Platforms | Windows, macOS, iOS, Android, web | Windows, Linux and macOS, from one codebase |
Moving over
Keep the official client for RemoteApp and Azure Virtual Desktop; bring the plain machines over, where having the shell in the same window pays for itself immediately.
And the rest of it
Replacing one tool gets you five. Whatever else that machine speaks is already a row on the same record - and every one of them takes the route you assigned.
Also compared