How does Terminal Server work?

  • Thread starter Thread starter Juan Jose Costello Levien
  • Start date Start date
J

Juan Jose Costello Levien

Hello,
I would like to know how does Windows 2000 Server administer the sessions
that Terminal Server opens. I tried it in an AMD XP 1.6, 512 MB RAM, 30 GB
HDD IDE, and I couldn't open more than 3 sessions using rdesktop. I searched
for detailed documentation, but I only found "Windows 2000 Server creates a
new environment for each user that connects". I supposed that what it does
internally is to create a separate region on memory (reserves X amount of
memory for each client) and tries to manage this. The thing is when you try
to run lightweight process in each session; as the session consumes
resources, the program that runs in it doesn't work fast.
If you know the details of how W2K works with Terminal Server, please tell
me.

Thx.


Juan
 
The reason you couldn't open more sessions is more likely that you're in Remote Administration Mode, not that you're system can't handle the load. As system like yours could easily handle 5-10 simultaneous Remote Desktop Sessions if Terminal Services is Iinstalled and in Application Server Mode

Here's some more technical info on how it works
Remote Desktop Protoco
http://msdn.microsoft.com/library/d.../termserv/termserv/remote_desktop_protocol.as

Resources on a Terminal Serve
http://msdn.microsoft.com/library/d...rv/termserv/resources_on_a_terminal_server.as

Specific instructions on how to plan, setup and administer Terminal Server here
http://www.workthin.com/tshta.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Juan Jose Costello Levien wrote: ----

Hello
I would like to know how does Windows 2000 Server administer the session
that Terminal Server opens. I tried it in an AMD XP 1.6, 512 MB RAM, 30 G
HDD IDE, and I couldn't open more than 3 sessions using rdesktop. I searche
for detailed documentation, but I only found "Windows 2000 Server creates
new environment for each user that connects". I supposed that what it doe
internally is to create a separate region on memory (reserves X amount o
memory for each client) and tries to manage this. The thing is when you tr
to run lightweight process in each session; as the session consume
resources, the program that runs in it doesn't work fast
If you know the details of how W2K works with Terminal Server, please tel
me

Thx


Jua
 
Back
Top