Bug Fixes

HyWorks Controller and Server-side Components

The following bugs have been fixed in the HyWorks v4.1 release:

Bug Id	Description
67647	With non-persistent desktop pools, users who had recently accessed desktops were being logged out, and virtual desktops were immediately released and reset. Cause: Conflicting threads and race conditions in environments with very frequent user log-in and logout were causing this issue. Fix: Appropriate improvisations and conflict handling fixes are implemented to avoid such issues.
67464	VM cloning fails with the AWS connector for Gold masters having configuration as Proceed without key pair. Fix: The issue is fixed in the v4.1 release.
67027	The controller should not allow configuring multiple Proxmox nodes from the same cluster. Impact: Having multiple Proxmox nodes from the same cluster configured in the same HyWorks Controller may cause duplicate VM entries and result in functional failures. Fix: Restricting administrators from configuring multiple nodes from the Proxmox cluster is implemented in this v4.1 release.
66782	Periodic errors suggesting failure in sending desktop pool data to ARS servers were coming in some specific error conditions. The handling is improved in the v4.1 release to include a fix for this issue.
65692	The HyWorks Controller Management Console dashboard displays inconsistent resource (CPU/Memory/Disk) details because of performance counters being corrupted on the Windows server. Improved healing mechanisms are implemented in this release, v4.1, to bring the system to a working state.
65629	Improved Controller upgrade errors for SQL connection issues due to forced encryption or untrusted certificates on remote SQL servers. The message has been improved to highlight potential issues and solutions.
60247	With the SCVMM connector, recompose does not consistently delete all virtual machines and may leave some VMs unmanaged on the server. Fixes in HyWorks and Hyper-V Connector releases of v4.1 will help in overcoming this problem.