--- Chakkaradeep C C <chaks.yoper@xxxxxxxxx> wrote:
Hi all,
We host Thick Servers and Thin Clients.We had
planned a lot with Linux
Servers but now we have to deploy in Windows Server
2003.However, next month
the same deployment is going to be started in
Linux(most probably, we will
be getting SLES).
I was checking in Windows Terminal Services and one
point hit me directly
and i dont know how we are going to implement in
Linux as we havent found a
solution for this till today.
Here is an extract from Microsoft Terminal Service
Document,
Terminal Services is a technology that lets users
run Microsoft(r)
Windows(r)-based applications on a remote Windows
Server 2003-based computer.
In a Terminal Server-based computing environment,
all application execution
and data processing occur on the server. In a load
balanced environment, a
farm of terminal servers have incoming session
connections distributed in a
balanced manner across the servers in the farm. The
session directory (SD)
keeps a list of sessions indexed by user name, and
allows a user to
reconnect to the terminal server where the user's
disconnected session
resides and resume that session.
Now, in Linux, we do have VNC(with several encoding
algorithms) and one
problem is solved.What about the Session
Management?. We have not got a
simple solution on this. Its like this,
- User logs into the Server
- User gets the login screen and he enters his
username and pwd
- Server checks for the last login and saved
session
- If any saved session, start the saved session
- If there is no any saved session, start a new
session
In Windows we are actually opening Sessions across
many Terminal Servers
which are put up in a single Server Cluster with
Network Load Balancing
enabled.
I would be happy if people could give me input on
the above and I need to
implement this in Linux, mainly Session
Management.Somehow, it works
directly in Windows Server 2003 ;(
