Omnissa Horizon Client for Windows Release Notes

Horizon Client for Windows 2206 | 19 JUL 2022

What's New

Horizon Client for Windows 2206 includes the following new features:

Support for background blur and effects when using Microsoft Teams Optimization
Background blur and effects enable you to blur your background or select a background image before or during a video call or meeting. For details and dependencies, see "Media Optimization in Microsoft Teams" in the Horizon Remote Desktop Features and GPOs guide.
Support for HID (Human Interface Device) compatible headset usage when using Microsoft Teams Optimization
For details and dependencies, see "Media Optimization in Microsoft Teams" in the Horizon Remote Desktop Features and GPOs guide.
Support for timeout warning and timer
You can configure the warning to be displayed and set the timer at which the warning is displayed before a user is forcibly disconnected from a remote desktop or published application. You can also configure the message that is displayed when the user is forcibly disconnected.
Display timeout message before forced disconnect
You can configure a message and timeout warning to be displayed before a user is forcibly disconnected from a remote desktop or published application.
Media Optimization for Microsoft Teams can be changed on the Horizon Client for Windows User Interface
You can now change Media Optimization setting for supported WebRTC based Unified Communications apps on the Calls and Sharing dialog box. For example, Microsoft Teams Optimization can be disabled. This setting is enabled by default and this is the recommended setting.
Encryption of on-screen keyboard input
On-screen keyboard encryption is enabled when you select Enable Keylogger Blocking during custom installation.
Support for a favorite remote desktop or published application on a Horizon Cloud Service Next-Gen server
You can select favorite remote desktops and published applications on a Horizon Cloud Service next-gen server.
Support for Windows Hello for Business With Certificate Authentication
Windows Hello for Business with certificate trust is now supported with the Log In as Current User feature.
Default microphone on client computer reflected on remote desktop
When using multiple devices, the default microphone is reflected on the remote desktop.
Support for enabling or disabling BlastCodec decoding on the Horizon Client for Windows User Interface
You can now enable or disable the use of BlastCodec decoding to receive remote screen content on the client interface.
RTAV log files saved in separate files
RTAV agent and client logs are written to separate files within the logs directory for easier analysis.
Selective Printer Redirection with Integrated Printing
You can now select the printers to be used in remote desktop sessions.

For information about new remote desktop features, see the Omnissa Horizon 8 2206 Release Notes.

Before You Begin

For the Windows operating systems that this release of Horizon Client for Windows supports, see the Horizon Client for Windows Guide.
Horizon Client for Windows is supported with Omnissa Horizon 8 version 2006 and later.
To install Horizon Client for Windows, download the installer from the Horizon Clients download page.
For installation instructions, see the Horizon Client for Windows Guide.
For information about the features that are supported in nested mode, see Omnissa Knowledge Base article 80509, "Horizon Guidelines for Nested Mode."
The Horizon Client for Windows installer requires .NET Framework version 4.5 or later.
Beginning with Horizon Client for Windows 2006, Virtual Printing (also known as ThinPrint) is not supported. Use Integrated Printing instead.

Resolved Issues

On a Windows 11 client machine, the title bar and borders of the remote desktop used to flicker after you share the desktop using Microsoft Teams. Microsoft has resolved this issue.

Known Issues

Enable Relative Mouse feature does not work on touch-enabled screen
If you use a touch-enabled screen on your client system to work in a remote desktop, do not use the Enable Relative Mouse feature. This feature provides improved mouse performance for 3D and CAD applications, but for touch-enabled screens and tablets, the mouse coordinates are not translated properly, even in 3D and CAD applications.

Workaround : None.
When a remote desktop is reconnected, Powermic Speechmic does not work with DMO 2022.2
When a remote desktop is reconnected after being disconnected, Powermic device does not work with dictation on DMO 2022.2. This happens when using a USB split and RTAV solution.

Workaround: Use Nuance extension to redirect Powermic devices on the remote desktop.
Horizon Client for Windows quits when launching a remote desktop
Horizon Client for Windows might quit unexpectedly when launching a remote desktop with multiple monitors at a high resolution.

Workaround : Check the supported multiple monitor configurations in the documentation to resolve this issue. If you still encounter this issue, consider the following workarounds:
- Configure your monitor layout so that it’s not very wide or very tall (for example, use a tile/matrix layout instead of using single row/column of monitors).
- Try not to launch multiple desktops with multiple monitors in one client instance, but start a new client instance to launch another remote desktop.
- Use the Omnissa Horizon Blast protocol to start the remote desktop.
Limited context menu with Browser Redirection feature
With the Browser Redirection feature, the context menu options on right click are limited to open link in new tab, open link in new window, back, and forward.

Workaround: None.
Incorrect event log report
With the clipboard audit feature, the event log reports one byte more than the actual length of the data that was copied from the agent machine to the client machine. For example, if you copy 10 bytes of data from a remote desktop to the client machine, the event log reports "XXX copy 11 bytes CPFORMAT_TEXT data from Horizon Agent to Horizon Client XXX with clipboard." Also, if "\r\n" is in the copied text, the event log records only the length of "\r." For example, if you copy the following text, the audit message records the length as 12 bytes:
```
aaa
bbb
ccc
```
Workaround : None.
Error when connecting to a remote desktop with the Microsoft RDP display protocol
A “Pending session expired” error might occur when you try to connect to a remote desktop with the Microsoft RDP display protocol. This problem only occurs in large-scale environments where a Unified Access Gateway appliance is used, and virtual printing is enabled.

Workaround : Establish a connection to the remote desktop without using a Unified Access Gateway appliance, or disable virtual printing and establish a connection using RDP.
RDP session ends on the physical machine
If you use the RDP protocol to connect to a published desktop from a physical machine, and then you try to connect to the same published desktop from a zero client, the RDP session ends on the physical machine and the zero client cannot connect.

Workaround : Relaunch the same desktop pool with RDP from the physical machine, select Options > Disconnect and logoff in the launched RDP session, and then reconnect to the same desktop pool from the zero client.
Client's "log in as current user" function is not available
If you install Horizon Agent and then install Horizon Client on the same Windows machine (a nested mode installation), and you later uninstall Horizon Agent, the client's "log in as current user" function is lost after Horizon Agent is uninstalled. This problem occurs because the wsnotify.dll file is removed after Horizon Agent is uninstalled.

Workaround : Reinstall Horizon Agent or Horizon Client to bring back the "log in as current user" function.
Windows Fax and Scan hangs
On Windows 10, Windows Fax and Scan hangs when using a CardScan 800 device.

Workaround: None.
Mouse pointer does not move downward
If you have multiple monitors with different screen resolutions and expand Horizon Client to all monitors and then select the Enable Relative Mouse feature, occasionally, the mouse pointer might not be able to move downward beyond a certain position.

Workaround: Press Ctrl+Alt.
Horizon Client may stop responding when Automatically Connect at Startup is selected
If you select Connect USB Device > Automatically Connect at Startup for a camera in nested mode, Horizon Client may stop responding when you reconnect the second hop agent but the USB audio devices are removed immediately in the client side.

Workaround: None.
Bandwidth Limit setting for serial port redirection fails to take effect
The serial port redirection group policy setting Bandwidth Limit does not set a limit on the bandwidth.

Workaround : Use third-party software to limit the bandwidth.
Performance of Horizon Blast slows down with serial port redirection at high baud rate
With serial port redirection at a high baud rate such as 115200, the performance of Horizon Blast slows down, and the connection might sometimes hang.

Workaround : Use a baud rate of 9600.
IPv6 IP mapping for LBP results in issues
In an IPv6 environment, if you configure IP address mapping for location-based printing, users might encounter a problem accessing the printer because the client can have multiple IPv6 addresses. Anytime the client connects, it can use any one of the addresses.

Workaround : Use the location-based printing group policy setting IP Range to include the multiple addresses. However, the printing problem might still occur because the client might use a temporary address, which is not in the specified range.
White border appears to the right side of the desktop window
On a Windows 11 client machine, a white border appears to the right side of the desktop window. When you launch a desktop in All Monitors mode and then quit the All Monitors mode and maximize the desktop, a white border is displayed to the right side of the desktop window.

Workaround: This is a Microsoft Windows 11 issue. Until Microsoft fixes this issue, launch the desktop directly in large mode.
Wacom500B cannot be unshared from agent
If you enable Automatically Connect when Inserted for Wacom500B, it is not unshared on the local client after the device is redirected. This is because the arbitrator deletes the device when unsharing it from agent to client but if the device is still plugged in on the client side, it is re-added.

Workaround: None.

Documentation

Horizon Client for Windows documentation is in the Omnissa Product Documentation.

Localized Content for Omnissa Docs

The transition from Broadcom to Omnissa is in progress. As part of that transition, we are reviewing our localization strategy for how best to serve the needs of our customers and partners. We will be providing localized version of Omnissa Docs content again soon. Thank you for your patience.

Support Contact Information

To receive support and to learn more about support policies, see Omnissa Customer Connect.

For information on filing a support request in Customer Connect and via Cloud Services Portal, see Omnissa Knowledge Base article 6000005.

Was this page helpful?