HyWorks Controller Known Issues
- Last Updated Date: 03-Apr-2025
- Release: HyWorks v3.4-SP2
Note
The known issues list is updated with every release. Listed below is the latest summary of issues.
| Bug ID | Description |
|---|---|
| 43644 | On HyWorks, the logs do not have the username of the person who has updated the authentication server settings. |
| 42752 | HyWorks continues to use the old cached secret for the Azure Connector even after changing it from the HyWorks Management Console and requires the HyWorks Controller Service to be restarted. Solution: The HyWorks Controller service has to be restarted on the management node. |
| 42142 | !!! Important The known issues list is updated with every release. Any old setups (v3.4-SP1 HFx) having Message Queue configured from HyWorks Controller Management Console will require an update MQ password after upgrade to 3.4 SP2. Cause: This has started occurring because of the encryption being added to the MQ password from v3.4-SP2. |
| 41507 | Users are unable to log into a new organization in HyWorks if they already have any session with the same device in any other organization. Error: 'failed to register device'. Workaround: Either log in to another organization and clear the session, then attempt to log in to the new organization or get the administrator to delete the old device and session from the other organization. |
| 41471 | Task manager is not provided on the application session page and is available only on desktop sessions. |
| 40899 | Recompose operations may fail if the internal ID of the Gold master has changed in HyWorks. Cause: The Original GM is deleted from hypervisor, and during the update of the VM list, the controller has got another VM having same name. |
| 40731 | User session may get cleaned-up by HyWorks because associated desktop session got removed with "Desktop Session Monitoring on RDP Status type" enabled. Cause: Issue occurs when desktop session from HyLite gets disconnected and then reconnected due to network glitch but the desktop session entry has removed from Controller side. |
| 40649 | HyWorks does not throw correctly leading error when it fails to connect to Azure due internet issues. |
| 40381 | Controller servers in secondary/Fault/Maintenance mode denies the communication to the clients with message "Server mode do not allow this operation" but does not log anything. |
| 40231 | "Move to version" failure logs do not have information of VM and Pool and thus do not correctly lead for identification of the affected VM and Desktop Pool. |
| 39959 | HyWorks Controller Active-passive setups may go into error state with DB sync getting failed with the error "remote peer is outdated". Cause: This has observed for the setups where the syncing has not happened from a long time between primary and secondary node and then it attempts to sync. |
| 38952 | In some rare cases pool cloning is not getting initiated on pool save and update operations performed from the Management Console. |
| 38528 | Virtual machine cloning failures in SCVMM if VLAN ID is associated with the Gold Master. |
| 38265 | VM scale booster may update the wrong RDP session when multiple entries with the same desktop ID are pushed from desktop agent side. |
| 38232 | In a very isolated case new version is not getting created for a specific pool after version '9' with no clear error in HyWorks Controller logs. Workaround: Restart HyWorks Controller service or switch to the secondary HyWorks Controller and create version from new primary server. |
| 38191 | Proxy configuration saved in EDC.service.exe config file gets removed after upgrading HyWorks Controller and has to be reconfigured post upgrade. |
| 37556 | In some rare cases the Management console became inaccessible after some Windows updates on Windows 2019 servers. Workaround: Uninstall and reinstall IIS role from Windows Server and then repair the HyWorks Controller Management Console. |
| 37521 | Desktop agent may report HyWorks detected address (GW address or visible network) as WAN IP to ARS when directly connecting via HyWorks Controller. Cause: HyWorks uses visible network as WAN IP if not reported by client. |
| 37322 | In following cases, desktop pools are not listed for scheduled actions and thus administrator may not get clear leads on next action: 1. Pool having only version with non-zero count of graceful recompose will not be visible and admin will not be knowing. 2. When limited is set to non-zero then while creating a schedule action for move to version, Pool name is not listed and admin is not aware about this. |
| 36984 | In an isolated case Message Queue user created with the script having specific set of password is not able to login into rabbitqa console and giving authentication failed error. Workaround: Try to reset and use different password avoiding the not working set. |
| 36595 | Action processor works on primary only and thus, if it stops working with other modules (Controller, Scheduler services) still working, the features associated like scheduled actions or capacity planning will not work. |
| 35800 | Change in group membership of a user will not reflect on HyWorks desktop/app access unless user logs-in again. The AD group based classification rule does the calculation on logon. |
| 35736 | Classification Rule recalculation on Connect Desktop happens only in case of HyLite and does not work with HyDesk Client. Classification rule recalculation on Connect Application is not supported, its supported for connect desktop only. |
| 35431 | HyWorks default advance configurations considers datastore and hosts represented with grey color (disconnected or lost communication), though having least priority. Workaround: Change from HyWorks Advance settings to allow only on specific category of hosts and datastores. |
| 34924 | In some very rare case recompose didn't get initiated (both Forceful and Graceful) with no error logs. Workaround: Switching to other management node and initiating may work or restart HyWorks Controller service and try the operations again. |
| 34756 | Syslog setting doesn't get synced with other controller nodes and have to be configured on all nodes. |
| 34735 | In a rare case, HyPrep was not initiated for multiple VMs deployed through self-study reservations. Cause: Due to duplicate IPs and VMs not deleted from past reservations. |
| 34607 | Some logs of child organization get created in default organization. Downloading logs specific to the organization will not have those logs created in default organizations. Workaround: Download logs of all organizations for troubleshooting. |
| 34448 | Unable to update expired password (used for domain joining and trust relationship reset) in the Customization tab until recompose is initiated. Workaround: New feature to make versions and update password for specific versions are available and can be used. |
| 34216 | In a rare case, logs for making user sessions idle were not created, and thus caused confusion as how the sessions were terminated without appropriate logs. |
| 34159 | With advance setting "Allow Org change" enabled and user with session in one organization, tries to switch to another, the session will be terminated without any notification to the user. Impact: The User may lose any unsaved data in the sessions. Important: This is not the default configuration. |
| 34151 | With multiple datastores selected and no resource pool specified, HyWorks may attempt to clone on the resource pool of the best host and may fail if permissions are not there. Solution: With multiple datastore selections, the admin should have rights on all objects (hosts/ resource pools) associated with the datastore. |
| 33696 | For non-persistent desktop pools, assigning VMs (having restore point creation got failed) from the management console is allowed. |
| 33562 | With too many devices, short device heartbeats and fast login rate database operations may become bottlenecked and cause functional failures, including user login. |
| 33492 | Using the email attribute for login last login time is not updated for existing users, and for new users, entries do not get created in Registered Users. |
| 33361 | With the 'Disable RDP port ping for session host machine' flag set as 'False' from Advance Settings, HyWorks may skip checking RDP port connectivity in some cases. Impact: With certain conditions where only the RDP port has become unreachable, the Controller may continue to give sessions and thus fail the connections in the end. |
| 32528 | Power Operations initiated from HyWorks Client may fail if broker nodes are not having connectivity to the Hyper-V provider. |
| 32481 | OS Disk size is copied from the image and not copied from GM while cloning from Image. |
| 32162 | HyWorks Controller service can not be configured with a gMSA account to connect with an MS SQL server. Issue - Controller service and Licensing service fails to start when configured with service logon account as gMSA account. |
| 32107 | MSRA (by default) does not take the session of the provided session ID (in case of multiple sessions) but prompts the administrator with the list of sessions. |
| 30952 | On the HyLabs portal, the connect button is not automatically updated for users when the status is changed. |
| 30914 | HyWorks Controller allows the addition of nodes in a cluster with different time zones in a setup without any warning or errors but causes functional failure. |
| 30352 | If Spare VM creation fails for a floating desktop pool, the next spare VM creation is not triggered automatically and may cause connection failures to new users as no spare VMs will be available. |
| 29930 | Applying license in a multi-node setup is very tedious and requires multiple steps for each node. |
| 29926 | HyWorks does not retain the network information of VMs whose cloning has failed, and thus, even if the preserve network is enabled, the newly created VMs will not have the information. |
| 29832 | A replica gets deleted on deleting the linked cloned pool when the admin has checked the option to retain the desktops option. |
| 29656 | In some rare cases, the managed SHD VM entry is not removed from the load-balancing page on deleting the cloned SHD VM from the VMs page, and the status of the shared desktop is inactive. |
| 29213 | Resource Group could not be created.' Errors are logged when the resource group is not available in the AWS region. |
| 29079 | Failsafe failed to work with AWS/Oracle connectivity is down from HyWorks Controller. |
| 29040 | Spare VM create operation gets initiated by the broker node if the trigger has come because of login or other brokering operation. Thus, provider connectivity is needed from management and broker nodes. Failing to have connectivity to the provider may cause functional failures. |
| 28559 | In some rare cases, pool status is not updated even after cloning and Hyprep completion, and cloning completed logs are not logged on the controller. |
| 28430 | Could not retrieve Desktops. Session Provider is missing or deleted' errors observed after updating the desktop pool in some cases with no impact on functional aspects. |
| 28356 | The controller creates only a single replica VM, even when the Concurrent Full Clone flat is set for more than one. |
| 28222 | In some cases, 'Object reference not set to an instance of an object' errors are thrown when desktop cloning has failed due to connectivity problems with the provider. |
| 27761 | In a very rare incident already applied production license got corrupted on applying evaluation license. |
| 26745 | In some rare cases provider sync is getting failed due to DB deadlock issue. Workaround: Periodic server restart may help in overcoming these issues. Also Desktop provider cache update can be made false to improve. |
| 26515 | Deployment settings such as Network preserve, Cloned VM deployment settings, Encryption type, DVM reset are not getting saved in version details. |
| 26215 | With deployment settings being kept as default, all the cloned VMs are getting cloned on a single host on which gold master is running, even when the gold master is in cluster. Workaround: Make sure to specify deployment settings to be deployed at the cluster level. |
| 25937 | Secondary AD does not get synced in DCDR, if primary AD is already synced on DR site and 'AUTHENTICATIONSERVERSSYNCEDONDR' set as False. Workaround: Manually add the secondary AD in DR side. |
| 25685 | DCDR syncs License distributions on Controller and thus makes it compulsory to have same licenses on both DC and DR sites. Having different configuration may cause licensing issues. |
| 25659 | Even though User initiates the Power operations on VMs, the log is getting generated again system user in the Controller logs. |
| 25346 | Controller continues to show old platform for logged in user and does not refreshes the platform information. |
| 24997 | Same users from different authentication server can be added, if configurations are changed in auth-domain, e.g. auth-domain configuration is changed from built-in/built-in to LDAP/built-in or vice versa. Impact: The duplicate entries may confuse administrator and also may result in login or authorization failures sometimes. Recommendations: The organization configurations should be planned well so that it does not require change. Even if it needed change, clean-up of HyWorks should be done to remove all users from previous auth-domain configurations. |
| 24885 22968 |
Oracle Data Disk and OS Disk snapshot is not getting deleted in set time and in case of recompose the old snapshot may be used for provisioning causing the changes done on Gold master to be ignored. |
| 24678 | Controller creates an error log if user refreshes the app list on client side and previously some virtual apps in remote app mode are opened and then closed. Error log: No App session found to reconnect for User 'Username'. |
| 24527 | In some rare cases VM deletion was failed with error "The Object context instance has been disposed and can no longer be used for operations that require a connection", while deleting the desktop pool. Workaround: Manually remove the VM from HyWorks and respective provider. |
| 24380 | Password change may fail with exception, if port 636 is not reachable from HyWorks Controller or appropriate certificate configurations are not done on active directory server and option 6 is used for active directory connection. Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host |
| 24373 | HyWorks Controller does not log VM image creation on AWS. There is no impact of this but eventually can create some confusion as VM image deletion logs are generated after cloning is completed. |
| 23805 | Provisioned SHDs published as physical PCs are not responding without showing error displayed. The issue is because, all the physical VMs added with same IP address are going to have duplicate IP and in that case controller does not show agent status. |
| 21958 | Client entry is not getting updated after updating DN for a user and so multiple client entries are created. |
| 21829 | By default for fresh controller installation, with active directory option# 6 for user authentication and authorization, built-in groups and nested groups do not work in HyWorks Controller. If required it can be changed from HyWorks Controller > Advance Settings. |
| 21731 | Controller does not create synchronization logs for a very long period of time when the secondary server with a very large number of records has been added to a controller. |
| 21724 | SQL transactions fails on the Controller, when too many devices (100K) are registered. |
| 21287 | With small timeouts on HyWorks (< 5 minutes), sessions taken from HyLite may get logged out abruptly though user is working. This happens because the default sync time between HyLite and Controller is 5 minutes. It is recommended to have timeouts more than 10 minutes, when delivering with HyLite. |
| 21044 | Controller access via VIP does not work, if network adapter used for VIP configuration is having space in it. Workaround: Change network adapter name to have no spaces and same name on both controllers. |
| 20866 | Controller sets display name same as username while importing users from LDAP and does not use the actual display name configured on LDAP. |
| 20800 | On initiating sync session info action on inactive session provider, controller displays a success status but does not perform any sync operation. The behavior is also different, when performing the same operation on session team with inactive session provider where appropriate logs will be created. |
| 20733 | Active directory server fails to be added into HyWorks, having following policy enabled: Policy: "Domain controller: LDAP server signing requirements" enabled and configured as "Require signing" Exception: Additional non-parsable characters are at the end of the string |
| 20616 | With too many records for synchronization (more than 100000), cluster configuration fails and primary server may go into fault mode. Workaround: Create secondary server with backup of primary database and then add to HA, avoiding too much synchronization. |
| 20296 | Adding a deployed shared hosted desktop pool creates a team with same name as desktop pool name but updating the desktop pool name does not update the team name. |
| 20202 | Network Settings details are not integrated in CSV export from session teams page. |
| 20129 18966 |
Controller does not support DVM Tools - Lite upgrade. Provisioned SHDs shown in VMs page can be incorrectly upgraded to DVM tools instead of Lite, because of above issue and may cause functional issues. |
| 20124 | Reason of service not responding for Linux session host server is shown as "Feature not available" and may cause little confusion. |
| 20119 | If a Windows session host server configured in HyWorks is powered-off, it can create a confusing log. Log: The Session Provider 'provider name' is not reachable. More Info :Unable to connect to the Session Provider hosted at 'Not Available'. Reason: Unable to parse URI 'http://Not Available, Reason: Invalid URI: The hostname could not be parsed.. |
| 20009 | In some cases, HyWorks may log an error while deleting desktop pool, though related objects are deleted successfully. Error: Store update, insert, or delete statement affected an unexpected number of rows (0). Entities may have been modified or deleted since entities were loaded. |
| 19984 | Configuring static IP address on Gold master may result in duplicate IPs in the network post provisioning. |
| 19983 | Controller may fail to delete a device having associated session and attempts to register into another organization. Ideally Controller should delete the associated sessions also. |
| 19868 | The shutdown operation on Linux VMs is kept on hold, if someone has logged-in to the VM from hypervisor console session. |
| 19664 | Controller lists all attached VIPs, while trying to change primary IP for the VM. Ideally VIPs should not be listed as they are not always attached to virtual machines. |
| 19560 | Saving a session team with a very long range of VIP may get stuck and cause high resource (memory/CPU) utilization by controller service. Workaround: Create some small network range and configure it on team. |
| 19091 | Controller by default uses the primary or first IP on the network interface added on Azure VM, though VM has multiple IP addresses configured on network interface. Option to choose primary IP will not work for Azure provider VMs. |
| 19038 | If a permanent VIP is having issue, the user session will be rejected unless the issue is solved or a new VIP is assigned. |
| 18830 | Controller may intermittently show error "Error while getting device software information for EDCA00MAC000", causing some confusion. |
| 18507 | With too many users connecting a time (more than 10 users per second) |
| 18327 | Controller transactions with SQL may get failed with timeout exception if database diagram is created. Usually database diagram is created when user clicks on it and it checks with user to create it. |
| 18078 | In case of domain controllers are deployed in child-parent configuration and HyWorks is configured with child domain, it does not fetch groups or OUs from parent domain controller. |
| 18015 | Changes to management are not forbidden from session nodes, so if any deployment is having management console installed on session nodes, changes can be done from session nodes as well. |
| 18006 | Controller displays a confusing error invalid username and password, when SAM Account Name is to be used for logon but truncate is off and user is using username@domain-name or domain-name/username to sign-in. |
| 14404 | If special characters %/\" are included in Gold Image (Source VM) name or snapshot name for vCenter, snapshot of replica is getting created every time after increasing the count of VM for Persistent pool of type linked clone Avoid using special characters in Gold Image (Source VM) name or snapshot name. |
| 14376 | Incorrect error message is displayed in Test connection of AD, when configured admin account is locked |
| 14375 | If the user has changed password, Auth domain (AD/Built-in) and synchronization as Do not create/ Manual, connection to dedicated desktop fails. |
| 14305 | [HA] Removal of controller from HA setup leave Tracking Table in DB. |
| 14256 | With CredSSP enabled, sessions from Linux based endpoints will fail because of protocol negotiation. Workaround: Create a separate connection profile for Linux based endpoints. |
| 14083 | Deleting a node from HyWorks Controller active-active setup requires node to be destroyed before removal as on service start the node may again get added. |
| 13923 | Controller will fail to authenticate users, who are member of "CNF" group in AD. Exception: XML parsing: line 1, character 1744, illegal xml character. How is CNF group created: If an object is created on one domain controller and an object with the same name is created in the same container on another domain controller before replication occurs, it creates an object name conflict. Active Directory automatically changes the relative distinguished name of the object with the earlier timestamp to a unique name. Reference: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727059(v=technet.10)?redirectedfrom=MSDN |
| 13889 | Internal configuration is displayed in the error message when user is not able to connect to the AD server. |
| 13767 | Even when the single Monitor usage is set in the Endpoint, user is able to use multiple monitors. |
| 13667 | User's are not notified about the destruction of desktops they are working on. |
| 13256 | Enable DVM reset option is not working for SHD desktop pool due to which snapshot is not created. |
| 13189 | User friendly logs are not displayed when controller tries to get the weight of SHD servers which is not in a reachable state. |
| 12972 | While performing power operation, internal configuration is displayed in the Controller logs. Due to this, Administrator may not understand which desktop is affected. |
| 12971 | Connect desktop logs are not user friendly. |
| 12942 | It is not possible to delete vCenter server with 6000 or more VMs. |
| 12871 | AD User is not able to log in to client with 256 character length password. |
| 12792 | Unpredictable behavior when Round robin load balancing is used with multiple teams. |
| 12564 | With UPN as logon attribute, following special characters do not work in username “|\@”` |
| 12561 | User, Group or OU with pipe | character is not supported in HyWorks so user logon fails |
| 12547 | Fetching OU in entitlements fails if search string includes bracket ( ). Workaround: Search without bracket |
| 12539 | If backslash() is included in username, user might have login issues while logging from client using UPN. |
| 12518 | Secondary controller hangs and is not able to sync if primary controller is having a large amount of data (1L rows). |
| 12517 | Authorization with built-in and nested AD group does not work when Group retrieval type is set to 6 Workaround: Add entitlement using groups created manually and specific groups only. |
| 12458 | Desktop provisioning continues even when enough resources are not available on desktop provider (VMware, Nutanix, Azure, Hyper-V). |
| 12439 | Unable to delete the AD when reservations created by AD user exists in RMS Workaround: Delete all the associated objects from database before removing AD. |
| 12436 | User friendly errors are not logged when cloning fails and Administrator has to check respective Hypervisor or cloud logs. |
| 12434 | In many cases, test connection failure may not give detailed exception and thus more analysis of controller/ AD server is required. |
| 12432 | Controller fails to fetch OU details if domain name provided in AD configuration is not same as NetBIOS name. |
| 12406 | Desktop status is shown incorrectly as Not synced instead of Missing if configured DVM is deleted from the session provider. |
| 12403 | Misleading status of desktop VM, when user initiates shutdown internally. HyWorks does not support stop with de-allocation and because power-off is equivalent to stop with de-allocation, incorrect status is displayed. |
| 12402 | Status of Desktop agent is Not Responding, when multiple VMs with different IP addresses are present in HyWorks with same IP address. |
| 12399 | HyWorks Controller Logs : Username and APPS name is not appearing in Log Details. |
| 12384 | Controller Installation on WVD: 1. IIS installation externally (Class not registered) 2. MSMQ installation externally ([RMSBackgroundWorker] while monitoring import events). |
| 12371 | [Azure] Log message incorrectly states that recreation of Desktop VM is supported when it is possible to recreate Desktop VMs |
| 12341 | Large deployments with 10000 users might fail due to application connection issues. |
| 13334 | In User Details, primary AD server details are displayed even when user is authorized from the secondary server. |
| 12328 | AD server configuration fails with error "The specified forest does not exist or cannot be contacted." Workaround: Enable Skip attribute verification. |
| 12319 | Skip Login Attribute Verification settings is not retained after updating AD server Workaround: Check this configuration every time active directory configuration is updated. |
| 12317 | Session nodes logs provide misleading information when management nodes get switched ON. |
| 12187 | Incorrect error message shown to user when user account has expired in AD and Group retrieval type is set as '3' |
| 11950 | When the Controllers in HA cluster are configured with different ports than information about different ports is not visible on client Workaround: Use same port for both the Controllers. |
| 11884 | Controller installation on other than default port does not get updated in management console configuration. Workaround: Update Management console configuration file to point to modified ports. |
| 11784 | [Azure] FQDN of cloned VM not reflecting on desktop VM page. |
| 11780 | On user session reconnection (re-login by user), controller may give reconnect of disconnected RDS session with no app running in some rare case, where user has closed the remote app before the disconnection. |
| 11635 | Session host server resource data does not get updated in real time and thus with adaptive load balancing server score will be updated after 30 second duration and may cause session from same server for some time until score gets updated. |
| - | Deleting a node from HyWorks Controller active-active setup will require node to be destroyed before removal as on service start the node may again get added. |
| 11349 | External load balancers must use HyWorks health probe service to detect node health, using port reachability may cause failure in detection of node down due to reasons such as licensing or SQL connection issues. |
| 11334 | Current weighted round robin does not work in the expected manner and may end up giving more session than expected. |
| 11330 | HyWorks uses Least connection load mechanism to serve the session when multiple sessions are requested at the same time. Due to this it might happen that multiple sessions may get served by the same server. |
| 11263 | Database gets deleted incorrectly if it is pointed at the time of installing new node and the installation fails. Workaround: Installation should be done using dummy database and node should be configured in the cluster post installation. |
| - | Database gets deleted after session node is uninstalled. This happens because by default database is removed after uninstalling node. Workaround: Uncheck Post installation database removal permission. |
| 10992 | When LDAP server is configured over SSL, it takes time to authorize/authenticate as Controller tries to resolve additional hosts. Workaround: Add appropriate host entry to reduce host resolution interval. |
| 10575 | Sometimes power off operation does not work with Nutanix dedicated session provider. |
| 10327 | Nutanix may keep old IP cache for some time and thus may result giving two IPs to HyWorks Controller causing issues. Workaround: Configure controller to use appropriate IP filtering. |
| 9569 | HyWorks may not fail to authorize from configuration using AD for authentication and built-in for authorization but using UPN as logon attribute. |
| 9519 | HyWorks sends logs to Accops Reporting Server or Syslog only once. Due to this, if it fails to send logs, these logs are lost and reports does not show data points of that duration. |
| 9493 | HyWorks database restore fails if the parameters - Username, password, SQL server version, location; configured in the new SQL server and the one which is to be restored are same. |
| 8555 | HyWorks may not work correctly with proxy authentication server e.g. Accops directory server. |
| 8439 | Shadow sessions are created using the connection profile of the actual user session. Due to this, it might happen that Shadow session may not have features it actually requires. E.g. In user session, connection bar is disabled but in shadow session it will be needed. |
| - | Base DN and User DN is mandatory for configuring directory searcher option as LDAP searcher from advance config. |
| - | As Controller requires FQDN to communicate with AD over SSL, if Controller needs to point to a specific AD instance, its host entries must be created otherwise Controller will continue to use first resolved AD. With multiple session manager nodes, this is required for all the nodes. |
| - | DVM Power Policies in DVM Pool may conflict with Auto-login (Auto-login will keep the machine powered-on whereas power policy may try to power-off the DVMs). Administrators are required to keep power policies as default or disabled in DVM pools if intending to have auto login on registered devices. |
| 7478 | Power off, Reset or suspend events are not known to DVM agent and thus controller will not be notified immediately. Power status will be updated as per timeouts in HyWorks Controller. |
| 7466 | DVM Push will not work with SQL installed in Windows authentication mode only. |
| 7082 | Virtual IP for HA script does not support Ethernet name with space. |
| 6380 | Sometimes error log 'Object reference not set to an instance of an object' are generated, while restarting session host server. |
| 6330 | Logs are not generated, when desktop is not assigned to users if they are in maintenance mode on desktop pool. |
| 6114 | HyWorks Controller requires restart to refresh time zone details. |
| 6101 | Unable to delete organization though all visible objects in organizations are deleted. Workaround: Before deleting organization, remove all the table references mentioned in logs. |
| 5729 | In some cases, HyWorks Controller installer is unable to detect correct OS type & previous installation of controller. |
| 5698 | Sometimes, select checkpoint in desktop pool wizard does not work in single click and may require reselection. |
| 5681 | With large deployments Hyper-V connector may stop responding and communication issues may occur due to timeouts or SSL errors. |
| 5375 | No desktop VM's are seen in Desktop VM tab of management console with zoomed in browser settings. |
| 5279 | Unable to authorize using built-in group Domain Users, when controller is not in same domain as configured AD (Both as authentication and authorization server). |
| 5278 | In Desktop pools - OU with special character is shown with garbage characters and after saving changes to "on" string |
| 5273 | HyWorks Controller does not support provisioning using templates with vCenter Server dedicated session provider. |
| 5171 | Pervious entitlements with authorization AD can login into client when authorization is changed to built-in when removal of entitlements. |
| 5105 | Some threads continue to connect to dedicated session provider though it’s made inactive. |
| 5083 | Updated AD group membership change is not getting fetched and thus failing to assign the desktops/apps runtime. Workaround: Use advanced settings to use alternate methods of fetching groups. |
| 5026 | Desktop pools and reservations become accessible once associated client groups are deleted. |
| 4840 | Gold master concurrent access is not restricted, and hence multiple users can access desktops which supports multi-user sessions e.g. Linux desktops. |
Controller Management Console Known Issues
| Bug ID | Description |
|---|---|
| 42406 | "Max Transferable Content Limit" value is getting Reverted to KB post updating of Connection Profile. |
| 35390 | Admin does not have option to change VM deployment settings (e.g. use last known settings) while recreating individual VMs from the Desktops page. Workaround: The configurations have to be changed from the desktop pool settings. |
| 34487 | Downloading logs may fail with too many logs in specified date range to download logs from HyWorks Controller Management Console. |
| 34460 | Authentication Server Configuration: HyWorks continues to attempt to connect with AD with configured password and may get the user account locked if the user password has changed from AD side. |
| 34160 | Different source IPs (Different when accessed using https:// |
| 33778 | With IIS_Users not having sufficient permissions on MMC folder inside of HyWorks Controller installation directory, the download logs option do not work and admin is not shown any error messages. Workaround: The user permissions can be configured to make it working. The issue is not common and may have occurred because of explicit user/ permission removal. |
| 32967 | Admin is not informed while selecting capacity plan associated desktops for scheduled actions but later actions are skipped because of the same reason. |
| 32457 | With the option 'Enable shortcut to minimize window [Alt + Ctrl + Shift] (Windows only)' enabled in connection profile: On clicking on restore button on the desktop session, the session gets minimized. |
| 30072 | The filtering option does not have option to filter-out physical desktops by its type. |
| 27859 | The time shown for "Info Last Updated on" in exported CSV of Desktops, is not in IST or local timezone but in UST format. |
| 27320 | On exporting the pool details with CSV pool having display name in Japanese character are being imported with some garbage characters instead of Japanese strings. |
| 26323 | A misleading error "There is no authentication server configured" is shown while searching for a user with dot and auth-domain configuration is using built-in users. |
| 26295 | Login with HySecure link becomes visible though not enabled while trying to login with invalid credentials into management Console. |
| 25963 | Option to enable DVM Reset is disabled, while adding new persistent desktop pool with dynamic provisioning. The issue is affecting all connectors: Nutanix, vCenter, SCVMM etc. |
| 25922 | Incorrect Desktop ready count is showing on pools page when new SHD is added using copy operation. |
| 25232 | On enabling Unassign on VDI log off, warning is displayed that hybrid mode is not enabled even when the hybrid mode enabled. |
| 24872 | It is possible to add duplicate AWS connector using the same information. |
| 24869 | A non-friendly error message is displayed if AWS connector is added with invalid credentials. |
| 24866 | A misleading error "One or more error occurred" is shown when administrator tries to add Oracle as connector in HyWorks with any of the incorrect details. |
| 24804 | Management Console fails to open, where its installed on Windows 2012R2 or lower with internal error 500.19. Workaround: Delete the following flag from web.config: |
| 22523 | HyLite does not use the portal settings of HyWorks - Organization and thus all the customization have to be run via HySecure management console or HyLite configurations. |
| 21121 | HyWorks management console UI gets distorted while searching the groups or OUs with special characters e.g. pipe "|". |
| 20961 | Saving a session team after assigning more than 2.5K applications, management console becomes inaccessible. |
| 20959 | Server page in Management console displays list of configured servers without IP address, if the ethernet card, holding the primary IP address used to configured server on HyWorks is deleted from the provider. |
| 20051 | Incorrect VIP is shown in dialog box while removing the Permanent VIP assignment for user from User details page. |
| 18827 | To play session recording using HyWorks management console, either appropriate certificate must be configured on the SRMS server or exception should be added on user's machine. To add exception: Get the complete recording URL by inspecting recording icon, open it in browser, when the warning is displayed, accept it to proceed. Now, the media or recordings can be played. |
| 18524 | Files deleted from the SRMS server by the administrator will not be removed from the management console list and will fail to play. |
| 18502 | Deleting a recording profile assigned to a connection profile fails but displays a success message and thus causes confusion and also functional issues. |
| 14424 | It is not possible to exit the Desktop pool wizard if the Administrator has specified a VM name prefix with unsupported chars and later corrected it |
| 14405 | Fetching Gold Master at the time of recompose results in an exception if the Gold Master name includes special characters. |
| 14386 | The error “Value cannot be null. Parameter name: source" is shown when a user who does not have edit permission on the capacity plan tries to edit any existing plan. |
| 14384 | Change mode reflects with quite a delayed response on UI and requires manual refresh. |
| 14371 | The DVM Reset option is getting enabled and editable on selecting recompose for a non-persistent pool, though no function impact even when unchecked. |
| 14368 | On re-editing the Dedicated Desktop pool, the section shown below Assign Desktop ‘on connect’ is not getting displayed. |
| 14365 | On enabling Unassign User on VDI Logoff during Desktop pool creation, it is showing a warning that Hybrid mode is not enabled even when the Hybrid mode is enabled. |
| 14324 | The adaptive load-balancing type option should not be visible for the Linux session team, as the monitoring service is not implemented in Linux SHD |
| 14314 | [Licensing] License is getting allocated to child Organization after 100% utilization in parent organization if licenses are all shared. |
| 14313 | [Licensing] Unable to update license if all the license is used (Reserved + Shared) with 100% utilized license to (all Reserved with unlimited check). |
| 14268 | Desktop VM page takes a long time to sync after deleting VM from it. |
| 14258 | The 'Browse' option should not be visible on the Server team page of the Linux application. |
| 14236 | In the Sessions Team page, the Session mode column is not applicable for an unmanaged session team but is still displayed. |
| 14228 | At times, when the user launches an application, the SHD session is launched instead of the application. |
| 14079 | 'Get icon automatically' option for application getting failed for Windows 2k19 server. |
| 14060 | Desktop removal on editing desktop pool is not working for Managed SHD pools. |
| 13808 | [3.2sp2+hf5/3.3 ]: Scrolling issue on left side tabs when using laptop touchpad. |
| 13510 | Select source VM test call fails in case of multiple IPs. |
| 13235 | It is possible to decrease the configured count of Maximum capacity than the already deployed desktop count for the SHD cloning pool. Ideally, it should not be possible to decrease. |
| 13207 | The controller is truncating the LDAP user who has leading and trailing spaces, making it impossible to log in to the Linux SHD. |
| 12977 | Manual assignment does not work when the user selects Group in Desktop Pool. |
| 12874 | Password field value visible, inspect and then by replacing password with text. |
| 11861 | Some labels or column values are different than their actual value in the database, and thus searches on those columns may not work as expected. |
| 7764 | Dashboard - The License section graph gets refreshed with abrupt flickering. |
| 7439 | Dedicated providers are added when they are unreachable with an active flag. |
| 7431 | The HyWorks management console session persists, so the user is able to access the Console even without a password by using the previous and next buttons of the browser. |
| 6712 | “Limit Single Instance per user” should be enabled and non-editable for Linux applications. |
| 6614 | Existing Custom URLs don't have the edit option. |
| 6923 | The same group/OU can be added multiple times while publishing applications. |
| 6666 | The device-based assignment gets removed for floating pools if the user from that device is logged off. |
| 6612 | The Linux SHD server is added incorrectly as Windows SHD. |
| 6125 | MS Edge - Unable to scroll using the mouse wheel once the User Sessions/Logs page is opened. |
| 5747 | Adding Application gets stuck in Loading state if size of Application Icon is greater than 3MB. |
| 5675 | With too many authentication servers or shared hosted desktops, the dashboard appears with lots of blank space. |
| 5611 | Search entry is removed on the Groups wizard after clicking Enter. |
| 5305 | After enabling the “Use Custom Client” window title, the “Delete shortcuts on exit" option exceeds the default page size. |
| 5288 | Launch mode for the application in the User Details page is always shown as Remote App. |
| 5284 | Display name in the User Details page displays garbage data if the user belongs to OU with all special characters. |
| 5277 | Unable to add OU with pipe "|" operator in its name in Entitlements. |
| 5276 | Incorrect data is displayed in Total powered on ready desktop VMs (includes shared hosted desktops as well) in event logs produced in HyWorks Controller. |
| 5275 | In the Add Desktop Pool wizard, sometimes the source VM does not get selected in a single click with the Microsoft SCVMM/Hyper-V dedicated session provider. |
| 5193 | Desktop pool is saved without assigning desktop to user in desktop assignment tab when auto-assignment is disabled. |
| 5191 | Group entitlements / User entitlements are not deleted from UI after deleting the group or user. |
| 5171 | Pervious entitlements with authorization AD can login into client when authorization is changed to built-in when removal of entitlements. |
| 5149 | User information from the User Details page is not deleted when built-in users are deleted. Trying to view user details will show an error on the page. |
| 5139 | The Linux app session should be removed from HyWorks manually if it is stuck in the initializing state. |
| 5129 | The same address can be added as primary and secondary authentication servers. |
| 3142 | Download logs fail with Management Console in Japanese with error-61 (Japanese OS). |
| 2042/ 42540 |
Updating the username and password for ESXi/vCenter Server for the first time fails due to an old key being used. Attempt to test the connection multiple times with the correct password, and it will show a success message in a couple of attempts. |
Upgrade Service Known Issues
| Bug ID | Description |
|---|---|
| 5027 | High memory consumption by Upgrade Service with too many upgrades initiated for DVM tools. |