Known Limitations and Issues in SHD and App Delivery
- Last Updated Date: 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.
Windows-Based Shared Hosted Desktops and Virtual App Delivery Known Issues
| Bug ID | Description |
|---|---|
| 40541 | MS Edge published as the virtual app does not work in the system context, and the session gets logged out. |
| 39226 | Shell mode apps are not getting launched to the user, on controller app session is shown as connected, and controller is sending response code 0 to client to launch the new RDP window. |
| 35580 | When connecting to the shadow session with local admin creds, session shadow is failing. The already present session of the local admin connected rather the user's session. This issue is with Windows server 2019 and may be because of issue# 34179. |
| 35217 | Some of the system processes or apps may still use the system IP even when virtual IPs are assigned for the user session. |
| 34179 | 2023-08 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5029247) - Causing Multi-session and Reconnection Issues. Recommendations: 1. New shell launch method can be tried if facing issues with multiple shell apps with Windows 2019, 2022 servers. 2. Desktop publishing with HyShell can be used with restrictions to file system and desktop. New advanced shell is being released soon to take care of some of the aspects. |
| 31822 | Exclude process (to use system IP instead of virtual IP) is not working with SHD pool. |
| 29789 | Controller does not remove virtual IP configured on disabling the feature from Advance settings. This to be done manually |
| 26461 | Session host IP virtualization feature does not work in cloud deployments (Azure/AWS/Oracle). |
| 25474 | Shadow sessions are considered as direct RDP sessions and may get removed by the agent. Workaround: Disable direct RDP block feature temporarily. |
| 25118 | Session host installation may not show any errors if the user running the setup does not have appropriate rights to add or update registries. This may result into functional failure at a later stage during the setup. Recommendation: Session host installation logs should be verified post installation. |
| 24995 | Some exceptions are logged in session host logs, when a session host with multiple running sessions (with VIP enabled) is restarted. Exception: The underlying provider may fail on Open. |
| 24888 | An error is logged in session host logs only after a shared hosted desktop pool is provisioned. Error: region LastServiceForcedExit failed. Error: The media is write protected. |
| 23964 | Successful VIP removal log is not getting logged on controller, when session is logged out from within the session (SHD). |
| 23408 | Users fail to read the notification as Tray agent is getting opened in background in case of remote app session recording. |
| 23297 | Controller does not support upgrade of session host servers that have sessions running. Due to which such servers have to be manually accessed and upgraded. |
| 22590 | Windows server 2022 by default does not support multiple sessions of a single user. This can adversely affect virtual app delivery in shell mode. Solution: Configure following group policy on server 2022: - Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. - Set Restrict Remote Desktop Services user to a single Remote Desktop Services session to Disabled. |
| 22519 | Recording does not stop for the applications that are configured for it even after closing the application or even the application is not in use. Same behaviour is observed for the configured network address. |
| 22170 | On removing the remote app sessions from controller, provider session is going into disconnected state. Workaround: Configure the group policy to logout the remote app sessions immediately: gpedit.msc > Computer configuration > Administrative template > Windows components > Remote desktop services > Remote desktop session host > Session Time limits > Set time limit for logoff of Remote app session. |
| 21254 | Logs are not created on HyWorks controller when local users are not created by session host server. |
| 20938 | Session recording may not start if recording is configured to be started on specific process launch and the process is initiated within 10 seconds of session start. |
| 20725 11145 |
Mozilla firefox and Microsoft Internet Explorer does not work correctly when initiated in a different user's context i.e. opened as a different user. This should be avoided. |
| 19910 | In a very rare case, monitoring service database is having some garbage values and because of that the service is not responding. The database should be replaced with empty database and monitoring service should be restarted to solve the issue. |
| 18860 | Session recording not working when SMB2 based network is accessed. |
| 16949 | PowerShell upgrade to v3.1 is must for Windows 2008R2-SP1 for trust relationship repair. |
| 16941 | Messages shown to user via virtual channels are outside of remote session and thus user may find it difficult to associate it with sessions, especially when running multiple virtual apps in shell mode. |
| 16929 | Capacity plan will continue to affect managed session team even when: 1. Plan is inactive 2. Session team in removed from capacity plan. 3. Schedule has expired. 4. Capacity plan is changed from enforce to disabled. |
| - | Chrome browser does not get launched in multiple remote sessions of a single user on Windows session host server. Workaround: As many deployment need to access chrome as virtual app in shell mode, which will require multiple sessions of a single users from single session host server, specifying following command line will enable accessing chrome in shell mode multiple times: Additional Command-line: --user-data-dir=%localappdata%\Google\Chrome\%sessionname% |
| 14208 | After upgrade or fresh installation of session host server, on first logon to server, couple of powershell windows will be shown for sometime. |
| 13922 | RDS role is bot available on Windows 2019 essentials and thus can not be used for virtual application or shared hosted desktop delivery. |
Known Limitation for New Shell Mode with Multiple Virtual Apps
While working on the new shell mode with multiple virtual, following points should be considered carefully:
| # | Subject |
|---|---|
| - | The delivery mode can only work with compatible client, controller and session host versions. The support in other endpoints (e.g., HyLite, MAC Client, Linux Client, Android client) will be integrated soon. Check compatible versions of different modules here. |
| - | If any incompatible client will try to access the apps in new shell mode, applications will get launched inside of already running remote session but error will be shown: - Error: You are likely encountering this error due to an older version of the client. The application will automatically launch within an existing session. Please check with the administrator to obtain a compatible client version. |
| #40534 | On reconnecting an existing virtual app session in shell mode, the application is getting minimized inside the remote session. The behavior is seen on Windows server 2022 only. |
| #40390 | Pin, unpin and close options like Windows task bar are not available on right clicking on the app button. |
| #40387 | Tool tip flickers, when mouse is hovered on the minimized app icon on the taskbar. |
| #40386 | With multiple (>8) virtual apps in single shell session, user experiences difficulty in accessing applications in the taskbar as arrow button to show more apps is having clear visibility and does not work in first click. |
| #40371 | App windows is not visible on hovering on app icons on taskbar (Like Windows taskbar). |
| #40367 | App group buttons are not aligned with the taskbar. |
| #40023 | Assigned VIP in session with multiple apps will only get detached on the session logout and will not get detached on app closure (VIP was assigned to the app). |
| #39666 | With multi-monitor setups, remote session window is launched in full screen but actual app and taskbar is not aligned with the full screen and floating in the middle of the screen. |
| #33399 | In case of application session, AUEM tray is not provided in this release for user to check the connected devices/Taskmanager/Notification history/Hide notification/Battery manager etc. |
Power Management Known Issues
| # | Subject |
|---|---|
| - | Session host server power management is applied only to the deployed managed session host server teams and will not work for existing manually created teams. Azure configuration is required to be done manually with privileged user account. |
| 24889 | While scaling down, maximum provisioned capacity is considered instead of minimum running capacity and thus can end-up in running more servers than planned. |
| 24868 | Error observed on HyWorks controller logs, when it tries to use cordoned servers for capacity plan scale up. Error: Team ID or desktop provider IDs can not be null. |
| 22037 | Capacity planning is checking the plan objective closest to 12.00 am/0.00 in the current plan only, even if multiple plans are applied to the single session team and thus it may fail to implement objectives from other plans. |
| 21875 | Action processor service crashes when AccopsMQ is not reachable. |
| 21735 | On-demand scaling using capacity planning is not supported for virtual application sessions and works only for shared hosted desktop sessions. |
| 21652 | In some rare cases, action processor has cordoned more servers than expected. Running sessions will not be affected but new users may have to wait for servers to be un-cordoned. |
| 19776 | The schedule background worker CPU usage can go high while saving a session team. |
| 17689 | If a managed (deployed) session team already exists and controller has been upgraded to v3.4, to generate schedule Ids the session team must be updated at least once. |
| 16904 | Some known limitations of automatic power management in HyWorks: 1. Backend call for plan implementation will occur at minimum 10 minute interval at 00, 10, 20, 30, 40, 50. 2. Action processor is having two calls i.e. 1.Plan implementation 2.Dynamic scale, hence scale may happen in next cycle if call to scale occurs first 3. Virtual channel based notifications to end-users will work with Windows end-points only and will require virtual channels to be enabled in session using connection profiles. 4. Notification settings need to configure through appsettings.json file and service restart is also required. 5. Admin is not having control on dynamically managed teams, which essentially means even if some servers are powered-on or off may get reverted to original state as per capacity plans. 6. Actual shutdown of cordoned server may not happen on notified time and will happen on next dynamic scale trigger. 7. CPU/ RAM thresholds (if applied) can conflict with capacity plan as it only considers max sessions allowed per server. 8. Overlapping of two objectives will result in implementation of current objective and thus the previous plan objective in-progress may get affected. |
| 13794 | [Power management] Log should log on controller when power off/on operation is not required, currently no logs are logged on the controller. |
| 13793 | [power management] When SHD cloning failed, power management for session team should work according to successful cloned VMs count. It continues to use the desktop count as specified in desktop pool. Workaround: Update the desktop pool with new count or clone again to match the count. |
| 13792 | [power management] Logic App logs use session team ID and provider ID and thus admin needs to identify affected team using IDs. |
| 13789 | [power management] For every managed session team we need Azure access for creating Logic app. |
| 13777 | [Power management] When team size is getting reduced, power management should work accordingly. |