Skip to content

Features & Enhancements

This section in release notes, provides the details of new features and enhancements in HyWorks v3.3-R3 release.

HyWorks Installer Improvements

HyWorks v3.3-R3 is having following changes to make installation process easy:

Controller

Fresh Installation

Setup wizard has following changes during fresh installation:

  • Setup wizard now provides option to choose Deployment Mode (two-node active-passive or multi-node active-active cluster), Node Type (for multi-node cluster, the type of role to be performed: management node, broker node) and Database High-availability Configuration (which type of database to be used: HyWorks managed or SQL managed).

  • In multi-node installation with SQL managed database high-availability, database configuration by second management node is optional.

  • Broker node installation will not perform any database configurations.

  • Automatic database configurations on broker nodes: Earlier the configurations were done by modifying configuration files, now broker node will get management node host address and it's settings from management node during installation.

  • Node type or controller role to be set during installation. This will help in smooth upgrade and uninstallation.

  • Embedding Microsoft Sync Framework in HyWorks Controller to reduce dependency installation externally.

Uninstallation

From this version onwards, database will not be removed on unistalling Broker node. Database removal option will only be given during uninstallation of management node.

Controller Upgrade

  • During controller upgrade, database configuration will be done based on the current role of the controller.

    • Broken node upgrade will not make any changes to database configurations.

    • For SQL managed database high-availability multi-node cluster, database upgrade will be done during upgrade of first management node.

Option to install Session Host using controller setup is removed

For simplification of installation and logical separation between management and session modules, session host server option from controller installation wizard has been removed.

  • For fresh installation or upgrade session host server setup must be used.

Scheduler Installer

New setup wizard of scheduler installer will prompt to configure database information. This will help in avoiding re-configuration of scheduler from application configuration file.

Scalability Enhancement

HyWorks Controller v3.3-R3 comes with performance improvements to support 10K concurrent shared hosted desktop connections.

Functional Changes

Option to fetch domain for remote session from user logon

HyWorks v3.3-R3 or later will have following configurations to support different deployment requirements:

Parse from Logon Name: This option is added to fetch domain name for remote session from user logon credentials in "Workspace > Organization > Auth Domain configurations" section. This will need user to provide domain name in logon (i.e. username@domain-name or domain-name\username)

Team association for providing session delivery with built-in Authorization Server is no more mandatory For configurations, where built-in directory is used as authorization server, it was mandatory to associate users in built-in directory with session teams.

Built-In User Team Association option is added System > Advance configurations to make it optional. Default value is true and setting it as false will not require user to be associated with teams for getting application or desktop access.

Note

  • In workgroup environment, it is required to sync users on session host servers and thus, option "Built-in User Team Association" must be set as true and users must be associated with respective session teams.

Special character @ is allowed in username in built-in user directory: In previous versions, special character @ was not allowed in username field. The restriction has been removed to support user logon with authentication domain configurations where AD (UPN as login attribute) is used for authentication and built-in server is being used as authorization server.

This will help, allow users belonging to different domains in a single organization, to login.

Advance Flag for Username Processing: When user is providing username, "Username Options" advance flag can be used to process username:

  • Set as 1: To truncate username using @ or \ as separator.
  • Set as 2: To use username as provided on logon without any modification
  • Set as 3: To prepare username using information provided in username@domain-name format.

HyLabs Features and Enhancements

Release Reserved VM on User Logout

In previous version of HyLabs, an assigned VM from reservation was getting released only at the end of the schedule. To use HyLabs as scheduled delivery of temporary virtual desktop, HyWorks v3.3-R3 will control releasing an assigned VM from an advance flag. Setting flag Remove HyLabs temporary assignment on logout as true, will release VM on user logout from client or HyLite.

Flag added to override retention of VMs on log off

Controller Management Console - System - Advance Config

To use this feature following settings should be applied to reservation:

  1. Reservation Type: Course Reservation
  2. Re-use Flag: True
  3. Assignment Life-span: Temporary
  4. Remove HyLabs temporary assignment on logout: True

Note

Enabling flag - Remove HyLabs temporary assignment on logout; will override default reservation settings of retaining VM after logoff. Because of which even if user tries to retain assigned VM, it will be released on logout, as per new advance configurations.