Skip to content

App Sessions

Application Sessions can be monitored from HyWorks Controller Management Console >Monitor > Live Sessions > Applications

App Sessions are comprised of Provider Sessions and Application Sessions.

Provider sessions are the container for all application sessions running under the same RDS session.

The Provider Sessions tab provides the following information in a tabular format:

Column Name Description
Username Displays the username of the logged-in user.
IP Address Displays the IP address of the session provider.
Session Id Displays the remote Session ID on the Session Host Server.
No. of application Displays the number of Application Sessions.
Connection Profiles Displays the connection profile applicable to this app session.
Status Displays the status of the session provider (Initializing/ Connected/ Disconnected).
Remote Control Displays the option to take remote control of the connected session. This is applicable for SHD/App sessions only. Refer to the document session shadowing for more details.

Upon clicking the Username, a list view of all Application Sessions is displayed with the following information:

Column Name Description
Application name Displays the name of the application that launch.
Server name Displays the name of the session provider.
Virtual IP Address Displays the Virtual IP Address assigned to the application session. Not available, if the virtual IP address is not enabled.
Status Displays the Status of the app session (Initializing/ Running/ Disconnected).

Application Sessions

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

  1. Some applications e.g. Internet Explorer (x86) invoke another process of 64bit Internet Explorer and then exit> In this case HyWorks Session host may try to keep track of the Child application, but if it fails to get the details of the 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 the 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 the application session does not provide any option to disconnect or log out. It will simply close the selected application.

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

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

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

    b. HyLite: No message will be displayed but the 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:

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

Provider Session

Remote session (WTS Session), under which multiple Application Sessions run, is termed as Provider session. The provider session can have the following behavior:

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

  2. 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 a unique WTS ID associated with it.

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

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