In the case of Smart Session a Thin Client cannot be configured with a list of Terminal Servers - instead it will have a Group of servers (the Smart Session group). When the client detects that the current session is no longer active it will go back to the ThinManager supervisor task (ThinServer) and request the address of another server within that group. ThinServer will re-evaluate the status of all the servers in the Smart Session group and pick the best server at that time - we call this Server Load Balancing. It will recognize that the server that just failed is not available so of course it will not use that one. It will then pass back the address of the best server in the group to the client which will then start a new session on this server.
The situation is a little more complex if the user also has MultiSession. In this case he will have multiple groups in his server configuration. However these groups will not be treated by the client as would a list of Terminal Servers (where the client will pick the next server). Failover will only happen within each group in a MultiSession/Smart Session configuration.
For instance, if one server in Group1 fails and the client connects to a different server in Group1 the session being displayed in Group2 remains unaffected. If all of the servers in Group1 end up failing, then that session for the client will just be blank with the message "searching for available server".
For more information on ACP Industrial Thin Client computers, please visit our web site at http://www.thinmanager.com
To sign up for the E-mail newsletter go here: ACP newsletter signup
For an archive of past newsletter articles go to: ACP Newsletter Archive