The session begins when the user authenticates. This timeout can be changed in the administration console.

  • User Activity Heartbeat interval

    This value controls the interval between Horizon Client heartbeats. These heartbeats report to the Tenant the amount of idle time that has passed. Idle time occurs when there is no interaction with the end point device, as opposed to idle time in the desktop session. In large desktop deployments, it may reduce network traffic and increase performance to have the activity heartbeats at longer intervals.

  • User Idle timeout

    This value controls the maximum time that a user can be idle while connected to the Tenant. When this time is reached, the user is disconnected from all active Horizon Client Desktop sessions. Additionally, when the user returns, they will be required to re-authenticate in order to access the Horizon Client.

    Note:

    The User Idle timeout should always be greater than the User Activity Heartbeat interval, and is recommended to be at least double the User Activity Heartbeat Interval to avoid unexpected disconnects from desktops.

  • Broker Session timeout

    This value controls the maximum time that a Horizon Client can be connected to the Tenant before its authentication expires (timeout count starts each time you authenticate). When this timeout occurs, you will not be automatically disconnected from the desktop and are able to keep working, but if you then perform an action that causes communication to the broker (for example, changing settings), the system requires you to re-authenticate and also to log back into the desktop.

    Note:

    The Broker Session timeout should always be greater than the User Idle timeout, and is recommended to be at least equal to the sum of the User Activity Heartbeat interval and the User Idle timeout.

Note:

Horizon Clients running on the Android OS have been known to override this policy setting, resulting in a session timeout of approximately ten minutes.