Our organization still relies on an older desktop application with a traditional client-server architecture. It does not perform well over latency, so VPN-based access is effectively unusable. The application also integrates heavily with Microsoft Word and Outlook through COM add-ins, including generating emails, sending messages, and exchanging documents such as PDFs.
We have tried publishing it as a remote application through Citrix, but those integrations and file transfers do not work reliably in that setup. For now, users receive a full Citrix desktop, which works but feels inefficient: they use reasonably powerful laptops mainly as thin clients, the experience is confusing, and local resources are mostly wasted.
Has anyone dealt with a similar legacy application? Are there better approaches, or is a complete remote desktop environment through Citrix, RDS, or a similar platform the only practical option until the application is replaced?
4 Answers
Before committing to a large virtual desktop rollout, measure the application's actual latency threshold and the distance between users, application servers, and the database. If it works at roughly 30–50 ms, placing application hosts closer to remote users may help. If it fails at that level, keeping the application session in the same facility or cloud region as the servers is likely required. Tunneling or moving the transport layer will not fix an application that relies on chatty file or database protocols.
Another common design is to leave each employee's physical desktop in the office and have them connect to it remotely. The home laptop only needs a VPN or secure access client, an RDP client, a softphone, and perhaps a browser for meetings. Users get the same desktop and application environment wherever they work, while the legacy software and its integrations stay on the office network.
Cloud-hosted desktops, such as Windows 365 or an Azure-hosted RDS environment, could reduce the burden of maintaining on-premises hardware. They still use the same remote desktop model, though, so they are an infrastructure change rather than a fix for the application's design. I would treat that as a temporary platform while planning a replacement or modernization project.
If the application cannot tolerate even modest latency and depends on local Office integrations, remote execution is probably the most realistic solution. RDS, Citrix, or a cloud desktop keeps the application, its database traffic, Word, and Outlook close together. A thin-client laptop with a remote desktop client is not unusual in this situation, even if it feels inelegant. The long-term answer is replacing or modernizing the application, but remote desktops are a reasonable bridge.
Protocols such as SMB can degrade badly over anything less than a very clean, low-latency connection, so network tunneling alone is unlikely to solve the underlying issue.