Horizon 8 version 2203 does not include updates for Horizon Connection Server. Please use the Horizon 2111 Connection Server version with Horizon 8 2203 Agents and Clients.
VMware Horizon 8 2203 | 05 APR 2022 Check for additions and updates to these release notes. |
Horizon 8 version 2203 does not include updates for Horizon Connection Server. Please use the Horizon 2111 Connection Server version with Horizon 8 2203 Agents and Clients.
VMware Horizon 8 version 2203 includes the following new features and enhancements. This information is grouped by installable component.
Version numbering is based on the planned year and the month of the release. The actual release date can vary based on business needs and engineering schedule changes to address critical customer requirements.
Virtual Desktops
Horizon Connection Server
There are no updates to Horizon Connection Server for this release.
Horizon Agent
Horizon GPO Bundle
Horizon Client
Release version 2203 installers are available for the following Horizon clients:
There is no release version 2203 for Horizon HTML Access.
For information about new features in Horizon clients, see the release notes on the VMware Horizon Client Documentation page.
Horizon Agent for Linux
/etc/vmware/config
configures the bandwidth bursting interval for data sent to clients. This option specifies the interval of time during which the network bandwidth can temporarily exceed the bandwidth cap set by RemoteDisplay.maxBandwidthKbps. See Setting Options in Configuration Files on a Linux Desktop./etc/vmware/config
lets you configure a search filter that prevents specific client printers from being redirected to the Linux desktop. This option supports search query syntax based on the name of the printer, the driver, or the driver vendor. See Setting Options in Configuration Files on a Linux Desktop.For the latest set of Horizon API, see Horizon API. For a list of Horizon RESTful API for each release, see VMware Knowledge Base article 84155.
Applicable to customers with VMware Horizon Universal Subscription, Horizon Enterprise Plus Subscription, Horizon Standard Plus Subscription, Horizon Apps Universal Subscription, or Horizon Apps Standard Subscription.
The Horizon Cloud Connector virtual appliance is a required component for VMware Horizon to support the management of Horizon pods using Horizon Cloud Service.
For a list of VMware Horizon features supported on VMware Cloud on AWS, see VMware Knowledge Base article 58539.
You can select Azure as an installation option to deploy Horizon on Azure VMware Solution (AVS). See Deploying VMware Horizon on Azure VMware Solution.
As Horizon Console is migrating to VMware clarity widgets which do not support Internet Explorer, we have removed Internet Explorer from the list of supported browsers for Horizon Console.
If you plan to install a version of VMware Tools downloaded from VMware Product Downloads, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. To determine which VMware Tools versions are supported, go to the VMware Product Interoperability Matrix. (Supported versions: 11.1.0, 11.0.6, 10.3.22, 10.3.21).There are also performance issues with the 11.x versions of VMware Tools. For more information, see VMware Knowledge Base article 78434.
Do not remove CA-signed certificates that were installed for production use, as recommended by VMware. CA-signed certificates will continue to work after you upgrade to this release.
frontServiceWhitelist = tunnel|ajp:broker|ajp:portal|ajp:misc|moved:*|file:docroot
Features that were introduced in prior releases are described in the release notes for each release, along with existing known issues.
The number provided before each resolved issue refers to the VMware internal issues tracking system.
The numbers provided before the resolved issues refer to the VMware internal issues tracking system.
Horizon Connection Server
Workaround: Open a new session in another tab or reload the login page.
This problem can occur for the following pool types:
Workaround: Use Horizon Client to restart or reset the virtual machine in the instant-clone desktop pool. If the virtual machine is already in the “Already Used” state, remove the virtual machine. This action automatically creates a new virtual machine based on the pool provisioning settings.
Workaround: Delete the instant-clone desktop pool. This will delete the related VMs and enable the corresponding hosts to enter maintenance mode.
It is mandatory to configure one enrollment server as primary. Configuring a secondary enrollment server is optional. If you have only one enrollment server, you will see only the first message (on error). If you have both a primary and a secondary enrollment server and both have connectivity issues, you will see both messages.
Workaround: Set up the Cloud Pod Architecture environment to view pod names in Horizon Help Desk Tool.
Workaround: Configure the Workspace ONE mode in Connection Server.
Workaround: Restart Connection Server.
Workaround: Log in to Horizon Console as a user who has the Administrator or Local Administrator role.
Workaround: Log in to the Horizon Console user interface for a Connection Server instance in the hosting pod and select Monitoring > Events to view pre-launched session information.
Workaround: None.
Workaround: Manually remove these parent VMs. For more information, see the Setting Up Virtual Desktops in Horizon document.
The following vGPU profiles have 512 Mbytes or less of frame buffer:
Workaround: Use a profile that supports more than one virtual display head and has at least one GB of frame buffer.
Workaround: None.
Workaround: Edit the role or create the role again with the "Manage Farms and Desktops and Application Pools" privilege, which also adds the “Manage Global Configuration and Policies” privilege.
Workaround: Add the bookmarks from the catalog in Workspace ONE again.
Workaround: Manually close the window of the remote desktop and disconnect from the remote session.
Workaround: This occurs because of a Microsoft Windows issue. To resolve this issue, follow the steps in this Microsoft help article: Sysprep fails after you remove or update Microsoft Store apps that include built-in Windows images.
Workaround: Use a DNS name instead of an IP address when connecting. For more information, see VMware Knowledge Base (KB) article 2150307.
Workaround: Safari version 10.1.1 is not a supported Web browser version for Horizon Console. Use a Safari version earlier than version 10.1.1 or version 11.0.2 and later to log in to Horizon Console.
Workaround: None. Horizon Help Desk does not support the following user interface features for Linux desktops: Skype for Business status, Remote Assistance, Applications tab, and the session idle status.
Workaround: None.
Workaround: Use the Fully Qualified Domain Name (FQDN) to login to Horizon Console. For more information on using FQDN to log in to Web applications, see the Horizon Security document.
Workaround: After an upgrade to vSphere 6.7, create a new custom specification and use this specification for pool provisioning.
Workaround: If Horizon Help Desk Tool does not display the logon time for the hosting pod, close the page that displays session details, wait 7-8 minutes and navigate to the Details tab to view the session details again.
Workaround: Save the profile again and perform a sync operation on the new profile. The sync operation can occur every hour or day, as set by the administrator.
Workaround: None.
Workaround: Use one of the following workarounds to resolve this issue.
Workaround: None. This problem is a third-party issue and is inline with the way Microsoft RDS license servers issue licenses.
Workaround: None.
Workaround: None.
Workaround: None.
Workaround: To resolve this issue, see “Origin Checking” in the Horizon Security document.
Workaround: None. Media Bypass is not supported with the Virtualization Pack for Skype for Business. See VMware Knowledge Base (KB) article 56977.
Workaround: You must delete the user from both pods and then recreate the user and configure the user for hybrid logon.
Workaround: None.
Workaround: None.
Failed to add vc instance: No enum constant com.vmware.vdi.commonutils.Thumbprint.Algorithm.SHA-1
This issue occurs because the certificateEncoding property that indicates a certificate override for self-signed certificates is added in Horizon 7 version 7.8. Therefore, earlier versions of VMware PowerCLI scripts that have an incorrect value of SHA-1 fail.
Workaround: Update the PowerShell scripts to use the property value DER_BASE64_PEM instead of SHA-1. For example, set $certificate_override.sslCertThumbprintAlgorithm = 'DER_BASE64_PEM'.
Workaround: Update the app path in Horizon Console after an upgrade and verify the app status is Available. Alternatively, do not upgrade the app.
Workaround: When device filtering is configured for client drive redirection, configure Connection Server so that RDP connections are not allowed.
Workaround: None.
Workaround: None.
Workaround: None.
Workaround: None.
"Error opening installation log file. Verify that the specified location exists and is writable."
This error occurs due to a third-party Microsoft error. For details see this Microsoft help article.
Workaround: Restart the virtual machine on which the Connection Server is installed.
Workaround: If you use this combination of features and Horizon version, disable this pre-login message on Connection Server. A pre-login message should instead be configured on the SAML IdP, so that it is presented to the user before the user enters their credentials.
Horizon Agent for Linux
This section describes issues that might occur with Horizon Agent for Linux or when you configure a Linux desktop.
Workaround: Resize the desktop window or reconnect to the remote desktop.
Workaround: Set the Keyboard Input Method System to iBus.
Workaround: After you add a domain using SSSD, modify the /etc/pam.d/password-auth file using the information in VMware Knowledge Base article 2150330.
Workaround: At the prompt, enter the smart card PIN and click OK. Or click Cancel to dismiss the prompt without entering a PIN.
Workaround: The user can log in to the desktop by entering the user password or reinserting the smart card.
Workaround: Configure pkcs11_eventmgr to specify the correct screensaver behavior in response to smart card events.
Workaround: Install Horizon Agent with smart card redirection enabled on a desktop running RHEL 7.1 or later.
Workaround: Make sure that the primary monitor's resolution is at least as large as the secondary monitor's.
Workaround: To access the desktop, unlock the screen after logging in with the smart card.
Workaround: Modify the policy in Ubuntu to download and install OS updates manually, instead of automatically.
Workaround: To reduce occurrences of this issue, edit the /etc/sssd/sssd.conf file by increasing the p11_child_timeout value under the [pam] section. Then reboot the desktop.
Workaround: To change to full-screen mode, select the Maximize command again.
Workaround: From the Connection Server, manually assign the icon for the LibreOffice application.
Workaround: Shift + right-click the application icon in the client's task bar and select Maximize to enlarge and refresh the window display.
Workaround: To update the AccountsService library to the required version, update the desktop operating system to SLED/SLES 15 SP2.
Workaround: Use a clipboard manager to retrieve the missing content from the clipboard.
Workaround: Use a different office application or browser to print the document.
Workaround: None
Workaround: None
Workaround: Turn off the page scaling option by setting it to 100% or None, on both the remote desktop and the client system.
Workaround: None
Horizon Agent
Workaround: Click “Ignore” in the dialog box that appears when you use Windows Add or Remove Programs to uninstall Horizon Agent. If you uninstall Horizon Agent from the command line, use the command msiexec /x /qn {GUID of Agent} instead of the command msiexec /x {GUID of Agent}.
Workaround: Repair VMware Tools on the Horizon Agent virtual machine.
Workaround: Move the mouse back on to the screen. Alternatively, don't use relative mouse mode in a multi-monitor session.
Workaround: Change the home page or the filtering rules.
Workaround: Add the collaborator by using domain\user.
Workaround: You can ignore this message as the device is usable in the remote desktop. Alternatively, you can turn off the Windows Settings notifications to prevent the message from being displayed.
Workaround: Edit the COM Port Isolation Mode group policy setting, change the mode to Isolation Disabled, and restart Horizon Agent. For more information, see "Serial Port Redirection Group Policy Settings" in the Configuring Remote Desktop Features in Horizon document.
SYSPRP Sysprep_Clean_Validate_Opk: Audit mode can't be turned on if there is an active scenario.; hr = 0x800F0975
Workaround: Apply these instructions on the golden image and then provision the desktop.
Workaround: Apply the procedure in this KB article on the OS image. If Horizon Agent is installed on an RDS host, and the Printer Name for RDSH Agents group policy setting for the VMware Integrated Printing feature is configured to use the client machine name as a suffix, the client machine name supports only English-language characters. If the client machine name contains characters in a non-English language, the VMware Integrated Printing feature does not work in published desktops and published applications.
Workaround: None.
Workaround: None
Workaround: In Horizon Console Desktop Pool settings, set the guest customization to None, then reboot the existing unreachable agent VMs.
Workaround: Use Blast protocol if available, or continue using Windows 10 build 1909.
Workaround: None.
Workaround: Download the installer to a non-download directory, such as the desktop, and run it from there for a successful installation.
Workaround: None.
Workaround: Revert to Workspace One version 19.03.0 and perform the sync operation again.
Workaround: None.
Workaround: None. This problem is a third-party issue.
Workaround: None.
Horizon Client
This section describes problems that end users might encounter when using Horizon Client or HTML Access to connect to remote desktops and applications. For problems that occur only in a specific Horizon Client platform, see the Horizon Client release notes on the Horizon Clients Documentation page.
Workaround: None.
Workaround: Unlock the desktop manually.
Workaround: Perform a scan on the client. The client scan calibrates the scanner. After the calibrate operation is finished, save the calibration file and deploy it in ProgramData\AmbirTechnology\ImageScanPro490i
Workaround: None.
Workaround: Set the English IME on the client device and set the non-English IME on the remote desktop.
Workaround: None.
Workaround: None.
Horizon Cloud Connector
Workaround: Use the vSphere Web Client to deploy the Horizon Cloud Connector virtual appliance OVA file.
This message is displayed incorrectly and does not indicate an actual problem with the network. You can disregard the message and continue to use Horizon Cloud Connector as usual.