![]() |
|
|
|
#1 |
|
OK, I'm sure that this question has been asked before, but I would like to
really get some good numbers/testing on deploying Terminal Services vs Citrix based on bandwidth limitations. My understanding is that you can assume ~10k per session for Citrix and ~30k per session for Windows Server 2003 TS. Now, some of the Microsoft graphs I looked at made it look as though I could use compression to get down to about 20k per session. Does anyone have any good links to share? I have spent way too much time on Technet looking for something hard and fast to use when pitching Citrix to a customer. Of course, Citrix's numbers were really easy to find. -- Mostly Gizzards A+ Network+ MCSE 2003 Mostly Gizzards |
|
|
|
|
#2 |
|
Posts: n/a
|
Mostly Gizzards wrote:
> OK, I'm sure that this question has been asked before, but I would > like to really get some good numbers/testing on deploying Terminal > Services vs Citrix based on bandwidth limitations. My understanding > is that you can assume ~10k per session for Citrix and ~30k per > session for Windows Server 2003 TS. Now, some of the Microsoft > graphs I looked at made it look as though I could use compression to > get down to about 20k per session. Does anyone have any good links > to share? > I have spent way too much time on Technet looking for something hard > and fast to use when pitching Citrix to a customer. Of course, > Citrix's numbers were really easy to find. Depends on a few things. What will you be running in your sessions? Is it something that is graphically intensive? What about printing? Printing takes up a lot of bandwidth. You'd be best of testing this yourself. Set a TS up and run some of your usual stuff, and measure the bandwidth used. We have about 90 users, and they've never used more than 400k of our 2mb line. -- Talent hits a target no one else can hit. Genius hits a target no one else can see. |
|