Known Limitations and Issues of Connectors or Session Providers
- Last Updated on: 03-April-2025
- Release: HyWorks v3.4-SP2
Note
The known issues list is updated with every release. Listed below is the latest summary of issues.
Hyper-V Connector (Hyper-V/SCVMM) Known Issues
| Bug ID | Description |
|---|---|
| 38528 | Virtual machine cloning failure in SCVMM if VLAN ID is associated with the Gold Master. |
| 23613 | The controller cannot process Hyper-V VMs with special character sequences "< ?" or "[ ]" in their names. An example of a processing failure is being unable to obtain an IP address. |
| 15298 15330 |
Hyper-V or SCVMM (Hyper-V connector) may occasionally become unreachable without providing relevant logs on the HyWorks Controller. Timeouts are sometimes observed. |
| 15249 | When deleting a provisioned desktop pool from an inactive Hyper-V connector, the actual VMs in Hyper-V or SCVMM are not deleted, and the administrator is not notified. |
| 14574 | Operational failures can occur if parallel operations (deleting VMs and provisioning) are initiated on Hyper-V 2012 R2 or 2016. Recommendations: Careful provisioning and operational procedures should be followed while working with Hyper-V. |
| 14501 | Hyper-V 2012 - Cloning will fail with object reference error if the source VM name has the following special characters: ` ~! $ % ^ & ( ) [ ] { } . |
| 14422 | [Hyper-V Connector - SCVMM] he replica is not deleted during the recompose process when changing the clone type from Linked Clone to Full Clone. Workaround: The replica can be cleaned up manually. Additionally, a separate controller patch is available. Please contact the Accops Support team for assistance. |
| 14420 | If the gold image name exceeds 20 characters, creating a linked clone or a clone with a snapshot in SCVMM will fail. Workaround: Ensure that the name of the Gold VM or Source VM is less than 18 characters. Additionally, a separate controller patch is available. Please contact the Accops Support team for assistance. |
| 14419 | [Hyper-V/ SCVMM] Cloning failures due to special chars in Gold Image (Source VM) name or Snapshot name (Feature: Clone from Snapshot) Recommendations: The following special characters should not be used in Hyper-V or SCVMM source VM name or snapshot name. [For SCVMM] Characters not supported in - VM name: space,,?,:,<,>,/,|,\,",',{,} Characters not supported in Snapshot name: `,&,\,",' [For Hyper-V] Characters not supported in VM name: ,?,:,<,>,/,|,\,",',{,},[,]. |
| 14383 | Sometimes, cloning fails on Hyper-V with the error: Creating the disk at location Workaround: Reboot the Hyper-V server. |
| 14382 | Installer cancellation fails with an inappropriate error when Hyper-V Connector setup is cancelled from the Platform Configuration Window. |
| 14381 | Hyper-V connector installer proceeds with the local system account even when credentials are given as administrator without domain name Workaround: Provide credentials as hostname\username. |
| 14380 | Hyper-V connector installer takes time when setting credentials (not using Local System Account). |
| 14345 | Hyper-V cloning will not happen in parallel but happens one after another because we are taking locks in clone tasks. |
| 14629 | Clone from Snapshot fails with an error as Unable to acquire a 'Delete' lock on object of type VirtualDVDDrive. |
| 14624 | Sometimes, the SCVMM provider goes into the Not Reachable state with the error "The connection to the VMM management server localhost was lost". This happens due to a heavy load on SCVMM, and it is not able to accept test connections from the connector. |
| 14316 | Installing the Hyper-V connector on an incorrect platform, such as selecting SCVMM while installing on Hyper-V, and configuring it on the controller will result in errors on the controller. |
| 8953 | Preserve MAC address on recompose feature is not supported with Hyper-V or SCVMM. |
| 6877 | Direct upgrade of Hyper-V connector is not supported and requires un-installation of the previous version Recommendation: Uninstall any previous version and install the new version. Hyper-V connector does not keep any information, and thus data will be not be lost on uninstallation and re-installation. Take a backup of the custom configuration before uninstallation. |
| 6874 | Known Issues - Hyper-V/SCVMM |
| 6873 | With Hyper-V 2016 VM, the DNS name is always shown as the hostname of the Hyper-V server. |
| 5420 | Cloning fails if communication with the Hyper-V Connector (SCVMM) fails. |
| 3294 | Cloning fails on SCVMM 2016 due to a task lock issue. The issue occurs when Gold Image is modified from Hyper-V and a local DVD drive is attached. Recommendation: Use gold master with no local DVD drive attached. |
Azure Connector Known Issues
| Bug ID | Description |
|---|---|
| 16160 | Limitations of disk encryption with HyWorks on Azure: 1. If controller service goes down when encryption is running, then status will not get updated and only workaround is to recreate the VM. 2. Disk encryption with Linux VMs is not yet supported on MS Azure. 3. SSE (CMK / CMK+PMK) based encryption is done after customization. |
AWS Connector Known Issues
| Bug ID | Description |
|---|---|
| 26461 | The virtual IP feature for shared hosted desktops or virtual applications is not supported with any cloud provider, i.e., Azure, AWS, or Oracle. |
Nutanix Known Issues
| Bug ID | Description |
|---|---|
| 30866 | With Nutanix as the connector, the hostname of the configured VMs is not shown in the HyWorks Controller Management Console. Workaround: Configure VM Scale booster to get this information via DVM Push feature. |
| 26042 | All the cloned VMs are created on the same storage container as the gold master and not on the specified storage container at the time of cloning with Nutanix. |