Known Limitations and Issues of Connectors or Session Providers
- Last Updated Date: 22-Sep-2022
- Release: HyWorks v3.4
Note
The Known issues list is updated with every release. These is the current list of known issues.
Hyper-V Connector (Hyper-V/ SCVMM) Known Issues
| # | Subject |
|---|---|
| 23613 | Controller is unable to process, Hyper-V VMs having special character sequence "<?" or "[]" in the name. An example of process failure can be unable to get IP address. |
| 15298 15330 |
Hyper-V or SCVMM (Hyper-V connector) may intermittently go into unreachable state, without providing relevant logs on HyWorks Controller. Sometimes timeouts are observed. |
| 15249 | While deleting a provisioned desktop pool from an inactive Hyper-V connector, the actual VMs from Hyper-V or SCVMM are not deleted and also the administrator is not warned. |
| 14574 | Operational failures may occur if parallel operations (Delete VMs and Provisioning) is initiated on Hyper-V 2012R2 or 2016. Recommendations: While working with Hyper-V, careful provisioning and operations should be done. |
| 14501 | Hyper-V 2012 - Cloning will fail with object reference error if source VM name is having following special characters: ` ~ ! $ % ^ & ( ) [ ] { } \ |
| 14422 | [Hyper-V Connector - SCVMM] Replica is not deleted during recompose when clone type changed from Linked Clone to Full Clone Workaround: Cleanup of replica can be done manually.A separate controller patch can be availed. Kindly contact Accops Support team for the same. |
| 14420 | Linked clone or clone with Snapshot fails with SCVMM is gold image name is having more than 20 characters Workaround: Gold VM or Source VM name should be less than 18 characters.A separate controller patch can be availed. Kindly contact Accops Support team for the same. |
| 14419 | [Hyper-V/ SCVMM] Cloning failures due to special chars in Gold Image (Source VM) name or Snapshot name (Feature: Clone from Snapshot) Recommendations: Following special characters should not be used in Hyper-V or SCVMM source VM name or snapshot name. [For SCVMM] Chararacters not supported in - VM name: space,,?,:,<,>,/,|,\,",',{,} Characterss not supported in Snapshot name: `,&,\,",' [For Hyper-V] Chars not supported in VM name: ,?,:,<,>,/,|,\,",',{,},[,] |
| 14383 | Sometimes cloning fails on Hyper-V with error: Creating the disk at location Workaround: Reboot Hyper-V server. |
| 14382 | Installer cancellation fails with inappropriate error when Hyper-V Connector setup is cancelled from Platform Configuration Window. |
| 14381 | Hyper-V connector installer proceeds with 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 parallelly , because we are taking lock in clone task keep as known. |
| 14629 | Clone from Snapshot fails with an error as Unable to acquire a 'Delete' lock on object of type 'VirtualDVDDrive'. |
| 14624 | Sometimes SCVMM provider goes in Not Reachable state with error "The connection to the VMM management server localhost was lost". This happens due to heavy load on SCVMM and is not able to accept test connections from the connector. |
| 14316 | Installing Hyper-V connector with wrong platform (e.g. Selecting SCVMM while installing on Hyper-V) and configuring on controller results 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 previous version Recommendation: Uninstall any previous version and install new version. Hyper-V connector does not keep any information and thus data will be not be lost on un-installation and re-installation. Take backup of custom configuration before un-installation. |
| 6874 | Known Issues - Hyper-V/SCVMM |
| 6873 | With Hyper-V 2016 VM, DNS name is always shown as hostname of Hyper-V server. |
| 5420 | Cloning fails if communication with Hyper-V Connector (SCVMM) fails. |
| 3294 | Cloning fails on SCVMM 2016 due to task lock issue. Issue occurs whe Gold Image is modified from Hyper-V and local DVD drive is attached. Recommendation: Use gold master with no local DVD drive attached. |
Azure Connector Known Issues
| # | Subject |
|---|---|
| 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 are not yet supported on MS Azure. 3. SSE (CMK / CMK+PMK) based encryption is done after customization. |