Secure Global Desktop 4.40 Administration Guide > SGD Servers, Arrays, and Load Balancing > Users Cannot Relocate Their Sessions

Users Cannot Relocate Their Sessions

When a user logs in to an SGD server without logging out of another, normally the user's session is relocated to the new server (this is sometimes called session grabbing). If the clocks on all SGD servers in the array are not synchronized, user sessions might not relocate successfully.

SGD uses the timestamps on user sessions to determine which is newer. The newer user session is considered to be current. If clocks are not synchronized, the timestamps might give misleading information.

Because time synchronization is important, use Network Time Protocol (NTP) software to synchronize clocks. Alternatively, use the rdate command.

Related Topics
Understanding User Sessions and Application Sessions