Solved

Terminal Server Bandwidth Requirements

Posted on 2008-06-18
2
6,115 Views
Last Modified: 2013-11-21
Looking to setup 10 users connecting via Terminal Services.
What is the recommended figure for bandwidth for each session?
Is there a way to figure out the bandwidth requirements for remote printing?
Is there an online calculator of some sort?

I realize that an exact estimate is not possible, but a general rule of thumb would be helpful.
0
Comment
Question by:bmsjeff
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 16

Accepted Solution

by:
gurutc earned 300 total points
ID: 21820961
Hi,

This really is a broad question, but there are some things to focus on.

First, Terminal Services is pretty asynchronous, meaning that each user won't be tying up their maximum needed bandwidth at the same time as the other users.  So you don't need 10 times the bandwidth for 10 users that you'd need for one.  Sometimes 3 or 4 times the one user requirement will work for 10 users.  Hmm, kind of like how Ethernet's functional bandwidth works, yeah...

Second, TS is asymmetrical, meaning that more data goes out to the clients than comes back from them.  A symmetrical connection at your central site is needed to send out the data to remote clients.  But you can get less costly asymmetrical connections at the remote sites.

Third, you want to support remote printing.  This is the biggest bugaboo, and will drive the bandwidth requirements you choose.  If you have two remote clients printing at the same time, and they're printing graphics, you could be looking at several megabytes of data going out, or up, through your net connection to your remote clients all at the same time.  This means that you have to have bandwidth to handle the printing.  Figure out how big your print jobs are and use that number to help size your bandwidth.

Lastly, the biggest thing is latency.  You want a fast connection.  Your remote users will complain about lag more than anything else.  Consider low latency just as much as high bandwidth.

Sorry none of these tells you any numbers, but I hope this helps you evaluate with more insight.

Good Luck,
- gurutc
0
 
LVL 29

Assisted Solution

by:Michael Worsham
Michael Worsham earned 200 total points
ID: 21822618
In addition to that gurutc has reviewed, another thing you need to watch for is the type of printers you wish to use via the terminal server environment. For best results and ease of configuration, stay away from all-in-one/multi-functional (MFC) printers and choose network based printers.

Also remember that using the Remote Desktop Client (RDC), heavy graphical-based applications (i.e. Adobe, Pagemaker) will perform sluggish as the RDC interface really isn't made to handle real-time screen refreshes of that graphical caliber.

I recommend reviewing this white paper, by Microsoft, on Remote Desktop Protocol (RDP) Features and Performance:
http://www.microsoft.com/technet/prodtechnol/Win2KTS/evaluate/featfunc/rdpfperf.mspx

Another thing you might want to look at is doing NIC teaming (if your system NICs support it -- i.e. Broadcom, 3Com, Intel). This way you can load balance your network interfaces to and from the box. I just recommend getting an additional 10/100/1000 network switch just in case one of the switches fails, so you still have network connectivity for the users.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Every system administrator encounters once in while in a problem where the solution seems to be a needle in haystack.  My needle was an anti-virus version causing problems with my Exchange server. I have an HP DL350 with Windows Server 2008 Stand…
The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box. This is what Event viewer showed after trying to start the WDS service:  An erro…
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers. Hopes this gives you ideas on visualizing your data in new ways ~ Create a calculated field in a query: …

632 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question