Skip to content

Desktop Sessions

Desktop Sessions can be monitored on HyWorks Controller Management Console > Monitor > Live Sessions > Desktops

Desktop Session section displays the list of all Desktop Sessions (dedicated/shared hosted desktops). The administrator can remove any specific Desktop session by clicking on the Remove Sessions button.

The Desktop 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 Device Name Displays the name of the device, if the user has logged in from HyDesk or HyWorks Client.
3 IP Address IP address of the machine from which the user has logged in. In the case of HyLite, this will be the IP address of the HySecure Gateway.
4 Session Id Remote Session ID on Session Host Server.
5 Pool Name Name of the desktop pool from which the sessions are coming.
6 Pool Display Name Display the Name of the desktop pool from which sessions are coming.
7 Desktop Name Name of accessed desktop VM. In the case of SHD, this displays the session host server name.
8 Desktop IP Address IP Address of the desktop connected to the network.
9 Connection Profiles Connection profile applicable for this Desktop session.
10 Status Status of the desktop session (Connected/ Disconnected).
11 Remote Control Option to take remote control of the connected session. Applicable for SHD sessions only.
Click here to refer to the document on session shadowing.
12 Virtual IP Address Displaying the virtual IP address assigned to the session. Unavailable if not configured.

Remove Desktop Session

  1. Go to Monitor > Live Sessions > Desktops.

  2. Select any Desktop session by clicking on the respective checkbox.

  3. Click the Remove Session(s) button.

  4. Confirm the action in the displayed dialog box.

  5. Selected Desktop Sessions will be logged out.

Behavioral Facts of SHD and Desktop VM Sessions

Dedicated Desktop VM Sessions

  1. No option to select between disconnect and logout.

  2. No option to send a message to the client.

  3. Default Desktop Session Removal Behavior: Disconnect the sessions. (The unsaved user data will not be lost until the session expires.)

  4. Removing Session When Session Host Agent is not available: Session will be removed with a success message, but a warning will be logged in logs.

    1. On HyLite: The session can run infinitely because the client does not sync the sessions (App/Desktop).
    2. On HyWorks Client: Sessions will be disconnected on the next heartbeat sync.

Shared Hosted Desktop Sessions

  1. No option to select between disconnect and logout.

  2. No option to send a message to the client.

  3. Default Desktop Session Removal Behavior: Log out the RDS session (Unsaved user data will be lost).

  4. Removing Session When Desktop Agent is not available: The session will be removed with a success message, but a warning will be logged in the logs.

    1. On HyLite: The session can run infinitely because the client does not sync the sessions (App/Desktop).
    2. On HyWorks Client: Sessions will be disconnected on the next heartbeat sync.

Task Manager on Desktop Sessions

Supported in Version: v3.4-SP2 or later.

Supported Platforms: Currently for Windows only.

On HyWorks Controller Management Console Monitor > Live Sessions > Desktops section, clicking on Username will open Task Manager view for the administrator.

Viewing Processes

The first tab of the Task Manager prompt - Processes, displays the processes in the desktop session with default columns (Process Name, Status, CPU (%), Memory (MB)).

  • It has options to customize the view by selecting columns as needed. Click Select Columns to open the column selection window, which lists the available columns.

  • Option to Refresh and Last Refreshed Time: The task manager does not refresh automatically. The Refresh button can be used to refresh it manually. The last refreshed time helps in understanding if a refresh is needed or not.

Killing Processes

Administrators can also choose to kill processes (if needed). To kill processes, the following steps can be done:

  1. Select one or more processes from the Processes tab.

  2. Click on the Next or End Task tab.

  3. The following details and options will be presented to the administrator:

    1. Process Name: The process(es) selected from the Processes tab.

    2. User Consent: Select this option if you want the user to be prompted for consent before terminating the selected processes.

    3. End Process Tree: Select if the process tree of the selected process should be killed.

    4. Custom Message: Enter any custom message to be displayed to the end-user during the session.

      1. If nothing is mentioned, the following default text is used: "Process [ Process Name ] will end in [Timer] seconds.",
    5. Timer (in seconds): Default 30. The user will be shown the message for the configured duration.

  4. Select appropriate options and kill on the Kill Task.

  5. End Task operation will be initiated, and a success message will be displayed.

  6. The administrator will be returned to the Processes tab.

Behavior of End Task with User Consent:

  • If the administrator chooses to kill process(s) with user consent, the following behavior will happen:

    • The user will be prompted with a message for consent.

      • If the user does not provide any consent, the process(es) will not be terminated, and the notification will disappear according to its duration.

      • If the user denies by clicking No on the Consent dialog, the notification will disappear, and the process(es) will not be terminated.

      • If the user confirms by clicking 'Yes' in the Consent dialog, the notification will disappear and the process(es) will be terminated.

  • If the administrator chooses to kill process(s) without user consent, the following behavior will happen:

    • The user will be shown a notification dialog with no options.

    • If the user chooses to close the notification dialog, the process(es) will terminate, and the dialog will disappear.

    • If the user does not act, the dialog will disappear according to the configured timer, and the process(es) will be terminated.