Amount of Load Each Client puts on a Terminal Server

[ShawnF]

How does one gauge or measure how much strain connected clients put onto a Terminal Server? I am sure it depends on what program(s) the Terminal Server is sharing, but surely there must be a way to figure this out. I'm looking at either using an existing W2K Terminal Server to dish out a single simple program, or use a different server (2003) that isn't quite as robust as the 1st one but isn't currently being used as a Terminal Server either. Are there certain "minimum" or "recommended" requirements for each client connection?

Thanks!

ShawnF

 

[Zcript3r]

Shawn,

Here is a link to a page on Microsoft's site that talks a bit about running Office XP on Terminal Server. It mentions a little bit about what is required in terms of hardware and what kind of RAM each TS Client requires.

http://www.microsoft.com/technet/prodtechnol/office/officexp/deploy/xptersrv.mspx

 

[oisnds]

You may want to go with Win2K just because of the licensing changes. A TSCAL is required for all clients in Win2K3 Terminal Services.

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx