The latency threshold for running a Terminal Server (RDS) over the WAN

colocationrdsthin-clientwindows-terminal-services

I've seen: Terminal server performance over high latency links

But I have a customer who is interested in relocating their system infrastructure to a datacenter that has ~62ms latency from their main headquarters.

The environment is comprised of a trio of Windows Server 2008 R2 RDS servers, file and print services and Microsoft Exchange 2010. It's all currently virtualized on a vSphere 5.5 cluster. There are 80 total users who currently connect locally to the RDS systems using HP thin clients.

Due to facility problems and an increase in offsite and remote users, there is a push to move the systems to a datacenter facility. The new site will feature higher-end vSphere hosts and all-flash storage.

Connectivity to the co-location facility will be established via site-to-site VPN with multiple ISPs and failover in place.

Is this a bad idea, though? I connect to this site often for maintenance work over RDP and SSH, performance is quite acceptable for my use case. The users are using the basic MS Office suite and a couple of lightweight SSH terminal-based ERP applications.

Is 62ms reasonable for this type of user load and Microsoft RDS?