Skip to content

Known Issues

Note

Known issues list is being updated and accordingly release notes will also be updated.

HyWorks v3.3-R2 Known Issues

# Subject
17689 While upgrading from v3.3-GA+HF4 to v3.3-R2, to generate schedule Id, existing session teams must be updated at-least once.|
This is required only if deployment has to use automatic power management post upgrade.
17675 Schedule Service, Scheduler Worker and Action Processor exe are not having any icons and can be seen without icons in Task Manager
17595 On disabling the 'share client info' flag, client info registry is getting created in SHD for existing user, though not having any impact.
This is part of network activity monitoring of users, where no registries should be created after disabling share client info.
17564 Closing the remote app/shell app/SHD immediately after launching it then SRT file is not generated in Raw_data folder
17487 With hybrid mode enabled (VM Scale boosted based deployments), dedicated session disconnection/logout is not getting updated to HyWorks controller and thus affects the session monitoring.
17448 With session monitoring based on session, Linux VDI (Dedicated desktop and shared hosted desktop) session will not become idle and will remain always active.
17314 Intermittently cloning failed with Hyper-V with object reference error with no specific steps identified
17271 ContentRedirect registries are not getting removed on uninstallation of Session Server Extension and have to be removed manually for proper cleanup. There is no impact on functioning of system due to left-over registry entries.
17111 HyWorks re-includes residual VMs in desktop pool which were failed to delete on recompose, if the VMs are already powered on it can send re-sysprep it or it may not attempt to power-on it, if in powered-off state.
17106 On Nutanix, recompose getting failed due to failure in deletion of VMs (Provider went unreachable because of too many shutdown calls at the same time)
17091 Limitations of Power management for Managed Linux SHD pool
- No notifications will be shown to user for force logout or shutdown
17079 Post upgrade or installation of session host server, administrator is shown PowerShell windows on first logon
17059 [HyLabs] HyLabs will attempt to deploy all reservations on first deployment window itself, though some reservations are scheduled after other windows and can be deployed that time.
17058 [HyLabs] With Nutanix based HyLabs, reserved VM for course self-study is getting restarted even when administrator has kept option as keep power on after reservation end for course self-study.
17040 [HyLabs] While importing HyLabs user giving error on 1st line as unable to convert into use VDI. The isse has not impact but incorrectly processing first row (column header) of CSV.
16965 Controller switched to fault mode for sometime after getting 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." - Error condition is not yet known
16959 Unable to change license allocation if license count decrease from last activation
16954 Deadlock error log is observed, while updating desktops agent details in pool and in check team call.
16949 Windows Server 2008 R2 SP1 need explicit PowerShell upgrade to v3.1 for domain trust check to work properly.
16941 Virtual display mechanism is showing notification outside the RDS session, end-user may not understand for which session notification is shown
16939 [UI] Options e.g., Force shutdown, Force logout are continued to be displayed and creates confusion, even when Capacity plan mode is set as disabled in pool/ team page
16929 Capacity plan will continue to affect managed teams even when 1. Plan is inactive 2. Session team is removed from capacity plan 3. Schedule is expired 4. Capacity mode is changed from enforce to disabled [Manual control will not be impossible]
16905 When Japanese language selected while logging in the test-mail & notification mail text content is shown in English language.
16857 Gold Master lock is not removed, if the provisioning is stuck due to any reason. Administrator has to perform alternative actions such as stop provisioning etc. to unlock gold master.
16854 Mouse cursor turns to restricted, while hover on choose snapshot radio buttons, but user can still select any radio button option.
16840 Shell-app Reconnection logs in controller uses word connect instead of reconnect. The logs are little confusing here and need improvement.
16720 Non-user-friendly exceptions are shown when action processor fails to connect to RabbitMQ e.g. after installation of Action Processor
16706 Object reference not set to an instance of an object error is coming in HyWorks-Controller-Installation logs. It has not impact on installation but can be improved to reduce confusion.
16694 Passive/Cordon desktop providers are not considered first for scale-up in case of corner case (Ready session servers = 0, Min Running = 0 and Max Running > 0 )
16629 After canceling the controller installation the created folder in the system are not getting deleted automatically.
16433 App/SHD session status is not showing in 'Connected' state, after deleting the SHD database file and reconnecting the App/SHD session again
16388 Create appropriate logs with team and plan information. Current log implementation is using Ids, which are difficult to map with user-friendly names.
16341 'Fix soft errors' & 'Fix all errors' options (Fix desktop) are not helpful in case of failed disk encryption. The feature is should consider disk encryption as condition as well and should try to re-encrypt the VM.

Known Issues in Previous Releases

Please refer respective releases articles to get the list of open issues.