Connection Profile Attributes
Basic Settings
Only for identification of connection profiles.
-
Profile Name: Logical name of connection profile
-
Description: Logical description of connection profile
Experience
The purpose of this feature is to define User Experience (UX) parameters for remote sessions. All configurations apply to the remote session.
Experience section settings will enable/disable settings in remote sessions.
-
Connection Type: Options are: Custom\LAN\Modem\Broadband\Detect Automatically\WAN. Attributes may be auto-selected based on the chosen connection type and can be modified by the administrator.
-
Visual Styles: To turn on or off desktop themes.
-
Font Smoothing: To enhance readability, configure font settings to make fonts appear smoother during remote sessions.
-
Desktop Background: If enabled, the end-users can change the wallpaper in remote sessions. If disabled, the users may be presented with a black background.
-
Desktop Composition: Enable or disable desktop composition in remote session
-
Menu and Windows Animation: To allow animated display
-
Show Window Contents While Dragging: Show contents while dragging the window.
-
-
Persistent Bitmap Caching: To allow bitmap caching during remote session
-
Automatic reconnect the session: Configure if sessions should attempt to reconnect automatically if disconnected due to network issues or similar problems
- Reconnection Tries: Retry count when the network is disconnected
Selecting a specific Connection Type also enables or disables relevant experience attributes as listed in the table below:
| Connection Type | Default Selected Features | Default De-Selected Features | Selection Possible |
|---|---|---|---|
| LAN | - All selected | - None | Yes |
| Modem | - None selected | - All | Yes |
| Broadband | - Visual Styles - Desktop Composition |
- Font Smoothing - Desktop Background - Menu and Windows Animation - Show Window Contents while dragging - Selection Enabled |
Yes |
| Detect Automatically | - None selected | - All | No |
| Custom | - None selected | - All | Yes |
| WAN | - All selected | - None | Yes |
Display Configuration
These configurations also apply to remote sessions.
-
Color: Defines the color depth for the remote session. It is not necessary to adjust color depth, but lower color depths will improve performance (below 16-bit color, you will notice significant dithering and unusual colors).
-
Multi-Monitor: The multi-monitor configurations here are directly reflected on Windows devices. For HyDesk (Linux) devices, multi-monitor configurations should be done from Device Settings, and this option should be kept as Uses Device Settings.
The options include:
-
User device settings: Use the same as end-user device configurations.
-
Do not use multi-monitor: Enabling this feature restricts the use of multiple monitors and opens the desktop session on a single monitor.
-
Multiple Display: Utilize all connected monitors. Desktop and application sessions in Shell mode will open across both monitors. The remote app will function as a native app and not span both monitors.
-
Use all monitors span mode: Use identical monitors to create a single screen. Remote App sessions can be stretched to two monitors.
-
-
Display connection bar: (Applicable for Windows Clients and supported with the latest LINUX RDP10 client) Enabling desktop sessions displays a connection bar for minimizing and maximizing.
-
Enable shortcut to minimize window [Alt + Ctrl + Shift] (Windows only): Enable a shortcut key to switch between full-screen virtual desktop and local PC.
-
Enable shortcut key to restore full screen [ALT + CLT + ENTER] (Linux only): Each Linux endpoint has a special key to restore full screen.
-
Smart Resizing Window: Enables auto-resizing of the remote desktop window
-
Enable Full screen (Linux only): Enables a specific flag for full screen on Linux-based endpoints.
Note
- The best way to configure multi-monitor settings on devices is through Device Settings. Refer to the Device Settings section for detailed instructions.
Local Resources
This applies to remote sessions for redirecting local resources and multimedia configurations.
-
Multimedia:
-
Audio Mode: To configure audio redirection in session or not.
Available options are:
- Redirect to this endpoint: Enables audio redirection. Audio will be played on the client side.
-
Audio Quality: Can be set as Medium, High, or Dynamic (Default). The better the quality of audio, the more data will be consumed.
- Do not redirect: Disable audio redirection.
-
Play on the remote computer: The audio will not be redirected but played on the local system. Any audio devices connected physically to the desktop system can listen to the audio.
Note
- Limiting audio quality can help with slow links.
-
Microphone: To enable microphone redirection in session. The available options are:
-
Redirect to this endpoint: The microphone or voice will be captured at the endpoint and redirected to a remote server to be processed.
-
Do not record: Disable the microphone.
-
Note
- The option may not use all the latest codecs or latest options on Linux-based devices and, thus, if advanced configurations are available. These settings should be disabled from the Multi-media section and configured as Additional Settings > Command Line parameters.
- Enable Video Redirection: Not required with RDP8/RDP10 protocols on HyDesk devices.
-
-
Local Drives and Resources: Enabling redirection of local drives and resources to the endpoints
-
Drives: For redirecting client-side drives to remote sessions.
Available options are:
-
Redirect All: Redirect all client-side drives into a remote session.
-
Specify drivers:
-
For Windows end-points: One or multiple Driver names can be specified in a semi-colon separated format, e.g. C:/;D:/.
-
For Linux end-points: It is required to specify:
-
Drive Name: As should be visible in the remote session, e.g., My Home.
-
Directory Path: to be redirected, e.g. \home
-
-
Additional command lines can be specified to redirect drives on Linux client platforms.
Note
The settings are not applicable for HY2000, HY3000, HY4000, or TS3020 HyDesk devices.`
-
-
Video Capture Devices: Enable redirect video capture device to server. Applies to Windows Clients only.
-
Video Capture Encoding Quality: When encoding video, select the appropriate quality level based on your needs.
There are three options:
0: High compression for videos with lots of motion.
1: Medium compression, balanced between quality and compression.
2: Low compression for high picture quality.
-
-
Clipboard: Enable clipboard support in a remote session. Applies to Windows Clients and HyLite.
-
Printers: Enable printer redirection. Applies to Windows Clients and HyLite.
-
Smart Card/ Ports/ Plug n Play devices: Redirection of the Smart Card, Ports, or Plug n Play devices. Applies to Windows clients only.
-
-
Redirect All USB Drives: For controlling USB redirection using a Built-in or Enhanced USB Redirection driver. Driver selection can be configured from Management Console > Devices > Devices/Device Set or Default Settings.
-
Redirect Multi-Touch Device: This applies to HyDesk devices only for enabling multi-touch device redirection.
Important
It is important to know that redirection of a Multi-Touch device may require additional device drivers to be installed on the client (HyWorks Clients) and server (Desktop to be connected).`
-
Allow RDP Plugins: The feature enables or disables use of RDP plug-ins:
-
Accops HyPrint printing Plugin: Allow Accops printing virtual channel.
-
Accops smart file transfer: Allow Accops file transfer virtual channel.
-
Accops tools: Allow generic virtual channel of Accops for other functions.
-
-
Accops Web Request redirection: Allow Accops token and biometric request redirection.
-
Allow third-party plugins: Allow other 3rd party plug-ins. If this option is unchecked, only the Accops RDP plug-in will be loaded.
Advanced Settings
Advanced configuration options for remote sessions.
-
Enable Console: To provide a console session to the user. It should be kept disabled until required to give administrative access to the user. This can be useful when low privileged users fail to connect (e.g., if the RDS license is expired) and the administrator needs to connect and perform administrative activities.
Warning
Accessing a remote session with this flag enabled using a non-admin user could result in session connection failure.
-
Graphics Acceleration Codec
-
Remote FX: To enable Remote FX support in remote sessions, which could help in improved remote session performance. Allow with this option to be enabled, RemoteFX needs additional configuration on the target virtual machine.
-
Enable Graphics Acceleration: Enabling graphics acceleration can help in getting improved graphical and video performance. But the following facts should be remembered while using this remote session enhancement feature.
-
This is applicable for only HyDesk Hy2000, Hy3000, and HY4000.
-
With the RDP7 protocol, the option has no impact and thus can be disabled.
-
With the RDP8 protocol, this option can be enabled to have better graphics, but if the target desktop has RDP10, i.e., Windows 10 or Windows Server 2016 session may freeze on access.
- The best graphical performance could be achieved with the RDP10 protocol on the HyDesk device and the graphics acceleration option enabled, including a session of RDP10 Windows machines.
-
Enable Progressive GFX: To enable progressive GFX in a remote session.
-
Enable H.264 Codec (Linux Only): Enable this option to get the best performance from Linux devices with minimal bandwidth usage.
-
-
Graphics Rendering (Linux only):
-
Software: Reduces the bandwidth associated with graphics remoting by encoding the drawing operations that produce an image instead of encoding the actual image at the software level.
-
Hardware: Reduces the bandwidth associated with graphics remoting by encoding the drawing operations that produce an image instead of encoding the actual image at the hardware level.
-
-
Enable Compression: For enabling compression of remote session data and reducing data traffic over the network, which ultimately optimizes speed.
-
Enable Optimized Video: Enable this option to get an optimized remoting channel with the RDP10 protocol.
Protocol Security
The Protocol Security section in the Connection profile determines the security protocol to be used while connecting to a remote server.
Improper configuration of security protocol may lead to connection failure and thus should be configured cautiously.
The following configurations are possible:
-
Auto: Automatically choose the best security settings as per capabilities negotiated between the client (HyWorks Clients) and server (target Desktop to be connected)
-
Force (Enabled):
-
Enable RDP: Uses RDP security settings forcefully and may fail if the server uses NLA or TLS-level settings.
-
Enable NLA: Pushes NLA-level security settings from the client side.
-
Enable TLS: Uses TLS security settings from the client side for remote connection.
-
-
Force (Disabled):
-
Enable RDP: Un-checking this will ignore RDP for remote connection and use NLA or TLS, whereas selecting this option will specify RDP security settings.
-
Enable NLA: Deselecting this will ignore NLA for remote connection and use RDP or TLS.
-
Enable TLS: Deselecting this will ignore RDP for remote connection and use RDP or NLA.
-
-
Enable CredSSP: For supporting Credential Security Support Provider. For NLA-enabled SHDs or app delivery, connecting from Windows clients, this can be kept enabled.
Session Timeouts
Session timeouts in connection profiles apply to the following two types of sessions:
-
Remote sessions on Session Host Server or Desktops.
-
User sessions on HyWorks Controller.
More information about applying session timeouts will be explained later in this section.
The following configurations are available in the Session Timeouts section:
-
On Client-Disconnect: Defining how the client disconnect should be controlled on the controller, the following actions can be configured:
-
Disconnect the user session: Keep the associated sessions in disconnected mode.
-
Logout the user session: Completely log out of the session and associated desktop/application sessions.
-
-
Enable User Inactivity Monitoring: To enable/ disable user inactivity monitoring. Sessions are monitored for inactivity, and then, on finding a user session idle for a specific time, it will be moved to idle sessions. The user will be disconnected/logged out after remaining idle for some more configurable time limit.
-
Make User Session Idle In: Time in minutes, after which inactive (a session with no user activity) will be marked as idle.
-
Expire Idle Session In: Time in minutes, after which idle sessions will be removed per the configured On Expire settings.
-
On Expire: Determines if sessions should be disconnected or logged out on expire.
-
Disconnect the user session.
-
Logout the user session
-
-
Set Max Session Timeout: To enable only limited-time remote sessions.
-
-
Logoff Disconnected Session After: Time in minutes, after which disconnected sessions will be logged-out from the controller or session host server.
-
Lock Idle Session Screen: Locks the user session on the user's PC when idle for X minutes.
- This applies to endpoints in modes where user cannot control the lock screen on their own or cannot be controlled using group policies, e.g., Linux Endpoints, Windows Endpoints in KIOSK mode, etc.
Application Access Settings
Important configurations define the remote session appearance and access methods.
The following configurations are available:
-
Application Launch Mode: Decides how the applications will be launched
-
Remote App: Remote applications will appear like native applications, and all applications will run in single remote sessions on the session host server.
-
Shell: Applications are launched in a separate Windows shell, which means every application session will be launched in a different remote session and will lead to multiple license consumption for a single user.
-
-
Session Experience Option: Defines the launching experience of the remote session. This applies to Windows clients only; the following options are available:
- Always Seamless: Sessions will be launched in seamless mode, and until the session is connected completely, HyWorks custom dialog and progress bar will be displayed
- Never Seamless: A remote desktop window will always be displayed to handle unknown prompts or errors. This opens another parent application window, which should not be closed. It does not give the best user experience but can be used for troubleshooting or cases where the prompt inside of a remote session can not be handled in Remote App mode.
-
Window Client Session Launcher Option: Defines the launcher of the remote session. This applies to Windows-based desktop clients only, following options are available:
-
Built In (Default): To use and control a remote PC with an Accops native desktop Desktop client.
-
Legacy (MSTSC): To use and control a remote PC with a Remote Desktop client.
-
It does not work with Remote Apps.
-
For shared hosted desktop sessions delivery, see "note" below.
-
-
Windows Desktop client (MSRDC): To access remote apps and desktops from Azure Virtual Desktop and Windows 365.
-
It does not work with Remote Apps.
-
For shared hosted desktop sessions delivery, see "note" below.
-
-
PC-over-IP Protocol (PCoIP): Teradici PCoIP is a high-performance display protocol that is built to deliver virtual desktops and to provide end users with a rich desktop experience.
-
Note
-
To deliver shared hosted desktops (SHD) using Legacy (MSTSC) and Windows Desktop client (MSRDC), the following configurations must be done:
-
HyWorks Management Console > Settings > General > Advance Settings > Enable win alternate shell: True.
-
The session can be terminated by session agents or controllers if the above configurations are absent.
-
Additional Settings
It is a very powerful mechanism to use any of the latest options available on the side launcher but not yet available on the HyWorks Controller. Any other custom attributes can be defined using an additional settings section. Additional command line options for different protocols can be defined here. Additional command line options can be specified for the following protocols:
-
RDP 7.0 (Linux): Use this section for Linux-based clients running with RDP10 or RDP8 protocols, e.g. -k 0x00000407, -a 32.
-
RDP 8.0 (Linux): Use this section for Linux-based clients running with RDP8 protocols, e.g. /floatbar.
-
RDP 10.0 (Linux): Use this section for Linux-based clients running with RDP10 protocols.
-
RDP (Windows): Use this section for Windows-based clients, e.g., connection type:i:7.
-
Generic RDP: As per format supported by the client using generic RDP, e.g., HyLite.
Warning
Additional command line options are very useful. But with Linux Clients, the invalid command line attributes can result in session failures and thus should be configured very carefully on production systems.
- Session Recording Profile: To enable session recording of a user session, associate the session recording profile with the connection profile. Select the session recording profile from the dropdown control to start the session recording of the user session.
Connection profiles assigned to apps or desktops will now be recorded. If no session recording profiles are attached to the connection profile, then session recording will not be done.
Note
-
The session recording profile needs to associate with the connection profile to enable session recording.
-
Without association, session recording of the user session cannot start.