Skip to content

User Session Management

User session management begins when the user logs into HyWorks and continues until they log out. This document outlines the details of user session management in HyWorks.

  • The Session Timeout settings of the Connection Profile govern the session management. Upon login, a user session is assigned a connection profile, and applicable timeouts for the user are applied with this connection profile.

  • User sessions can be viewed and tracked from Monitor > Live Sessions > Users.

User Session Flow and Use Cases

Log in from HyLite or Android Clients

**Case #1: Logging in from HyLite and not connecting to any virtual applications or desktops. **

Action Status on Management Console
User logs-in Active [Initially]
No activity Idle [Connection profile - Session timeout configurations]
No activity Session expires [Connection profile - Session timeout configurations].

  • Upon session termination, the user session can be kept in HyWorks as disconnected or removed. This is done based on Connection Profile > Session Timeout > On Expire settings.

    • If On expire is set to Disconnect, user sessions will be kept in HyWorks with a disconnected status. The Session will be removed from HyWorks as per the configuration Connection Profile > Session Timeout > Logoff disconnected session after.

    • If On expire is set to Logout, the user session will be removed from HyWorks.

Case #2: Log in to HyLite and connect to any virtual applications or desktops.

Action Status on Management Console
User logs-in Active [Initially]
Connects to assigned applications/desktops Active until virtual application or desktop sessions are connected
The Application/Desktop session gets disconnected or logged out. Active as per Connection profile - Session timeout configurations
No activity Idle [Connection profile - Session timeout configurations]
No activity Session expires [Connection profile - Session timeout configurations].

  • Upon session termination, the user session can be kept in HyWorks as disconnected or removed. This is done based on Connection Profile > Session Timeout > On Expire settings.

    • If On expire is set to Disconnect, user sessions will be kept in HyWorks with a disconnected status. The session will be removed from HyWorks according to the configuration Connection Profile > Session Timeout > Log off disconnected session after.

    • If On expire is set to Logout, the user session will be removed from HyWorks.

Important

  • HyLite starts sending heartbeat (Keep-alive) updates to the HyWorks Controller after a connection to any virtual application or desktop is established.

  • HyWorks determines the user's active status from two sources: 1. Heartbeats from HyLite and, 2. Desktop or Virtual Application Connection.

  • This Keep-alive interval is configurable from the HySecure Management Console.

    • Ideally, the Keep-alive interval should be less than or equal to one-third of (connection profile idle + expire timeouts). [Keep-alive=(Idle+Expire timeouts)/3]

Log in from Other Desktop Clients

With the latest HyWorks Controller, the behavior of user sessions from desktop clients will be identical to that of HyLite. Check the cases mentioned in the above section for understanding the behavior.

Default Configurations

Accops HyWorks is having following system level configurations by default, which determines the session management mechanisms:

  • Enable win alternate shell: Recommended to be kept as True. Default value is True. Not directly associated with user session management but plays important role for desktops session reconnection between different types of client. This setting controls the launch mechanism of sessions and enabling this makes the Windows client to use the same mechanism as Linux and HyLite.

    • Important: This must be set True, when Windows end-point is configured to use Legacy (MSTSC) or Windows Desktop Client (MSRDC). Keeping it false results in removal of sessions as session host agent is not able to identify the session as managed.

  • Enable Session Sync on Session Host: Default value is false. If enabled, session synchronization will be initiated by session host. Not directly affecting session management but this is used to sync the session info between controller and session host, accordingly clean-up of un-managed sessions can be done.

  • Session Sync Interval on Session Host: If setting "Enable Session Sync on Session Host" is true, the session sync will happen based on configured interval here.

  • Failed session cleanup Configurations: Applicable for virtual apps and shared hosted desktop sessions. Following configurations are available:

    • Failed application remover: Recommended to be kept as True. Default value is True. The configuration ensures that if no intimation comes from session host agent of the launched session of virtual app or shared hosted desktop session, it is removed from HyWorks Controller.

    • Failed session cleanup interval: This configuration is used when "Failed application remover" is set as true. Controller checks for failed sessions based on configured interval here.

    • Failed sessions remove timeout: Controller will remove any shared hosted desktop or virtual app session, which exceeds the configured timeout without receiving confirmation from the session host agent.

  • Active session time before close on RDP status

  • Desktop session monitoring on RDP status type: Personal desktop active session monitoring based on RDP connection status. Active/Connected dedicated desktop session will be removed if the RDP session does not exist on DVM. Set 0 to disable it. Set 1 to monitor the desktop session of DVM with Linux and Windows OS. Set 2 to monitor the desktop session of DVM with Windows OS only.

    • Interval in minutes for desktop session monitoring on RDP status: Set the interval in minutes to run the Desktop session monitoring on the RDP status thread.

    • Active session time before close on RDP status: Set the active session time in minutes before it closes which will be used by the Desktop session monitoring on RDP status thread. The session will not be closed if its age is below than the given value.

  • HyDesk user session idle monitoring: HyDesk user session idle monitoring type, If it is set as 1 then user session idle session monitoring will be done based on device heartbeat and if it is set as 2 then the user session idle monitoring will start when no active RDP session is running. Recommended is to set it as 2.

  • Desktop poll mode:

  • Physical PC Logoff Options: Physical PC Logoff Options: 1.Default behavior (no change), 2.Disconnect on Logout, 3.Restrict Logoff and Disconnect . Default value 1 Desktop readiness condition In session, HyDesk heartbeat timeout multiplier Heartbeat Interval Keepalive interval Disable HyDesk activity monitoring Heartbeats allowed to missed Keepalive idle Enable multiple user session

Failed sessions remove timeout

Reconnect the session from Inactive server

Delay time before logging out users and shutting down VMs (min) Concurrent threads for idle session logout or disconnect <-->