Taking into account Poor Bandwidth and Latency for Remote Desktop Services

This excellent article Dealing with Poor Bandwidth and Latency is an excellent article how Terminal Servers or Remote Desktop Servers should take into account poor bandwidth and latency for Remote Desktop Services. The factors highlighted in the articles include

  1. Changing packet acknowledgements timer
  2. Keepalives
  3. The use of QoS
  4. MTU and more…..

But that is just the Server side. You must also configure the Client portion to deal with High Latency Issue. You should try to update to RDP Client and make use of the new features. Among the many features is those that support High Latency Network

 

There are many ways to reduce the latency between the client and server. Will probably write on this soon.

Deploying Big-IP LTM with Microsoft Remote Desktop Services

If you are deploying  BIG-IP LTM with Microsoft Windows Server 2008 R2 Remote Desktop Services, you will find these articles useful for the deployment.

BIG-IP LTM Configuration

  1. Working with Trunks (From F5 Knowledge Base)
  2. Using Link Aggregation with Tagged VLANs  (F5 Knowledge Base)
  3.  Deploying the BIG-IP LTM with Microsoft Windows Server 2008 R2 Remote Desktop Services (pdf)

Microsoft Remote Desktop Services Connection Broker Essential Documentation relevant to Big-IP LTM

  1. Remote Desktop Connection Broker (Microsoft Technet)
  2. Overview of Remote Desktop Connection Broker (RD Connection Broker) (Microsoft Technet)
  3. Checklist: Create a Load-Balanced RD Session Host Server Farm by Using RD Connection Broker (Microsoft Technet)
  4. Install the RD Connection Broker Role Service (Microsoft Technet)
  5. Add Each RD Session Host Server in the Farm to the Session Broker Computers Local Group (Microsoft Technet)
  6. Configure an RD Session Host Server to Join a Farm in RD Connection Broker (Microsoft Technet)
  7. Configure DNS for RD Connection Broker Load Balancing (Microsoft Technet). Not Relevant as F5 will do the load balancing.
  8. About IP Address and Token Redirection (Microsoft Technet)
  9. About Dedicated Farm Redirection and Virtual Machine Redirection (Microsoft Technet).