Terminal Services Bandwidth

[DomRCS]

Hi,

I administer a small server farm running Windows 2003 server. We currently have about 15-20 users on the internal network and 1 or 2 offsite users getting in via DynDNS. We've had no complaints attributed to bandwidth issues.

A decision has been made to add about 40 offsite users to the server, we have a 640kbps upload line coming in (practical tests show around 450kbps upload). We're trying to gauge the impact on the upload bandwidth when we implement the changes and allow access to those 40 offsite users.
Does anyone have any idea on the bandwidth requirements per client coming in?
Does anyone administer this type of setup, or have any idea how much bandwidth 40 users would take?

Thanks in advance

 

[itsp1965]

I think TS requires about 20Kb/s per user (then again this was an old Citrix value) so if you are going to have 40 remote users coming on simultaneously you may be stretching your bandwidth.

 

[mrdenny]

The amount of bandwidth that each user requires will depend on what options they enable when they connect. The most stripped down setting is labled as for a 28.8k modem. The highest at requiring LAN speeds. Basically the prettier the user experience (backgroup, animations, etc) the more bandwidth each user will need.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[DomRCS]

First thanks for the quick replies, a few clarifications:

1) I know the 450kbps line going out now isn't going to cut it, I'm looking to see what I need to get to make sure everyone has a pleasant experience.

2) Here are the settings that the clients will be using:
Full Screen Display (1024x768)
16 bit (millions) color
Connection Speed: Broadband (128Kbps-1.5Mbps)
Allow all but Desktop Background
Play remote sound locally

 

[ascotta]

The only way to get an accurate picture will be to model it.

Each application etc will consume bandwidth differently depending on the graphics (mostly) that will be sent to the remote device.

I would advise against mapping local hard drives too, that will

a) be extremly slow
b) eat bandwidth.

Also model each user type. Each user will use different bandwidth typically. Hojwever you should be abkle to ruel of thumb 1 user bandwidth usage x number of users wanted = bandwidth required.

Remember to take into account all other traffic that will use this link & factor that in including http and smtp site links and anything else that will leave the building by that route.

[blue] A perspective from the other side!![/blue]

Cheers
Scott

 

[LWComputingMVP]

MS RDP is between 20 and 30K. I WOULD NOT allow playing of sound or local hard drives - that will eat bandwidth unnecessarily. For myself, I usually disable EVERYTHING except printing. So, now you need to estimate that you have 60 users (existing 20 + 40 new) multiplied by 30 K per connection equals 1.8 Mbit MINIMUM. To allow things like remote printing (which will give a sudden burst of bandwidth usage) and if each person prints on average a job twice an hour, then you will have, generally between two and six print jobs running at any given time. I would suggest you want AT LEAST 3 Mbit (and frankly, that may be a little low, I'd really recommend 4-5 Mbit for an internet connection - that assumes that the line is used for NOTHING ELSE other than RDP connections (in most cases, this would be VERY unlikely).