Terminal Server Load Balancing - Terminal Functions:
Dedicated load balancing pools together all the processing resources of multiple servers, using the TCP or IP networking protocol. End users have the instant access to the special service via a cluster or user specific group of terminal servers. The terminal servers help to achieve the desired level of 'scale' with respect to the performance of every single terminal server, by distributing the identified sessions across multiple servers.
The specially compiled and regularly updated Session Directory that is freely accessible within Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition, helps the end users to keep a check on the disconnected sessions on the dedicated cluster. The approach also ensures that users stay connected or rather reconnected to those particular sessions.
The industry and user specific terminal services connection management works in sync with the user's deployed load balancing service. Together they ensure that the end users are reconnected without any hidden catches, to the original server that is designed and programmed to host the disconnected Terminal Server access.
Terminal components:
There are a number of specially designed and regularly updated components of Terminal Services Connection Management. They include a network load-balancing solution within the sphere of influence of the Network Load Balancing, Domain Name System or DNS round-robin or any other available solution option marketed. Another component includes the application of two or more terminal servers that are logically grouped or clustered within a dedicated Terminal Server cluster. Then end users can also optimize the availability of the special session directory server. This computing machine could be any active Windows Server 2003, Enterprise Edition or the Windows Server 2003, Datacenter Edition. These applications are easily accessible on the network. Users can also explore the functionality of a running Terminal Services Session Directory service. It is to the user's best advantage to opt for making the Session Directory server a highly available network server that is distinctly not the running Terminal Server itself. Access to the Terminal load balancing technology:
The Terminal Server Connection Management process is implemented by the following procedure: - The end user logs on to the dedicated terminal server cluster. - The terminal server that receives the user or client 'log on' request then sends runs an enquiry directed towards the session directory server. - The session directory server in turn, verifies the username against its database. - The result is then directed towards the initial requesting server. - If the user sessions are not disconnected, the logon application continues at the server that hosts the first identified connection. - If, for some reason, the user does have a disconnected session on another server, then the client session is reverted to that particular server and the logon application continues. - Finally, when the user logs on to the disconnected session, the session directory is automatically updated.
Load Balancing
| 