check-circle-line exclamation-circle-line close-line

This list outlines the version numbers of artifacts that are provided new in the world or have been updated as of the July 9, 2020 calendar date.

  • VMware Horizon® Cloud Service™ | The quarterly service release 9 July 2020
    • Note: All new cloud-plane-based features that do not rely on pod manifest version level or Cloud Connector version level or Horizon pod version level or control-plane regional differences are automatically provided to both existing customers and new customers. As an example, a new feature that does not depend on new APIs for API calls between the cloud plane to the pods or related to Cloud Connector will be visible and exploitable by customers from the 3.0 Release Notes level, unless otherwise noted below or noted in the product guides. To illustrate this point, one such feature is the Administration Console's enhanced feedback submission. The new feedback icon and flow is available for use by existing customers even prior to upgrading the pods or Cloud Connector to their latest versions.
  • VMware Horizon® Cloud Service™ on Microsoft Azure | Version 3.1
    • Starting from the July 9, 2020 date, the pod deployer will deploy new pods using the new manifest 2298.0 by default. (If subsequent patches are needed for stability or performance enhancements, the number following the decimal point will be incremented: 2298.1, 2298.2, and so forth.)
    • Note: Pods that exist deployed in your service tenant prior to this version 3.1 release will continue running at their existing manifest version until they are updated to the manifest that is brand new for this release.
      • Service features that are new as of July 9, 2020 which have zero dependencies on APIs that require the version 3.1 level will be available for those existing pods. As an example, one such feature is the new ability to add a gateway configuration that uses the Standard_F8s_v2 (8 vCPUs) VM size.
      • Service features that are new as of July 9, 2020 which rely on APIs at the version 3.1 level will not be available for those existing pods until those pods are updated.
      • Some service features that are new as of July 9, 2020 might depend on the cloud plane region in which your tenant account is located. Such features are noted in the following sections of this document.
  • VMware Horizon Cloud Connector | Version 1.7
  • VMware Horizon Universal Broker plugin installer | Version 20.3
  • VMware Horizon Agents Installer (HAI) | Version 20.2
    • This HAI version is supported for use with pods of manifests that match the manifest level
    • Note: The console's Import VM from Marketplace wizard uses the HAI that is built into the pod manifest. As a result, pods deployed at the manifest that is brand new starting with this July 2020 quarterly release will have HAI 20.2 built into them, and running the Import VM wizard and selecting a pod at this level will install the agents from that HAI 20.2 version. For pods that are not yet updated to this quarter's manifest level, the Import VM from Marketplace wizard uses the HAI version that was available when their respective pod manifests were built.

Tip: This document is revised periodically after the quarterly release date when the Horizon Cloud Service itself is refreshed between its quarterly releases, so that you have current information about the service. Check back regularly for additions and updates to these release notes and look for green New text or red Update text.

This document applies to the quarterly service release that was pushed into production on July 9, 2020 and the subsequent weekly maintenance refreshes until the next quarterly service release. As of this date, pods newly deployed into Microsoft Azure are deployed using manifest version 2298.0. Access to some of the What's New features newly available in the service with this quarterly release might depend on factors such as which Horizon Cloud control-plane region your customer account is located in, the pod manifest versions supported in that region, the manifest version of your current cloud-connected pods, and so on. For the release notes of previous quarterly releases, use the links listed in the left-hand navigation pane at https://docs.vmware.com/en/VMware-Horizon-Cloud-Service/index.html. Your control-plane region is stated in the Welcome to Horizon Service email sent when the customer account is created, as described in Onboarding to Horizon Cloud for Microsoft Azure, Horizon On-Premises, and Horizon on VMware Cloud on AWS.

Update: These items are provided new as of August 11, 2020, aligned with the August 11, 2020 releases of Horizon and the Horizon Clients and Horizon HTML Access. You can read about the latest clients as described in their various documentation pages, linked from the Horizon Client Documentation page and about the latest Horizon from its Horizon Documentation page:

  • New Support is now available for using the 2006 version of the Horizon Clients and Horizon HTML Access with the desktops and remote applications brokered by pods in Microsoft Azure at manifest 2298.0 and later. The VMware Product Interoperability Matrices reflect this information.
  • New Support is now available for using the latest behavior of the Horizon remote experience feature for Media Optimization for Microsoft Teams. As described in this linked Horizon 2006 documentation topic Configuring Media Optimization for Microsoft Teams, this feature provides for Teams media processing to take place on the client machine instead of in the virtual desktop. See that linked Horizon documentation topic for more information. For pods in Microsoft Azure, use of this feature requires pod manifest 2298.0 or later and Horizon Agents Installer version of 20.2 or later, along with using the latest 2006 version of the Horizon Clients. As described in the previous section, running the Import VM wizard and selecting a pod at the manifest 2298.0 or later level will install the agents from that HAI 20.2 version.
  • New Support is now available for using the Horizon Cloud Connector 1.7 with a Horizon pod running the 2006 version of the Horizon software. With this support, you can cloud-connect a pod running the Horizon 2006 version using Horizon Cloud Connector 1.7.

Update: These items are provided in the service as of August 11, 2020:

  • New There is a new Export function for Sessions, VDI Applications Usage, and User Usage reports that allows you to export all of your report data. Previously exports were limited to 2,000 records. For details, see the Reports Page topic in the Administration manual. 

Update: These items are provided new in the service after the July 9, 2020 quarterly release date:

What's in the Release Notes

The release notes cover the following topics:

About VMware Horizon Cloud Service

VMware Horizon Cloud Service transforms traditional desktop and application virtualization by providing a cloud-scale architecture that frees you to choose where your virtual desktops and applications reside — in-cloud or on-premises — and manage them all from a single control plane. Pods can reside on-premises, as in a traditional Horizon pod installation, and pods can reside in clouds such as Microsoft Azure and VMware Cloud on AWS, which gives you the freedom to deploy workloads based on cost, location, geography, and current usage. The Horizon Cloud control plane gives you a single UI to manage all those cloud-connected pods and which gives you visibility into the pods' capacity usage, health monitoring, help desk services, and ability to set up end-user workspace assignments which associate your end users with their entitled virtual desktops and applications. Your overall tenant environment in Horizon Cloud consists of the VMware-hosted cloud service itself and the cloud-connected pods wherever those pods reside — and you manage it all using a single pane of glass, the cloud-based administration console.

What's New in This Release

The July 2020 quarterly release is the debut of the following headline features. If you are a current customer that has existing cloud-connected pods prior to this release, additional detail is provided in For Current Customers with Existing Cloud-Connected Pods - About this Release.

Key documents updated for this quarterly service release include:

  • VMware Horizon Cloud Service on Microsoft Azure Requirements Checklist (HTML).
  • VMware Horizon with Horizon Cloud Requirements Checklist (HTML).
  • Deployment Guide (HTML | PDF)
  • Administration Guide (HTML | PDF)
  • Managing Images from the Cloud (HTML | PDF)

What's New for Horizon Cloud Service

  • The Horizon Cloud Administration Console now supports both single sign-on (SSO) and multi-factor authentication, providing enhanced security for administrators accessing the console. Authentication is enabled using VMware Cloud Services federated identity management. The federated identity management feature is in Limited Availability. For more information, please email the VMware Horizon Cloud Service team at horizoncloudservice@vmware.com.

What's New for Horizon Cloud on Microsoft Azure

  • Universal Broker is now available for greenfield deployments of Horizon Cloud on Microsoft Azure pods. Universal Broker enables unified brokering of multi-cloud assignments across hybrid and multi-cloud Horizon environments with support for both Horizon 7 and Horizon Cloud on Microsoft Azure. To learn more, visit vmware.com/go/Horizon-UB.
  • Horizon Cloud administrators can now create multi-cloud assignments with greenfield deployments of Horizon Cloud on Microsoft Azure pods using Universal Broker. Multi-cloud assignments provide administrators with the ability to create both dedicated and floating desktops that span across multiple pods and sites. 
  • App Volumes with Simplified Application Management is now available for Horizon Cloud on Microsoft Azure pods. App Volumes provides the ability to decouple application package management from assignment management, along with full lifecycle management of an application to meet the dynamic needs of end users.
  • Use of App Volumes with Microsoft Windows 10 Enterprise multi-session in your Horizon Cloud on Microsoft Azure pods — both for Microsoft's MSIX app attach and for App Volumes VHDs — is now Tech Preview. For more details about this tech preview, see App Volumes Applications - Overview and Prerequisites in the Administration Guide.
  • Horizon Cloud on Microsoft Azure pods now support multiple tenant subnets from either the pod’s VNet or from multiple, connected, peered VNets for both desktop assignments and farms. 
  • RDSH farms now support advanced session load balancing, which provides the ability to load balance sessions using dynamic performance metrics from the session hosts in the Horizon Cloud on Microsoft Azure pods.
  • Additional Microsoft Azure VM sizes are now available for use with internal and external Unified Access Gateways for Horizon Cloud on Microsoft Azure pods. 
  • Administrators can now cancel both desktop and farm expansion tasks that are in a queued or running state, with support for automatic desktop assignment and farm resizing for Horizon Cloud on Microsoft Azure pods.

What's New for Cloud-Connected Horizon Pods

  • Horizon Cloud Connector 1.7 is released and available for download from the Horizon Cloud Connector area within the Horizon Cloud Service downloads page at my.vmware.com.
  • You can now schedule your Horizon Cloud Connector automatic updates using the Horizon Cloud Administration Console.
  • Collecting support log bundles is now much easier through the Horizon Cloud Administration Console and the Cloud Connector setup interface.
  • License sync warnings are much more accessible displayed as color-coded banners at the top of the Horizon Cloud Administration Console dashboard. The banner will change color and description based on severity.
  • More descriptive connectivity error messages in the Horizon Cloud Administration Console event logs. These messages enable administrators to self-diagnose and provide a link to a corresponding KB article that offers remediation recommendations.

For Current Customers with Existing Cloud-Connected Pods - About this Release

In addition to the items listed in the preceding What's New in This Release section, this section is for those of you who already had existing cloud-connected pods as of July 9, 2020 onboarded in your environment, and you have previous experience with Horizon Cloud features and workflows. This section describes what this release's new features and changes might mean to you and those pods. The new features related to enhancements of the cloud-based administration console are collected at the bottom of the list. For more detailed information, see the Deployment Guide and Administration Guide.

  • Specifically about existing cloud-connected Horizon pods:
    • Horizon pods are onboarded to Horizon Cloud for two primary use cases: to activate use of a subscription license with those pods and to enable use of cloud-hosted services that Horizon Cloud provides for Horizon pods. Each pod is onboarded using the Horizon Cloud Connector. The origin of onboarding Horizon pods to Horizon Cloud started with Horizon 7 version 7.6 environments and Horizon Cloud Connector 1.0 for activating subscription licenses on Horizon pods. Then with each new version of Horizon combined with a new version of Horizon Cloud Connector, additional cloud-hosted services become available for cloud-connected Horizon pods running the latest Horizon version paired with the latest Horizon Cloud Connector version. This release's Horizon Cloud Connector version 1.7 brings the new items described in the preceding What's New in This Release section. We recommend customers having earlier versions of Cloud Connector to upgrade to this latest version to take advantage of new features as well as security and resiliency fixes. Also, see VMware Knowledge Base Article 77564 for the matrix of currently supported versions of Horizon pod software with Horizon Cloud Connector. If you are running a combination of Horizon Connection Server and Horizon Cloud Connector version that no longer matches that matrix, please update as soon as possible to a supported combination.
  • Specifically about existing pods in Microsoft Azure:
    • For the following new features described in the preceding What's New in This Release section, an existing pod must first be upgraded to this July's quarterly manifest version to take advantage of the feature:
      • Multiple tenant subnets for use with farms and VDI desktop assignments. (Note: This feature is not yet available for use with multi-cloud desktop assignments, which are used in a tenant configured with Universal Broker.)
      • Use of the advanced session load balancing for RDSH farms
      • Ability to cancel both desktop and farm expansion tasks that are in a queued or running state, with support for automatic desktop assignment and farm resizing. (Note: This feature is not yet available for use with multi-cloud desktop assignments, which are used in a tenant configured with Universal Broker.)
      • To provide for improved end-user login times, the time it takes for a VM to get to agent-ready state for pod-provisioned desktop VMs that are powered off and need to power on to fulfill an end user's request for a desktop has been reduced.
      • Use of the App Volumes features — the pods must be updated to this release's manifest version and your customer account must be located in one of the following Horizon Cloud control-plane regions: USA-2 (PROD1_NORTHCENTRALUS2_CP1), Europe-2 (PROD1_NORTHEUROPE_CP1), or Australia-2 (PROD1_AUSTRALIAEAST_CP1). Your control-plane region is stated in your Welcome to Horizon Cloud Service email.
    • When deploying a gateway configuration on your pod, in addition to the Standard_A4_v2 VM size in previous releases, you now have the option to use the Standard_F8s_v2  VM size, which provides more vCPUs for each Unified Access Gateway instance. For existing pods, this new feature is available when editing the pod to add a new gateway configuration to that pod.
  • Administration Console enhancements:
    • An enhancement to submitting product feedback is now available in the console's header bar, for all existing customers.

Environments, Operating Systems, and Compatibility

  • Compatibility with other VMware Products: For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.
  • Browser Experience: The cloud-based administrative console is compatible with recent versions of Google Chrome, Mozilla Firefox, and Microsoft Edge. Use of the console in Microsoft Internet Explorer 11 is deprecated and will give a sub-optimal experience. The console is not supported for use in Apple Safari, although you can try using the console in Apple Safari. If you attempt to access the console using a non-modern browser such as Microsoft Internet Explorer 11, the console displays an information message to use an up-to-date browser. For the best user experience, use the most recent versions of Google Chrome, Mozilla Firefox, and Microsoft Edge
  • Microsoft Azure Cloud Support: For Microsoft Azure deployments, the service is currently available in the following Microsoft Azure cloud environments:
    • Microsoft Azure (Commercial)
    • Microsoft Azure in China
    • Microsoft Azure Germany (Public)
    • Microsoft Azure Government (US Gov Virginia, US Gov Arizona, US Gov Texas)

    Note: Currently, the High Availability (HA) capable architecture for pods in Microsoft Azure is only supported for pods deployed in the Microsoft Azure standard global regions. Support has not been qualified for pods in Microsoft Azure in China, Microsoft Azure Germany, and Microsoft Azure Government. The VMware team is working on adding support for the pod architecture to work in those cloud environments. If you have an existing pod in Microsoft Azure in China, Microsoft Azure Germany, or Microsoft Azure Government that you want to upgrade to this release's manifest version without the HA-capable architecture, please contact your VMware representative for assistance.

  • Supported Microsoft Windows Operating Systems: In the service's Microsoft Azure deployments, the following Microsoft Windows operating system editions and versions in the Azure Marketplace are the ones supported for use in this release, regardless of whether you use the automated or manual method of deploying an image in this release.
  • Supported Horizon Client versions for Microsoft Azure deployments: To see the specific versions of Horizon Clients that are compatible with the desktops and remote applications brokered by your pods in Microsoft Azure, see the VMware Product Interoperability Matrices and select Horizon Cloud Service on Microsoft Azure and VMware Horizon Clients in the drop-down menus. You can obtain the Release Notes for the Horizon Client versions from the VMware Horizon Client Documentation page at docs.vmware.com/en/VMware-Horizon-Client/

    Note: The VMware Horizon HTML Access client does not support certain features when used in mobile browsers. Also, even though the Horizon Client supports copying and pasting text between a client's local system and a VM out of the box, for HTML Access, you must configure this feature before your end users can use it. For more information, see the VMware Horizon HTML Access documentation page and search for the information in the most recent User Guide and Installation and Setup Guide.

  • Microsoft Windows 7 Operating System: As described in this release's What's New in this Release section, this release provides Tech Preview support for Windows 7 virtual desktops with Extended Security Updates. If your Welcome to Horizon Service email indicates that your Horizon Cloud tenant account was created in one of the following regions, you have access to this Tech Preview operating system using your Horizon Cloud Service tenant: US-2, Europe-2, Australia-2 (previous names appeared as PROD1_NORTHCENTRALUS2_CP1, PROD1_NORTHEUROPE_CP1, PROD1_AUSTRALIAEAST_CP1). With virtual desktops based on this operating system, you can use the Horizon Windows client, RDP 8.x protocol, and the Horizon remote experience features USB redirection and Help Desk. Use of GPU with NV-series VMs is not supported.

  • Supported NSX Cloud versions with Microsoft Azure deployments:  For pods at this release's manifest version (new pods or upgraded pods), using NSX-T Data Center 2.5 or later is recommended. For pods at the prior release's manifest version, the NSX-T Data Center patch release (patch release 2.3.0.1.0, build 10539383) will continue to work. Note: When using NSX-T Data Center 2.4 or 2.5, additional configuration steps are needed on the forwarding policies for the NSX-managed VMs. For details, see the Administration Guide.
  • Versions for cloud-connected Horizon pods: See VMware Knowledge Base Article 77564 for the matrix of supported versions of Horizon pod software with Horizon Cloud Connector. To get the benefits of advanced features that are only available for cloud-connected Horizon pods, you must have more recent versions of the Horizon Cloud Connector and Horizon pod software. You can download the latest Horizon Cloud Connector appliance and VMware Universal Broker plugin installer by navigating to the Horizon Cloud Connector section located within the VMware Horizon Cloud Service download page.
    Important: You must use the version 1.6 or later of Horizon Cloud Connector if your Horizon Cloud customer account was created in one of the following regions: US-2, Europe-2, Australia-2 (previous names appeared as PROD1_NORTHCENTRALUS2_CP1, PROD1_NORTHEUROPE_CP1, PROD1_AUSTRALIAEAST_CP1). Only version 1.6 and later versions is compatible with those regions. Your Welcome to Horizon Service email states in which region your account was created.
    Important: When you plan to upgrade both Horizon Cloud Connector and Connection Server for a cloud-connected Horizon pod, make sure to monitor and verify the health of the pod during the upgrade process. Monitoring the Horizon pod's health can help with troubleshooting any issues that might arise. Upgrading the Connection Server on a cloud-connected Horizon pod can sometimes result in problems with the health of that Horizon pod. If you then subsequently try to upgrade the Horizon Cloud Connector paired with that unhealthy Horizon pod, the upgrade of Horizon Cloud Connector might fail. Follow this best practice:
    1. After upgrading the cloud-connected Horizon pod's Connection Server, verify that the pod is in good health.
    2. To view the pod's health status, first log in to the Horizon Cloud administrative console and perform an Active Directory domain bind. That step allows you to access the console's Capacity page where you can verify that the pod shows a health status of Online or Ready.
    3. If the pod shows an unhealthy status, contact VMware Support to get help with resolving any connectivity issues involving the pod before you attempt the Horizon Cloud Connector upgrade.

Things to Know Before Using this Release

Review this information as you prepare to consume this release of VMware Horizon Cloud Service.

Knowledge of the following facts is useful before using Horizon Cloud Service with any of the deployment types.

  • Login authentication into the cloud- and Web-based administration console relies on My VMware account credentials. If the My VMware account system is experiencing a system outage and cannot take authentication requests, you will not be able to log in to the console during that time period. If you encounter issues logging in to the console's first login screen, check the Horizon Cloud System Status page at https://status.horizon.vmware.com to see the latest system status. On that page, you can also subscribe to receive updates.
  • When deploying a pod using the console's pod deployer wizard or connecting a Horizon pod using the Cloud Connector, specific DNS names must be reachable and specific ports and protocols must be allowed. See VMware Horizon Cloud Service Deployment Guide for the connectivity requirements.
  • Each of the pods paired with the Horizon Cloud control plane and associated with the same customer account must have line of sight to the Active Directory domains connected to those pods and have one-way or two-way trust configured along with that line of sight. For example, when you have three pods where one pod is in Microsoft Azure, one pod is on-premises, and one pod in VMware Cloud on AWS, each of those pods must have line of sight and one-way or two-way trust configured to the same set of Active Directory domains.

Knowledge of the following facts is useful before using Microsoft Azure deployments.

  • Subscriptions and Number of Pods: Be mindful about the number of pods you deploy into a single Microsoft Azure subscription, especially if you plan to have each pod running at a large scale. Even though multiple pods can be deployed into a single Microsoft Azure subscription, whether all into one region or spread across multiple regions, Microsoft Azure imposes certain limits within a single subscription. Because of those Microsoft Azure limits, deployment of many pods into a single subscription increases the likelihood of hitting those limits. Numerous variables, and combinations of those variables, are involved in reaching those limits, such as the number of pods, the number of farms and assignments within each pod, the number of servers within each pod, the number of desktops within each assignment, and so on.
    If you plan to have pods running at a large scale, consider adopting the approach of having multiple subscriptions with those multiple subscriptions under one Microsoft Azure account. Microsoft Azure customers can, and often prefer, this approach because it provides some benefits for ongoing management of the subscriptions. Using this approach, you would deploy a single pod per subscription, roll up those subscriptions in a single "master account", and avoid the chances of hitting the Microsoft Azure limits that are imposed on a single subscription.
  • Outbound Internet access is required on the Microsoft Azure Virtual Network (VNet) that is connected to the node's temporary jump box VM and pod manager VM (or plural VMs for the case where high availability is enabled on the pod). Proxy-based authentication is supported in this release. You must provide your proxy details in the pod deployment wizard. For pod deployment, specific DNS names must be reachable and specific ports and protocols must be allowed. See VMware Horizon Cloud Service Deployment Guide for the connectivity requirements.
  • Subnet sizing: Expanding the size of the pod's subnets after the pod is deployed is not currently supported. As a result, for production environments, you should use subnet sizes that are large enough to accommodate the following requirements:
    • Management subnet: When deploying a pod, as of March 2019, the pod's management subnet is required to have a minimum of CIDR /27, where in previous releases a lower minimum CIDR of /28 was allowed. This change was made to reduce the occurrence of issues that can happen during pod updates due to lack of available IP addresses in the subnet. A CIDR of /27 provides for 32 IP addresses.
    • VM subnet - primary: Use a CIDR in a range that is large enough to accommodate attaching the VMs for your anticipated VDI desktops, the RDS images, and every VM in the pod's RDS farms. The pod manager VMs and the Unified Access Gateway VMs also need some IP addresses from this subnet (12 addresses total to accommodate the blue-green update of an HA-enabled pod with both types of gateways). Generally speaking, the range of /24 to /21 would provide for typical use cases.  Note: At times, this VM subnet is referred to as the desktop subnet or the tenant subnet.
    • Starting with service release July 2020 and pod manifest 2298.0, a new feature provides for using additional tenant subnets for your VDI desktops and RDS farm VMs. Those additional subnets can be in the same VNet as the pod or in peered VNets. For a pod at manifest 2298.0 or later, you can edit the pod's configuration to include those additional subnets. Then you can specify use of those additional tenant subnets in the definitions of your farms and VDI desktop assignments instead of them using the primary VM subnet. Use of these secondary subnets for your farm VMs and VDI desktop VMs provides for simplified administration, because you can specify which farms and VDI desktop assignments are on which tenant subnet and VNet.
    For the feature to deploy the external gateway into its own VNet, the VNets must be peered. As a result, you must create the subnets manually in advance of running the deployment wizard. For the external gateway's VNet, its management subnet and back-end subnet must each adhere to the same minimum CIDR /27.

Knowledge of the following facts is useful before connecting Horizon Cloud to pods installed on-premises or in VMware Cloud on AWS.

  • If your Horizon Cloud tenant account was created on or after March 17, 2020 in one of the following regions: US-2, Europe-2, Australia-2 (also formerly known as PROD1_NORTHCENTRALUS2_CP1, PROD1_NORTHEUROPE_CP1, PROD1_AUSTRALIAEAST_CP1), you must use Horizon Cloud Connector version 1.6 or later to connect those pods to Horizon Cloud. The date on your Welcome to Horizon Cloud Service email is the date to use to determine if your tenant account was created after March 17, 2020. The email also states the region in which your account is created. Earlier versions of the Cloud Connector will have compatibility issues when used with tenant accounts created on or after March 17, 2020 in those regions.
  • Outbound Internet access is required for the Cloud Connector to communicate with the service's cloud plane, especially to receive the licensing details. Specific DNS names must be reachable and specific ports and protocols must be allowed. See VMware Horizon Cloud Service Deployment Guide for the connectivity requirements.
  • Before connecting a second Horizon pod to Horizon Cloud, you should log in to the Horizon Cloud administrative console and complete the Active Directory domain registration process after connecting your first Horizon pod to Horizon Cloud using the Cloud Connector's onboarding process. When you pair multiple Horizon pods with Horizon Cloud before completing that Active Directory domain registration, unexpected results might occur when you eventually log in to the console to attempt the domain registration process.
  • Due to a known issue, when you are using an on-premises Active Directory domain to service a pod in VMware Cloud on AWS, slow access times might occur due to network latency or network congestion between that on-premises Active Directory domain and the pod in VMware Cloud on AWS which results in calls to the domain timing out. Symptoms of this latency typically include the Active Directory login screen failing to complete the login before timing out. If you experience such symptoms, configuring a writable domain controller in each in-cloud software-defined data center (SDDC) might help.

Product Documentation and Additional Helpful Resources

To access the product documentation for all deployment models of Horizon Cloud, see the VMware Horizon Cloud Service documentation landing page.

Visit the community site for helpful tips and to ask any questions. White papers are also available in the Resources section of the Horizon Cloud product page.

Known Limitations

The following limitations apply to all deployment types.

  • The Web-based console is not supported in the Apple Safari browser. Some user interface features might not work correctly. In a Mac OS, instead of Apple Safari, you can use Chrome or Firefox browsers.
  • Every pod associated with your Horizon Cloud customer account and connected to Horizon Cloud must have line of sight to the same set of Active Directory domains and have one-way or two-way trust configured along with that line of sight.

Horizon Image Management Service has the following limitations.

  • Horizon pods located in VMware Cloud on AWS are not supported.
  • Horizon Image Management Service only supports vCenter Server authentication based on user name and password credentials.
  • During image publishing operations, you must prevent activities occurring in vCenter that would cause guest VM migrations on the image's underlying VMs. Guest VM migrations that occur at the same time as image publishing operations on the VMs can affect the image publishing operations.
  • The system default setting is to have three import or publish operations in progress at a time. As an example, importing can be in progress for one image while publishing is in progress for two images. You can change the default on the console's General Settings page. Increasing the setting will increase the time to complete the replication.
  • Horizon Image Management Service does not support the management of images for linked-clone workspace assignments. In addition, this release requires that you disable Horizon View Composer on any pods that you want to manage. You cannot publish images successfully when Horizon View Composer is enabled.
  • Horizon Image Management Service requires the privileges of the full, built-in Windows administrator to create a directory and install Horizon Agent on the virtual machines (VMs) cloned from managed images. For more information, see the Microsoft documentation topic Enable and Disable the Built-in Administrator Account.

Microsoft Azure deployments have the following known limitations.

  • Due to limitations with how Microsoft Azure VNets handle concurrent subnet creation and deletion operations, running concurrent pod-related operations that require modifying the same VNet at the same time can result in failure to complete those operations. To avoid running into this issue, avoid running pod deployment, pod deletion, or pod edit operations that involve subnets at the same time when those pods are using the same VNet. Here are some examples of concurrent pod-related operations involving modifying the VNet where the chances of experiencing concurrent subnet actions on the VNet can occur, resulting in failures to complete the operations:
    • When you do not create your subnets ahead of time and are having the pod deployer create the subnets using CIDRs, and you initiate creation of two pods concurrently on the same VNet. The subnets are being added to the VNet for both pod creations simultaneously.
    • When one pod is deploying and you initiate deletion of another pod on the same VNet. The subnets are added to the VNet for the deploying pod at the same time the other pod's subnets are being deleted from the same VNet.
    • When you edit a pod to add an external gateway configuration in the pod's VNet using CIDR blocks while another pod is in progress of being deleted. The subnets are added to the VNet for the gateway configuration at the same time the other pod's subnets are being deleted from the VNet.
  • Due to a known issue, use of the disk encryption feature for farms and VDI desktop assignments is not currently supported for pods in Microsoft Azure Government clouds.
  • Expanding the size of the pod's subnets after the pod is deployed is not currently supported. Before you deploy a pod, you must ensure the address spaces for the subnets you specify in the deployment wizard are large enough to accommodate your expected usage. Note: A new feature in the July 2020 release provides for adding tenant subnets for use by your farms and VDI desktops assignments after the pod is deployed. This feature provides for flexibility to add tenant subnets located in the pod's same VNet or in a peered VNet for use by your farm and desktop VMs after the pod is deployed. For more details, see the Administration Guide.
  • This release does not support use of the following Horizon Agent features: VMware Logon Monitor service. By default, the Horizon Agents Installer disables the VMware Logon Monitor service in all installations that the installer performs.
  • During the ten-minute process of updating a pod from an earlier software level to the latest one, end users who have connected sessions to the updating node will have those active sessions disconnected. No data loss will occur – except for the case where the RDSH farm or VDI desktop assignment serving the sessions has the Logoff Disconnected Sessions set to Immediately. For such farms and VDI desktop assignments, the disconnected sessions are also logged off immediately and in-progress user work is lost in those conditions.
    After the update process is complete, those users can reconnect.
  • Multiple pods cannot share the same fully qualified domain name that is set on their Unified Access Gateway configurations. Each pod configured with Unified Access Gateway instances needs its own unique fully qualified domain name (FQDN). The FQDN cannot contain underscores. Starting with the July 2020 service release, deploying a brand new pod of that release's manifest requires using the same FQDN in both the external and internal Unified Access Gateway configurations on that pod. Because both gateways will have the same FQDN, you configure Split DNS (Split Domain Name System) to resolve the gateway address either to the external gateway or internal gateway depending on the origin network of the end-user client's DNS query. Then the same FQDN used in the end-user client can route to the external gateway when the client is on the Internet and route to the internal gateway when the client is on your internal network.
  • Your authenticated (logged in) session into the Web-based administrative console will time out after the time setting that is configured in the console's General Settings page. The default is 30 minutes. If you have at least one cloud-connected pod, you can change the default to a value ranging from 30 minutes to 180 minutes. In most cases, when the configured time is up, the system will automatically explicitly log you out and present a message that you must log back in. However, sometimes the system ends your authenticated session and does not explicitly log you out. When that happens, when performing certain tasks in the console, error messages might be displayed which do not accurately reflect the current state, such as the node deployment wizard fails to validate your subscription entries, values are not displayed in drop-down lists, and the Farms page reports no node is available in which to create a farm and error messages stating "No service_sessions of type identity_node were provided". If you start to see such behavior and you have been using the console for 30 minutes or more, manually log out and then log back in.
  • The USB redirection capability is not supported when using the VMware Horizon Client for Android to access virtual desktops and remote applications served by your Horizon Cloud environment.
  • For GPU-enabled master images based on server-type operating systems, Microsoft Windows Server versions 2016 and 2019 are recommended to avoid limiting the number of end user sessions. Due to an NVIDIA driver limitation on Windows Server 2012 R2, the maximum number of sessions for each RDS desktop server is 20.
  • The NSX Cloud capabilities in this release are not supported for Microsoft Windows Server 2019.
  • If you have an image using Microsoft Windows 10 1709 (RS3) and you want to update it to Windows 10 1803 (RS4) or Windows 10 1809 (RS5), first upgrade that Windows 10 1709 to the latest Horizon Agent version 19.4 before proceeding with upgrading the Windows operating system.
  • By default, when you use the automated Import Virtual Machine from Marketplace wizard to create an image with a Windows 2012 server operating system, the resulting image does not have the Desktop Experience enabled. If you want the resulting image to have the Desktop Experience, you must manually enable the Desktop Experience in the resulting image.
  • When you deploy a Horizon Cloud pod in Microsoft Azure after you have already configured True SSO for previously deployed pods, the system does not automatically pair the new pod with the Enrollment servers. You must manually repeat the steps to export the pairing bundle and import it into the Enrollment servers. For the steps, see this release's Administration Guide.
  • In a URL redirection customization, URL patterns are treated as case sensitive when they are intercepted by the Horizon Client. For example, URL redirection does not occur for URL patterns specified as *GOOGLE.com and *Google.com, even though the pattern *google.com is redirected. Redirection for the end users does not occur if the specified pattern does not match the actual character case used in the target file systems.
  • The system retrieves the data for the Utilization, Concurrency, Session History, and Top Applications reports once a day, at a specific UTC time. The data for the Utilization and Concurrency reports is retrieved at 2 AM UTC, the data for the Session History report is retrieved at 2:10 AM UTC, and the data for the Top Applications report is retrieved at 2:30 AM UTC. As a result, the reported information that is displayed in the administrative console might not reflect the data collected between the last retrieval time and the time at which you are viewing the reports in the console. As an example, because the logic for the Users and Peak Concurrency data in the Concurrency report is calculated on the daily basis for which the data is retrieved, the data from user activity on April 23 is calculated at the 2 AM UTC time point on April 24 (the following day). After that time point is passed and the system retrieves the collected data, the data from April 23 gets displayed in the report. If one of your end users starts a session after the 2 AM UTC time point on April 23, data for that user's session will not be reflected in the on-screen report until after 2 AM UTC on April 24.
  • In workflows that result in the system creating VMs, such as creating farms, images, and assignments, if you try to enter a name that is longer than length supported by the system for the to-be-created item, the system prevents you from typing in more than the supported number of characters. The number of characters supported for an item's name depends on the workflow.
  • In a Microsoft Azure multi-pod environment, you cannot reuse names that you used in one pod when creating items in another pod. The reason for this limitation is that pods in the multiple-pod environment share the same Active Directory domain and the same VNet. As a result, if names are shared within such multiple-pod environments, unexpected behavior can occur. This limitation applies to names for image, farms, and VDI desktop assignments. Ensure that unique names are used for your master images, farms, and VDI desktop assignments.
  • Follow these rules when entering characters in the administrative console:
    • Use only standard ASCII characters in user names and passwords, and for the password when downloading the DaaS SSL bootstrap file. If you use non-ASCII characters for these items, unexpected results might occur.
    • When entering names for imported images, farms, assignments, and other assets that result in creating a VM in Microsoft Azure, do not enter more than 12 characters for the name.
    • Do not use commas in user passwords.
    • When using the Import wizard to create a master VM from the Microsoft Azure Marketplace:
      • Enter a username and password that adheres to the Microsoft Azure requirements for VM admin usernames and passwords. See the Microsoft Azure FAQ page for details.
      • Do not enter a name for the image that ends with a hyphen (-).
      • Do not include an underscore character (_) in the image name.
  • If you initiate converting a desktop to an image but cancel before the task finishes, a second attempt to convert the desktop to an image may fail. To avoid this issue, you should power off the desktop and power it on again before attempting to convert it to an image a second time.

Known Issues

Note: Known issues for Horizon pod software version 7.12 and earlier versions of Horizon pod software are contained in the release notes for the Horizon software product. Horizon software version 7.12 documents are linked from the VMware Horizon 7 Documentation page. Even though you cloud-connect these pods, the known issues for the Horizon pod software reside in the Horizon product release notes.

Note: Due to a known issue, the regional sentence in your Welcome to Horizon Service email might have contained a system string name instead of a human-friendly name. As an example, your welcome email might contain a name like EU_CENTRAL_1 instead of Europe-2.

The known issues are grouped as follows:

Note: The numbers in parentheses stated in each known issue refer to VMware internal issues tracking systems.

Active Directory Related Known Issues

  • Primary bind account lockout is not detected until you perform an action involving Active Directory in the administrative console. (2010669)
    Due to this issue, an administrator logged into the Web-based administrative console will not see a primary bind account lockout notification until an action involving Active Directory is performed in the user interface, such as when searching Active Directory to add users to assignments. The underlying services only detect a locked-out service account when they make a request to talk to Active Directory for either authenticating or searching (user or group).
    Workaround: None.
  • It takes up to 15 minutes for the Web-based administrative console to reflect a lockout or unlocked state of the primary bind domain account. (2009434)
    The system's connection object to Active Directory is cached for 15 minutes. As a result, it might take 15 minutes from the time point when the primary bind account goes to locked state and the system raises the notification to the administrator. Conversely, after the administrator clears the locked-out condition of the account, it might take up to 15 minutes for the system to stop notifying about the now-cleared account.
    Workaround: None.
  • For farms in a pod in Microsoft Azure, reusing the same farm name with a different domain in the same Active Directory forest can lead to domain join failures due to duplicate service provider names (SPNs). (1969172)
    Due to a new feature for domain controllers in Microsoft Windows Server 2012 R2 and higher, a duplicate SPN check on the domain controller causes domain join failures. See the Microsoft KB article 3070083.
    Workarounds:
    - Avoid reusing farm names.
    - As described in that Microsoft KB article, disable duplicate SPN checks in the Active Directory domain.

Images, Farms, Assignments Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • For pods deployed into Microsoft Azure Government cloud subscriptions, using the disk encryption feature in farms and desktop assignments fails. (2572579)
    When your pod is located in Microsoft Azure Government clouds and you try to create a farm or VDI assignment with the disk encryption feature selected, the creation process fails with error 'Azure error encrypting the VM'.
    Workaround: None.
  • In the Servers tab for an existing farm, all of the User Login Mode choices give an error message that the Horizon Agent must be updated. (2528295)
    Use of the administrative console to set the User Login Mode depends on detecting agent version 20.1.0 running in the farm VM. However, that version of the agent might not yet be available in the cloud control plane for updating the agents in your existing farm VMs.
    Workaround: None. When the 20.1.0 version of the agent is available in the cloud plane, then you can update the farm VMs to that agent to use the User Login mode choices.
  • Sometimes some desktop VMs out of a large floating VDI desktop assignment report unknown agent status. (DPM-3201)
    In floating VDI desktop assignments with large numbers of desktop VMs, due to a known issue, a small number of those desktop VMs can go into an unknown agent state because some Windows services, like the Horizon Agent's Blast service or the Microsoft Azure service, do not start or are slow to start. As a result, in the administrative console, the Agent Status column for those desktop VMs shows "Unknown" state, with reported agent errors.
    Workaround: In the console, use the Restart action to restart those VMs.
  • The Import Desktop wizard creates Windows Server 2012 images without the Desktop Experience enabled. (2101856)
    Due to a known issue, when you use the automated Import Desktop wizard to create an image with a Windows Server 2012 operating system, the resulting image does not have the Desktop Experience enabled.
    Workaround: If you want the resulting image to have the Desktop Experience, you must manually enable the Desktop Experience in the resulting image. Note also that for the Windows Server 2012 operating system, to install the Horizon Agent with the Scanner Redirection option requires the Desktop Experience be enabled in the operating system.
  • When publishing (also known as sealing) an imported VM, the process might result in a timeout or other failures to publish due to sysprep failures. (2036082, 2080101, 2120508, 2118047)
    After you click Convert to Desktop on an imported VM and Publish to make it a published (sealed) image, a number of operations are performed on the VM. These operations include running the Windows System Preparation (sysprep) process, shutting down the VM and powering it off, and so on. Due to industry-known issues with the Windows sysprep process and customizing virtual machines, sometimes the publishing process fails for various reasons. On the Activity page, you see messages like "Timeout Error Waited 20 minutes for virtual machine to power off.", and other sysprep failure message.
    Workaround: Generally speaking, you can avoid such sysprep issues when you create the master VM using the Import Virtual Machine from Marketplace wizard and select Yes for the wizard's Optimize Windows Image toggle. If you are seeing this error for a master VM in which you did not use that option, or if you manually created that master VM, refer to VMware KB 2079196, Microsoft KB 2769827, Microsoft MVP article 615, as well as the VMware Horizon Cloud Service Administration Guide for best practices in configuring your master VM to minimize likelihood of having sysprep issues when you go to publish the image. If you see the timeout errors in the Activity page, you can try this workaround: on the Images page, use the Convert Image to Desktop action on the image. When the Activity page indicates converting the image to a desktop is successful, navigate to the Imported VMs page. Connect to the VM by following the steps in the Administration Guide, and apply the best practices described in the KBs. After you have On the Imported VMs page, select the VM and click Convert to Image to run the publishing process again.
  • During farm creation, sometimes the server VMs are stuck at the customization step. (2010914, 2041909)
    Sometimes during the sysprep process on the farm's server VMs, a Windows service named "tiledatamodelsvc" prevents sysprep from accessing Windows files that it needs to complete the sysprep customization process. As a result, the farm's server VMs do not move past the customization step. The sysprep error log contains the line "Error SYSPRP setupdigetclassdevs failed with error 0".
    Workaround: If you encounter this issue and see that error message in the sysprep error log file, try disabling the "tiledatamodelsvc" service in the image and then creating the farm.
  • Agent status might display as 'undefined' on the Imported VMs page after duplicating an image or manually creating an image in Microsoft Azure. (2002798)
    When you use the Duplicate button on the Images page to clone a published image or when you manually create a master image in Microsoft Azure, the resulting VM is listed on the Imported VMs page. Due to this issue, even when the VM is fully powered-on, the agent status might be displayed as 'undefined'. However, when you select the VM and choose Convert to Image to publish it, the user interface reports the agent in 'Active' state.
    Workaround: None. If the Reset Agent Pairing or New Image or Convert to Image workflows report the agent as 'Active', you can ignore the 'undefined' status on the Imported VMs page.

App Volumes on Pods in Microsoft Azure

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • When your environment has multiple pods in Microsoft Azure, the Capture process can sometimes go into an unknown state after the process has completed. (2600573)
    When your environment has multiple pods with which you are using App Volumes, sometimes after running the capturing process, the console indicates the capture is in an unknown state even though the capture process on the VM has completed.
    Workaround: To work around this issue, re-import the application pakage using Inventory > Applications > New > Import. As a result, the application package is successfully imported as a separate application and the subsequent assignment and application launch works.

Agent Update Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • When you attempt an agent update on an image that has a Windows update pending, the update process might fail. (2234964)
    If the image needs an update to the Windows OS, as opposed to a minor non-OS update, this can cause OS resources to be offline and not available for the agent update.
    Workaround: Wait until the Windows update is complete and retry the agent update. To confirm that all Windows updates are complete, you can take the image offline, perform all pending updates, and re-publish the image before initiating the agent update.

Reports and Monitoring Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • In the User Activity report, the displayed weekly average (hrs) is not intuitive. (1817065)
    Due to this issue, the weekly statistics fluctuate along the time because the calculation logic is dividing the current week's duration by seven (7) and not rounding up to a whole week. For example, when you select the last 30 days, the data for completed weeks is unchanged but the data for the current week is divided by seven (7). The current logic is weekly average (hrs) = daily average (hrs) * 7 days, resulting in the last 30 days weekly average = (total duration / 30 days) * 7 days.
    Workaround: None.
  • The Desktop Health report does not reflect a newly updated farm or VDI desktop assignment name until an hour after the name change. (1756889)
    If you change a farm's name or VDI desktop assignment's name, it takes an hour for the Desktop Health report's Assignment drop-down menu and Assignment column to reflect the new name.
    Workaround: Wait an hour before expecting the new name to appear in the report.
  • The formatting in some of the CSV files that you can export from the Reports user-interface screens do not match the on-screen tables. (2015500)
    Some of the Reports page's subscreens provide an export feature to export the displayed data in CSV format. Due to this issue, the formatting in the CSV files exported from the Desktop Health, Concurrency, and Session History reports do not precisely match the ones you see displayed on the screen. For example, the column headings might be different and the CSV files might have more columns of data than in the on-screen tables.
    Workaround: None.

Identity Management, True SSO Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • When your pod from a previous manifest version is updated to this release and that pod has two-factor RADIUS configured on its Unified Access Gateway instances and is also integrated with Workspace ONE Access, launching a desktop from the Workspace ONE Access portal using the browser displays the RADIUS login form with the user name field prefilled with the user's UPN. (2248160)
    This symptom occurs because of a change that was released in VMware Horizon HTML Access 4.10. When your pod in Microsoft Azure from a previous Horizon Cloud release is configured with Unified Access Gateway instances and two-factor RADIUS authentication and you configure that pod to use Workspace ONE Access, previously when launching a desktop from Workspace ONE Access using the browser, the RADIUS login form prompts for the user name and passcode. The end user would type the user name and passcode in the form. However, due to this issue, after upgrading that pod to this release, using the same desktop launch steps, the RADIUS login form has the user name field prefilled with the domain user's UPN. This behavior only occurs when using the browser to launch the desktop. It does not occur when using Horizon Client.
    Workaround: If this situation is encountered, the end user can clear the prefilled user name field and enter their information. Generally, for most environments that are integrated with Workspace ONE Access, the two-factor authentication would be configured in Workspace ONE Access and not on the underlying Unified Access Gateway instances.
  • Launching a second desktop from Workspace ONE Access using the Horizon Client can fail with the error 'You are not entitled to that desktop or application'. (1813881, 2201599)
    This symptom occurs in the following situation. The user has entitlements to two dedicated VDI assignments through a group entitlement. Both dedicated VDI desktop assignments are listed in Workspace ONE Access when the user logs in. The user launches the first desktop using Horizon Client. That desktop connects. Then the user tries to launch the other desktop from the other assignment, also using the Horizon Client. The launch of that other desktop fails with an error indicating the user is not entitled. However, this issue is seen only for the first attempt on the second desktop. If the user launches the second desktop using the browser, subsequent attempts to launch the second desktop using Horizon Client succeed.
    Workaround: If you encounter this situation, try launching the second desktop using the browser.

User Interface Related Known Issues

Note: Unless otherwise noted in the known issue text, the known issues listed here apply to pods deployed in Microsoft Azure.

  • In the User Card, when you click Reset on a VDI desktop session from a pod in Microsoft Azure, an error message is displayed even though the VM is successfully reset. (2567272)
    Due to this issue, even though the reset operation is initiated successfully and the VM eventually is reset, the Administration Console displays an error message box. The message implies the system was unable to complete your request even though the VM actually gets reset.This issue might be seen for a desktop session from a floating VDI desktop assignment.
    Workaround: None. The reset operation is initiated successfully and the VM eventually is reset. Close the error message box that is displayed.
  • The Logon Segments chart displayed in the session dashboard has no data.
    The VMware Logon Monitor service provides the data for the Logon Segments chart that appears in the session dashboard. However, this release does not support use of the VMware Logon Monitor service and by default, the Horizon Agents Installer disables the VMware Logon Monitor service in all installations that the installer performs. As a result, even though no data is reported that the Logon Segments chart can display, you see the Logon Segments chart is still visible in the session dashboard. This issue applies to all types of pods.
    Workaround: None.
  • When using the administrative console in one browser tab, if you try to launch a disconnected desktop that you have in another browser tab in the same browser, the HTML Access portal is also logged off and you must log back in to the HTML Access portal itself. (2118293)
    Usually when you launch a desktop and disconnect from it without logging out of the desktop, you stay logged in to the HTML Access portal itself and you can reconnect to the disconnected desktop without having to enter credentials to the HTML Access portal. Due to this issue, if you are in a browser window where you are logged in to the console in one browser tab and use another browser tab to log in to the HTML Access portal and launch a desktop, when you disconnect from that desktop and try to reconnect to it, the HTML Access portal logs off. Then you must re-enter credentials to the HTML Access portal before you can reconnect to that desktop.
    Workaround: To avoid this issue, log in to the administrative console using a separate browser window from where you have the HTML Access portal. This behavior only occurs if you are also logged in to the console in a browser tab in the same browser window in which you are also using the HTML Access portal.
  • In the User Card screen for a specific user, VDI dedicated desktop assignments are removed from the Assignments tab after the user's first launch of the dedicated desktop from that assignment. (1958046)
    When a user is specified in a VDI dedicated desktop assignment as an individual user, not through an Active Directory group, that VDI dedicated desktop assignment appears in the Assignments tab in the User Card screen for that user only until the user's first launch of a dedicated desktop from that assignment. After the user's first launch of a VDI dedicated desktop from that assignment, the user card's Assignments tab no longer displays that VDI dedicated desktop assignment for that user. The user's first launch results in that user claiming a specific dedicated desktop from the underlying pool defined by that assignment and the system maps that specific dedicated desktop to that particular user. When that mapping is made, that specific dedicated desktop gets the Assigned state, and it is listed on the user card's Desktops tab for that user.
    Workaround: Instead of relying on the user card's Assignments tab in this case, to see the already launched VDI dedicated desktops assigned to a specific user, you can use the Desktops tab. If you need to locate the specific VDI dedicated desktop assignment in which that user-desktop mapping is made, obtain the desktop name from the user card's Desktop tab and use the search by VMs feature of the top banner search to list that specific desktop VM. In the results from the search by VMs, click the name to open the specific assignment page that has that particular dedicated desktop. Then you can locate the user in the assignment's details.
  • The What's New screen appears even though you previously selected the option not to continue showing it. (2075825)
    This issue applies to environments with any pod type. Due to this issue, if you clear your browser cache or you use a different browser than the one in which you previously selected the option to not show the What's New screen, the screen might appear when you log in to the administrative console. The flag for whether to show the What's New screen is stored in the browser's local cache, instead of per user.
    Workaround: None.
  • Even though the image creation process has not fully completed, the Getting Started screen displays Completed for the Create Image step. (2100467)
    Due to this issue, the Create Image step is marked as completed prematurely.
    Workaround: Use the Activity page to verify that the image creation process has completed.
  • When using the administrative console, you might see placeholders instead of the actual text strings or you click a button on a page and nothing happens. (2045967)
    This issue applies to environments with any pod type. VMware periodically updates the in-cloud management environment that hosts the Web-based console. This issue can occur when static content has been cached in the browser prior to the latest in-cloud update. It is a temporary issue that will clear when the browser cache is cleared.
    Workaround: Try logging out of the console, clearing the browser cache, restarting the browser, and then logging back in to the console.
  • Application names are displayed in lowercase characters when end users access them using Workspace ONE Access. (1967245)
    When your Horizon Cloud environment is integrated with Workspace ONE Access, your end users access their assigned desktops and applications using Workspace ONE Access. Due to this know issue, the users see the application names displayed with lowercase characters, regardless of the actual case used in the application names. This limitation is due to the way Workspace ONE Access creates launch IDs from Horizon Cloud by using older Horizon Cloud REST APIs.
    Workaround: None.
  • The memory usage percentages reported for desktop health reports and used for the desktop health alerts are based on percentage of committed memory, which equals physical memory plus pagefile size, and not on percentage of only physical memory. (2015772)
    Committed memory for a desktop VM is calculated as physical memory plus pagefile size. When calculating the percentage of memory usage in a desktop, the system takes the percentage used of that total (physical memory plus pagefile size). Both the desktop health alerts and the memory usage report in the desktop health reports use that percentage calculation. However, when you log into a desktop VM and open the Windows Task Manager to view the memory usage in the desktop's Windows operating system, the Windows Task Manager displays percentage based on physical memory only. As a result, the memory usage percentage that the desktop's Windows Task Manager displays does not match the memory usage percentage displayed in the Desktop Health reports or in the desktop health alert.
    Workaround: Keep in mind this difference if you decide to make a comparison between the memory usage percentage reported by a desktop's Windows Task Manager and the memory usage percentage reported in the console's Desktop Health report and desktop health alerts for that desktop.
  • If a desktop VM's CPU usage is at or close to 100%, the desktop alert is not triggered. (1446496)
    If an application or something in the desktop VM causes the VM's CPU usage to reach 100%, the desktop agent fails to send as many data samples as it usually sends to Horizon Cloud because the CPU is very busy. As a result of the low sample count returned, the calculation the system uses to trigger the desktop alert is affected.
    Workaround: None.

End User, Horizon Agent, Horizon Client Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • For a VM running Microsoft Windows 10 Enterprise multi-session 2004 or later, the DPI Synchronization and Display Scaling features have issues (2587685, DPM-6352)
    Due to an inability to query the current DPI in VMs running Microsoft Windows 10 Enterprise multi-session 2004 or later, these features with those VMs do not work as documented in the Horizon Client documentation. The DPI Synchronization and Display Scaling features do not work for PCoIP session reconnections. The DPI Scaling feature does not work for Blast session reconnections.
    Workaround: Log out of the session and log back in again.
  • For a VM running Microsoft Windows 10 Enterprise operating system 1903 or later, the DPI Synchronization and Display Scaling features have issues (2589129)
    Due to an inability to query the current DPI in VMs running Microsoft Windows 10 Enterprise client operating system 1903 or later, when reconnecting a PCoIP or Blast session, the features do not work as documented in the Horizon Client documentation.
    Workaround: Log out of the session and log back in again.
  • Sometimes when launching a VDI desktop using VMware HTML Access, an error message about being disconnected appears, and then subsequently the launch is successful. (2243471)
    VDI desktop virtual machines have a default session connection timeout, and when that timeout is reached, the session is disconnected. Sometimes, when launching a desktop, if the end user's HTML Access session has timed out at the time the desktop's default session connection timeout is reached, the desktop will initially throw that error, and then continue launching the desktop.
    Workaround: None.
  • When a VDI desktop assignment has disk encryption selected and a one- or two-core VM model, and a desktop's underlying VM is powered off, the Horizon Client's automatic retry option might fail to make a connection. (2167432)
    When a VDI desktop VM is powered off due to the VDI desktop assignment's power management settings, the VM has to power on and get ready before an end user connection can be made to that desktop. When an end user's client tries to connect to a VDI desktop assignment's VM and the VM is powered off, the system starts powering on that VM. For non-encrypted VMs, the VM is typically ready to accept a client connection in under 10 minutes. However, an encrypted VM with one or two cores usually takes longer than 10 minutes to get ready to accept a connection. The Horizon Client's Client Retry option has an upper limit of 12 minutes. Because of this upper limit of the Client Retry option, when the end user has the client automatically retry the connection while the desktop's underlying VM is getting powered on and ready but the connection is not made within 12 minutes, the client's automatic retry gives up. Because an encrypted VM usually takes longer than 12 minutes until it is ready to take the client connection, the end user might see that Horizon Client's automatic retry fails to complete the connection to their encrypted desktop VM.
    Workaround: When you want to have disk encryption for a VDI desktop assignment, select a VM model that has more than two cores. Otherwise, if your VDI desktop assignment has disk encryption and has a VM model with one or two cores, inform your end users that they might experience this issue with using the Client Retry option with these encrypted desktop VMs.
  • For a virtual desktop from a dedicated VDI desktop assignment, the shortcut link on the Horizon client's Recent page might not launch the desktop. (1813881, HD-3686, DPM-1140)
    The iOS and Android versions of the Horizon clients have a Recent page which displays links to recently launched desktops. When the user does the initial launch of a dedicated pool virtual desktop, the desktop launches as usual, and the client creates a launch icon on the Recent page. However, when the user disconnects from the desktop and then tries later to launch the desktop from the Recent page, the desktop fails to launch because the launch icon is using a shortened version of the desktop name.
    Workaround: Launch the desktop from the client's main page, and not the Recent page.

Updates to Pods in Microsoft Azure Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • While a pod is undergoing an update, active end user sessions to that pod are disconnected. (HD-12577)
    During the ten-minute process of updating a pod from an earlier software level to the latest one, end users who have connected sessions to the updating pod will see those active sessions disconnected. However, no data loss will occur – except for the case where the RDSH farm or VDI desktop assignment serving the sessions has the Logoff Disconnected Sessions set to Immediately. For such farms and VDI desktop assignments, the disconnected sessions are also logged off immediately and in-progress user work is lost in those conditions.
    Workaround: None. After the update process is complete, those users can reconnect. To prevent data loss for end users, before running the update, make sure the settings in the pod's farms and VDI desktop assignments do not have Logoff Disconnected Sessions set to Immediately.

Horizon Image Management Service Known Issues

  • Image publishing or replication hangs and times out after image publish. (2597932)
    During the image publish operation, the image copy gets stuck in the ‘Specializing VM’ or ‘Replicating’ state for more than 3 hours. After 24 hours, the image copy shows as ‘Failed’ with the message ‘Image Publish/Replication timed in Pod xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx’. This issue is more likely to occur if the publish operation is performed during the automated live migration of VMs.
    Workaround: None. This issue will be resolved in a future release.

Localization Related Known Issues

Note: The known issues listed here apply to pods deployed in Microsoft Azure.

  • When you are adding or editing locations in the administrative console, location names are not localized. (2366913, DPM-3282)
    Workaround: None.
  • When non-ASCII or high-ASCII characters are used in the True SSO template name, retrieving the template fails. (1951143)
    Due to this known issue, if your True SSO template name contains non-ASCII or high-ASCII characters, you cannot successfully configure True SSO with your Horizon Cloud environment.
    Workaround: To avoid this issue, use only ASCII characters in the names of your True SSO templates.
  • Some of the strings in the Desktop Health page's desktop health alerts are not localized. (2019363)
    Workaround: None.

Previous Issues Resolved in this Release

This release resolves the following issues reported in the previous release:

Resolved Active Directory Related Issues

  • When you remove a configured admin group from Active Directory directly before removing the group in the Administration Console's Roles & Permissions page, the following issues occur on the Roles & Permissions page. (2537147)
    You use the Settings > Roles & Permissions page to grant Horizon Cloud administrative roles to AD groups from your AD domain. If you remove an AD group from the AD domain before removing the group from the Horizon Cloud role:
    • The deleted group is listed on the Roles & Permissions page for that role as \unknown\XXXX
    • If you try to edit the Roles & Permissions page to add a new AD group while that \unknown\XXXX is displayed, an error occurs and the group details are not saved.
    This issue is resolved in this release.

Resolved End User, Horizon Client Related Issues

  • Users experiencing delays connecting to dedicated VDI desktops. (2257813)
    This issue occurs when a dedicated desktop has been powered off by default (no power schedule) but then gets a broker request and is powered on. When this happens, it takes up to 10 minutes before the agent is ready to allow the end user to log in.
    This issue is resolved in the current release so that these delays no longer occur.
  • Users get disconnected after one hour from their desktops or remote application sessions when using HTML Access (Blast) and PCoIP protocols. (2519400)
    This issue is due to an issue in Microsoft terminal services in Microsoft Windows 10 Enterprise multi-session systems. For session-based desktops and remote applications provisioned from RDSH farms based on the Microsoft Windows 10 Enterprise multi-session operating system, when an end user reconnects to an existing desktop or remote application session using either HTML Access (Blast) or PCoIP protocol, after an hour has passed, the user's session is forcefully disconnected. There is no data loss. Even though the user can reconnect again and the session is in the same state it was at the disconnect time, this behavior repeats and the reconnected session is again forcefully disconnected after an hour.
    This issue is resolved using Horizon Agents Installer (HAI) 20.1 or later. When your 1976.0 pod is updated to manifest 1976.1 or later, the Import Virtual Machine from Marketplace wizard will automatically install the agent software that has this fix. If your pod is still at 1976.0 manifest level, running the wizard will still install the agent software with the issue. However, when you seal the VM, the Images page will show the blue dot, signifying that you can use the Update Agent feature to update the agent to the level with the fix.
  • When switching protocols in the client, if you choose the Connect choice instead of Log Out and Reconnect, the client might become unresponsive. (2528014)
    This issue happens when switching protocols in the client after establishing a session to an RDSH farm using one protocol. When you launch the desktop or application using one protocol, disconnect that session, use the client's menu to switch to a different protocol, launch the same desktop or application, the client presents a dialog box saying "This desktop is open on the server but is running a different protocol." and presents a choice to connect or to log out and reconnect. If you select the Connect button, the dialog appears a second time, and if you select Connect again, the client becomes unresponsive.
    This issue is resolved in pods that are updated to this release's manifest version.

Resolved Horizon Image Management Service Related Issues

  • System prompts for credentials twice when you have two pods in a single vCenter Server (2468092)
    If you have two pods in the same vCenter Server, the system prompts you twice for the vCenter Server credentials during the import process and then replicates the image on the vCenter Server when you publish it.
    This issue is resolved in this release.
  • Images imported from a cloud-connected Horizon pod remain visible in the administrative console after unplugging the pod and you cannot delete them (2552744)
    If you have imported images from a cloud-connected Horizon pod and then use the Horizon Cloud Connector to unplug that pod, the imported images remain displayed on the Settings > Images page and there is no way to delete them.
    This issue is resolved in this release. Note: The VMs remain in your vCenter infrastructure. When the pod is unplugged from the cloud plane, the in-cloud related entities are deleted from the cloud plane.