Skip to content

Features and Enhancements in HyWorks v4.0

This release notes section highlights the new features and improvements introduced in HyWorks v4.0.

HyWorks Enhancements and Features

Installation: Support of Group Managed Service Account (gMSA)

A group Managed Service Account (gMSA) is a managed domain account that provides automatic password management, simplified Service Principal Name (SPN) handling, and delegated administration.

In HyWorks, gMSA can be used to configure HyWorks services to connect to SQL Server, reducing password management overhead for system administrators.

HyWorks v4.0 modules, including HyWorks Controller, VM Scale Booster, Session Recording Manager Server, and Scheduler, are released with full support for gMSA-based deployments. Once installed, all relevant services use the configured gMSA for Log on as a Service permissions and database operations, provided the gMSA has appropriate privileges on the SQL Server.

All setup wizards include an option to configure a gMSA account during installation.

Installation: Removing Dependencies on SQL CE

Earlier versions of the HyWorks Controller required SQL CE (v4.0 SP1) as a prerequisite for installation. Since SQL CE is no longer supported, HyWorks v4.0 Controller installers have removed this dependency and now complete installation without requiring SQL CE.

Nutanix Connector Feature Integrations

APIv4 Integration

Recent versions of Nutanix Prism Central (v7.0 and later) introduce APIv4. HyWorks v4.0 includes native integrations with APIv4.

Batch Processing

APIv4 performs batch operations by default for VM cloning and related workflows, improving efficiency and reducing API overhead.

Nutanix Sub-type and API Versions with Recommendations

While adding a Nutanix Connector in HyWorks v4.0, administrators must select the Nutanix Connector subtype. Based on the chosen subtype, a recommended API version is automatically selected and can be modified if needed.

The following sub-types and recommended API versions are supported:

Type Sub-type API-type
Nutanix Prism Central (version > 7.0) v4 (Recommended)
v3
Prism Central (version < 7.0) v3 (Recommended)
Prism Element (version > 6.0 and < 7.0) v2 (Recommended)
v1
Prism Element (version < 6.0) v1 (Recommended)

Important

  • In previous versions, API configurations were managed using HyWorks Controller Advanced Settings. And thus, new configurations help in overcoming the following limitations:
    • System-level configurations instead of provider-level.
    • Less visibility to the administrator and misconfigurations.

No Direct Support for Prism Element Newer Than v7.0

As Nutanix continues to move toward Prism Central-based management, HyWorks v4.0 does not support adding Prism Element versions greater than v7.0. Administrators are advised to use Prism Central for such environments.

Container Selection During Deployments

In earlier versions of HyWorks, cloned VMs were deployed on the same container as the gold master VM. In HyWorks v4.0, administrators can explicitly select the target container for deployments.

If the gold master VM is not in the selected container, it will be migrated to the target container before deployment begins.

Azure Connector - New SDK Integration

This release includes an internal improvement to use the latest Azure NuGet SDKs.

Here is the list of packages for reference:

Note

This change does not introduce visible UI features but improves compatibility, stability, and long-term support.

Package Name Version
Azure.Security.KeyVault.Secrets / Keys / Certificates v4.8.0
Azure.ResourceManager.Compute 1.13.0
Azure.ResourceManager.Compute 1.13.0
Azure.ResourceManager 1.13.2
Microsoft.Graph 5.82.0
Azure.ResourceManager.KeyVault 1.3.3
Azure.ResourceManager 1.13.2
Azure.ResourceManager.Network 1.14.0
Azure.ResourceManager 1.13.2
Azure.ResourceManager.Authorization 1.1.6
Azure.ResourceManager.Resources 1.11.2
Azure.Core 1.50.0 (Consolidated)
Azure.Identity 1.17.1 (Consolidated)
Azure.ResourceManager.DesktopVirtualization 1.13.1

Bulk Operations Improvisations

The following additional operations are now supported with bulk selection of virtual machines:

  • Fix Desktop

  • DVM Tools Upgrade

Note

In previous versions, these operations were supported only for single desktops.

Recurring Schedules

Earlier versions supported only one-time schedules for actions such as Power operations and marking desktops as active or inactive.

HyWorks v4.0 introduces recurring schedules, enabling administrators to configure recurring activities across a list of VMs easily.

Example:

  • Periodic refresh of virtual machines by scheduling a nightly restart daily.

Controller Management Console Color Themes

Administrators can now choose a theme color for the HyWorks Controller Management Console.

To change the theme:

  1. Click on the logged-in username.

  2. Select a theme from the predefined list.

Available themes:

  • White

  • Orange

  • Black

vTPM Enabled Host Identification During Cloning

In earlier versions, if the gold master VM had vTPM enabled but the selected host did not support vTPM, the cloned VM could not enable vTPM.

The best host selection logic has been enhanced to:

  • Prefer vTPM-capable hosts for provisioning.

Features implemented in HyWorks (Pending compatible module release)

Important

Features listed in this section may be visible on the HyWorks management console, but can only be used with compatible modules.

Any changes required on the HyWorks side by submodules, such as the Workspace client or the desktop agents, will be addressed in the subsequent releases.

Desktops Grouping into Folders

Virtual Application add/edit wizards already provide the option to group applications into specific folders, which are typically visible on the client side.

Similar functionality for desktops—allowing association with existing folders or creating new folders—has been introduced in HyWorks v4.0 via the Desktop Pool add/edit wizard.

HyWorks Controller Management Console > VDI > Pools > Add/Edit Desktop Pool wizard > Client Settings - tab > Folder Creation

The Folder Creation option provides the following choices:

  • None: Desktops are not placed in any folder.

  • Create New: Creates a new folder for the desktops.

  • Use Existing: Allows you to select an existing folder.

Compatible Workspace Endpoints This feature is initially expected to be available on the following Workspace clients:

  • Windows: Not yet GA released. To be added as per the availability of the module.

  • macOS: Not yet GA released. To be added as per the availability of the module.

Important

Explicit folder management is not available. Folder association can be performed only through the Add/Edit Desktop Pool wizard.

Folder deletion is not supported and must be handled carefully.

Application folders cannot be used for desktops, and desktop folders cannot be used for applications.

Power Operation Control (for endpoints)

HyWorks v4.0 introduces controls to manage which power operations are available to end users on endpoints.

HyWorks Controller Management Console > VDI > Pools > Add/Edit Desktop Pool wizard > Client Settings - tab > Power Operation Control

  • These options are available only for single-session desktops.

  • Available configurations:

    • Allow All: All power operations are allowed, based on the current power state of the assigned virtual machine.

    • Disable All: No power operations are allowed, regardless of the current power state.

    • Allow Limited: Only selected power operations are allowed, depending on the current power state.

      • Supported power operations: Shutdown, Power On, Power Off, Restart, Pause, Resume.

Compatible Workspace Endpoints

  • Windows: Not yet GA released. To be added as per the availability of the module.

  • macOS: Not yet GA released. To be added as per the availability of the module.

Note

Power operation control is not available for multi-session desktops.

Task Manager for Linux Desktops

In HyWorks v3.4-SP2, administrators could view and terminate processes in a desktop session (Windows only).

This functionality has now been extended to Linux desktop sessions.

HyWorks Controller Management Console > Monitor > Live Sessions > Desktops section > Click on Username

Clicking the username opens the Task Manager view for administrators.

Compatible Linux Flavors and Versions

  • Not yet GA released. To be added as per the availability of the module.

API Client Integration (Experimental)

To enable integration with external portals, HyWorks introduces support for API Clients. Once configured, API Clients can securely consume HyWorks APIs.

Configuration is available at:

HyWorks Controller Management Console > Settings > General > API Clients (BETA)

Important

This feature is marked as Beta. Additional development or customization may be required based on specific integration requirements.

Console Connect for Proxmox VMs

Console Connect provides direct console access to virtual machines. This allows users to work with VMs even when:

  • The VM is on a different network.

  • The VM has no active network connectivity.

  • Full-tunnel VPN clients alter or restrict network access.

This feature was previously available for Hyper-V. With HyWorks v4.0, Console Connect support is now available for Proxmox virtual machines.

The feature requires integration with compatible Workspace clients.

  • Compatible Workspace Client Flavor and Versions: Not yet GA released. To be added as per the availability of the module.

Preserve MAC/Network Feature Extension to SCVMM

HyWorks supports preserving MAC addresses on on-premises hypervisors such as VMware and Nutanix. This capability has now been extended to SCVMM.

Full functionality requires integration with the Hyper-V connector.

  • Compatible Hyper-V Connector: The feature will be available as a spot patch in the latest connector release.
  • A combined Hyper-V/SCVMM connector release is planned for the following hotfix, with additional feature integrations expected.

HyLabs Features and Enhancements

New Events for Notifications

New events and time windows have been added for self-study and course reservations, enabling email notifications to selected audiences.

Self-study Reservations:

  • When Ended

  • When Expired

Course Reservations:

  • x days before Reservation Expires

  • When Ended

  • When Expired

Email Templates

HyLabs v4.0 introduces an Email Templates Configuration menu to define and manage email templates.

  • Templates are configured at the organization level.

  • Different organizations can have different templates.

System-Defined Email Templates

The following are the system default Email templates provided:

  • Default Course Template for HyLabs Admin Users

  • Default Course Template for HyLabs Participants

  • Default Self-Study Template for HyLabs Admin Users

  • Default Self-Study Template for HyLabs Participants

Enable Using Email Templates of the HyLabs Portal

Email templates must be enabled from:

HyLabs Portal > Default Reservation Settings > Use Email Templates

Admin Defined Templates

Apart from system-defined templates, administrators can create custom templates based on:

  • Specific event

  • Specific user category

Example: A custom template for Course Reservation - Create Event for participant users.

System Defined Variables and Definitions

While creating or editing templates:

  • A read-only section displays available variables and their definitions.

  • Helps administrators create accurate and meaningful templates

Email Templates Fallback Order

If Use Email Templates is disabled:

  • File-based templates are used (legacy behavior)

If Use Email Templates is enabled:

  • Priority# 1: Event and User Type–specific template

  • Priority# 2: Default templates from HyLabs Portal

Self-study Reservation Window

Self-study gold masters now support a Reservation Window configuration.

Administrators can define when self-studies are available using:

  • Reservation Windows: Enable or disable

    • Advance Booking [] days

      • Prevents very early reservations.

    • Allowed Time Windows

      • Allow all time between the specified Start Date and End Date.

      • Allow only specific one-time or recurring date/time windows.

    • Restrict Reservations On

      • None

      • Full Day on Specified Dates

      • Restrict only to specific time windows

Important

Properly configuring reservation windows helps optimize resource usage and manage user load efficiently.

Group/OU-based Assignments

HyLabs v4.0 extends reservation entitlements to directory groups and OUs from the configured authentication server, in addition to the existing user-based entitlements.

HyLabs Portal Changes

HyLabs administrators can configure groups or OUs from the following locations in the HyLabs Portal:

  • Add/Edit Course Wizard

  • Participant/ Incharge/ Assistant pages

  • Add/ Edit Reservation Wizard

CSV Import for Users

The HyLabs Users CSV now includes a column to define the Client Type, as shown below.

Example:

UseVDI, Role, Client Type, Display Name, Username, Class Code, Email, Realmname
1, Participant, g, ClientGroupTest, ClientGroupTest, CS

Client Type Values:

  • u: Users

  • g: Groups

  • o: OUs

Classification Rule: Directory Group Support

HyWorks already supports Group-based Classification Rules. This capability is now extended to HyLabs, allowing classification rules to be defined using Groups or OUs.

Limitations and Known Behavior with Group/OU-based Configurations

  • No Email Notifications for group/OU-based entitlements: Users who receive entitlements through Groups or OUs, and do not have a direct user configuration in HyWorks, will not receive email notifications.

  • Multiple roles via different groups: If various roles are assigned through different groups, the highest role will be applied in the following order: Incharge > Assistant > Participant.

Adding Users to Reservations

In previous versions, HyLabs supported only removing users from the Reservation wizard. In HyLabs v4.0, administrators can also add new users, groups, and OUs directly from the Add/Edit Reservation wizard.

Custom Computer Name Support

Earlier, HyLabs strictly followed a fixed naming convention for computers deployed using HyLabs:

  • 4-character computer name prefix + 6-character reservation ID + 4-digit number

In HyLabs v4.0, an option to specify a custom computer name is provided:

  • For Self-studies: While adding a self-study gold master, the following two options are displayed:

    • Use Provisioning Profile Computer/VM Name: Deployed VMs will continue to use the computer name as per the provisioning profile naming convention.

    • Override Default Computer/VM Name: Selecting this option lets you specify a custom computer name prefix of up to 11 characters, which will be suffixed with a hyphen (-) and a 4-digit number. Example: If the custom computer name is specified as ssjava, the computer names will be ssjava-0001, ssjava-0002, and so on.

  • For Course Reservations: While creating reservations, the Computer/VM Name configuration is displayed with the options Use Provisioning Profile Computer/VM Name and Override Default Computer/VM Name, with the exact specifications as described above.