Bug Fixes
The following bugs have been fixed in the HyWorks v4.1-Hotfix2 release:
HyWorks Controller and Server-side Modules
| Bug ID | Description |
|---|---|
| 72226 | Single-session non-persistent desktops were displayed with an incorrect orange status and snapshot error on Desktops > Personal. The issue had no functional impact and was automatically corrected after the user logged out. This issue has been fixed in this release. |
| 72102 | The Assigned Client field displayed the registered device UUID for device-based desktop pools. Fixed in HyWorks v4.1-HF2. |
| 72083 | In rare race conditions, HyWorks assigned VMs from the Master Pool that were marked for graceful recompose, resulting in session launch failures or disconnections. This issue has been fixed in this release. |
| 72082 / 71994 | With the Controller and Database servers configured in different time zones, incorrect connection times were displayed for user and desktop sessions. This issue has been fixed in this release. |
| 71994 | Incorrect idle timeout logs are generated when a user connects/disconnects and the controller and database servers are in different time zones. Latest VM Scale Booster release must be used for this release. |
| 71990 | Power operations stopped executing with the Azure connector when previous power operation jobs remained stuck indefinitely. Power operation timeouts have been implemented to prevent jobs from being held indefinitely. |
| 71858 | Recompose operations were not executed automatically, although desktop recreation from the same pool worked correctly. Multiple issues affecting graceful recompose triggering and job execution were identified, and they have been fixed in this release. |
| 71515 | Management operations were allowed from broker nodes, causing administrative activities and logs to be generated on those nodes. Management console restrictions have been implemented for broker nodes. |
| 71483 / 70895 | In some cases, users could not connect to shared-hosted desktops and received errors indicating that the desktop was not assigned or could not be found in the user session. This issue has been fixed in this release. |
| 70309 | With image-based cloning in Azure, the additional disk storage type, HDD LRS, was not correctly retained, and the cloned VMs were created with SSD LRS instead. This issue has been fixed in this release. |
| 69180 | With VM Reuse disabled, reservation VMs were destroyed during redeployment, but the old replica was reused, resulting in VMs being deployed without the selected snapshot. This issue has been fixed in this release. |
| 68983 | The Azure connector could become unreachable when multiple deployments were running in parallel due to exceeded Azure API limits. Azure API throttling and enhanced integration have been implemented to prevent such failures. |
| 69786 | Users with a custom role having desktop pool management permissions could not access the Pools page in the HyWorks Controller Management Console. This issue has been fixed in this release. |