Our organization still relies on an older desktop client-server application with no web interface. It performs poorly over even modest latency, so traditional VPN access is not practical. The application also depends heavily on Microsoft Word and Outlook through COM add-ins—for example, generating emails, sending messages, and interacting with documents stored in the system. Users also need to download PDFs and other files.
We have tried publishing the application as a remote app through Citrix, but the integrations with locally installed Office applications make that approach unreliable. For now, users receive a complete Citrix desktop, which works but feels inefficient: they use relatively powerful laptops mainly as thin clients, the experience is confusing for some users, and it is not especially user-friendly.
Has anyone dealt with a similar legacy application? Are there better ways to provide remote access, or is a full remote desktop, VDI, or similar solution the only realistic option?
4 Answers
The practical answer is probably to keep the application and its integrations running near the server, then deliver the whole desktop through Citrix, RDS, or a similar VDI platform. RemoteApp becomes awkward when the program needs to interact with locally installed Word, Outlook, files, and other desktop components. It may not be elegant, but keeping everything in one controlled environment is usually the most reliable short-term compromise.
Long term, this is an application modernization problem rather than a remote-access problem. Windows 365 or hosted virtual desktops can make the current setup easier to operate, but they are still workarounds. If the software is business-critical, it is worth planning a replacement or migration to a web-based system before investing heavily in a large VDI environment that preserves the same limitations.
A simple setup is to give users lightweight laptops with only the VPN, RDP client, softphone, and browser they need. Their actual office desktop remains in the office, and they connect to it remotely. That keeps the application, Office integrations, and data on the same network while giving users a consistent desktop experience from anywhere.
Before choosing a platform, measure the application's latency tolerance. If it works acceptably at roughly 30–50 ms and the users are geographically close to the servers, RDP or a cloud-hosted desktop may be sufficient. If it fails at that level, the application and database need to be placed together in a nearby data center or cloud region, with the users connecting to that environment. Tunneling or changing the VPN will not fix an application that depends on very low-latency protocols such as SMB.
Exactly. Moving the desktop session closer to the application servers is more important than simply changing the remote-access product. If the application cannot tolerate normal WAN latency, a local or same-region virtual desktop is likely unavoidable.
Agreed. Remote desktop is a reasonable bridge, but spending heavily to preserve an application that is already at the end of its lifecycle may cost more than starting a replacement plan.