locked
windows server 2008 R2 terminal services (RDS) RRS feed

  • Question

  • We have a branch office who connects to a web service product at head office via internet explorer. They are saying the web service product is slow and what can be done to speed thing up. The latency between head office and branch office shop is around 300 ms.  We setup a windows server 2008 R2 Terminal services (RDS) with the trial license at head office on as a vmware server. They are saying it is around 1 second faster. I setup their Remote Desktop client in Windows 7 64 bit so the connection speed would be 56k but that is not helping. I figured the terminal services product hosted in the same network and same vmware server as the web services product would be faster as if they were sitting at head office but it seems like it is still fairly slow. Is there some type of compression I can turn on for the terminal services product or any suggestions how I could improve the response time by 2-3 seconds as a lot of screen for them can take 6-10 seconds to load depending on the screens when they run the web services directly from their machine.

    Also, are the graphic are rendered on the host computer (the RDP server) instead of on the client device, and the applications use the host’s GPU and CPU to run at full speed? The data on the screen is it then compressed then sent to the client pc by default?.  I need a solution where the experience is almost the same as running the applications on the local computer is running at head office.

    Would there be value with me upgrading this to windows server 2012 r2 standard edition?

    Any suggestions you may have would be appreciated.



    • Edited by bubba1984 Friday, March 11, 2016 12:14 AM
    Friday, March 11, 2016 12:00 AM

Answers

All replies