Skip to content

App Sessions

App Sessions are comprised of Provider Sessions and Application Sessions. Provider sessions are the container for all application sessions running under same RDS session.

The Provider sessions tab provides the following information in tabular format:

Sr No Column Name Description
1 Username Displays the username of the logged in user
2 IP Address IP address of the session provider
3 Session Id Remote Session Id on Session Host Server
4 No. of application Number of application sessions
5 Connection Profiles Connection profile applicable for this App session
6 Status Status of the session provider(Initializing/ Connected/ Disconnected)
7 Remote Control Option to take remote control of connected session. Applicable for SHD sessions only.

On click of Username provides a list view of all Application sessions, providing following information:

Sr No Column Name Description
1 Application name Name of application which launch
2 Server name Name of session provider
3 VIP Address VIP Address
4 Status Status of the app session (Initializing/ Running/ Disconnected)

Application Sessions

Any independent application accessed using HyWorks Client or HyLite will be logged in HyWorks Controller Management console and will be termed as App session. All applications being delivered to users are tracked using unique App Session Ids. Following behavior of the app session is available

  1. Some applications e.g. Internet Explorer (x86) invokes another process of 64bit Internet explorer and then exits. -> In this case HyWorks Session host may try to get track of Child application, but if it fails to get the details of Child process then it will lose the track of app session and when the entry will be shown as "0" -> Zero app sessions.

    a. But provider session (Please see next section) will be kept alive as some   child process is running -> In this case the reconnection won\'t be possible.

  2. Closing application session does not provide any option to disconnect or logout. It will simply close the selected application

  3. In case of same apps is launched multiple times, no identification mechanism is available for uniquely identifying any app

  4. While closing the application session, administrator can choose to send a custom message with timer

    a. HyWorks Client: Message will be displayed, and application will remain active for provided time

    b. HyLite: No message will be displayed but application will be closed as per the provided time

    c. Dependency for Custom Message:  RDP Extensions

  5. Remove App Sessions when Session Host Agent is not available: Removing App session when Session Host Agent is not available

    a. HyWorks/HyLite: App session removal will be failed, and an error entry will be created followed by appropriate warning entries

Provider Session

RDS session (WTS Session), under which multiple application sessions run, is termed as Provider session. The provider session can have following behavior:

  1. A single provider session can have one or multiple application sessions

  2. For the applications whose control is lost (which invokes child processes and gets itself killed later.), will have no application session entry and will not be shown under the provider session.

  3. Provider session will have unique WTS Id associated with it.

  4. Selecting a provider session, enables the terminate Process(s) button which can be used to completely logout the specific RDS session

  5. Multiple Provider sessions can be removed together, and it will also logout all the associated App sessions