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

VMware Horizon® Cloud Service™ | Release Date 17 September 2019
VMware Horizon® Cloud Service™ on Microsoft Azure | Version 2.1
VMware Horizon Agents Installer | Version 19.3
VMware Horizon 7 Cloud Connector | Version 1.4

These release notes apply to the service release that went live on September 17, 2019. For pods deployed into Microsoft Azure, these release notes apply to software manifest versions 1600 and later. For the release notes of earlier manifest versions for pods deployed into Microsoft Azure, see the release notes for previous Horizon Cloud releases that are still supported by using the links listed in the left-hand navigation pane at https://docs.vmware.com/en/VMware-Horizon-Cloud-Service/index.html.

This document is revised periodically when the Horizon Cloud Service itself is updated, so that you have current information about the service. Check back for additions and updates to these release notes. For revisions made after the service release date, look for the red Updated text in the document below.

This document was changed on December 4, 2019 for the bulleted items below.

  • Currently, the High Availability (HA) feature for pods in Microsoft Azure is not supported for pods deployed in the following Microsoft Azure cloud environments:
    • Microsoft Azure in China
    • Microsoft Azure Germany
    • Microsoft Azure Government (US Gov Virginia, US Gov Arizona, US Gov Texas)
  • The VMware team is working on adding support for the HA feature for pods in those above listed 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 feature, please contact your VMware representative for assistance.
  • Additional detail is added that the HA feature uses Microsoft Azure Database for PostgreSQL service Gen 5 Memory optimized tier.

Documents updated in this release include:

What's in the Release Notes

The release notes cover the following topics:

About VMware Horizon Cloud Service

VMware Horizon Cloud Service provides visibility, health monitoring, help desk services, and end-user workspaces for cloud-connected pods. Cloud-connected pods can be VMware Horizon 7 pods using on-premises capacity, Horizon 7 pods using VMware Cloud on AWS capacity, and pods using Microsoft Azure capacity. The overall environment consists of the VMware-hosted cloud service, your provided capacity, and VMware software deployed into that capacity.

For example, you can use the Horizon Cloud Administration Console for unified health monitoring and multi-pod workspace assignments for two cloud-connected Horizon 7 pods, one using on-premises capacity and the other using VMware Cloud capacity. Such multi-pod workspace assignments create global entitlements across those cloud-connected Horizon 7 pods. For pods in Microsoft Azure, you can use Horizon Cloud to create master images, from which the pods can provision virtual desktops and remote applications that your end users can securely access from any device.

Updated Horizon Agent Installer 19.3.1 - Released November 2019

Horizon Agent Installer (HAI) 19.3.1 has been released. HAI 19.3.1 addresses a defect in 19.3.0 Agents that manifests itself during Agent Auto Upgrade from 18.x Agents.

  • The issue only impacts VMs that are upgraded via AAU from 18.x Agents (18.2.x, 18.4).
  • The problem does not exist for 19.3.0 Agents installed/upgraded via the interactive/manual installer, nor does it exist for VMs upgraded via AAU from HAI 19.x.
  • There is no functional difference between 19.3.0 and 19.3.1. The fix only impacts the upgrade path from 18.x agents, so if you are already running 19.3.0 Agents it is not necessary to upgrade to 19.3.1.

What's New in This Release

This September 2019 release is the debut of these headline features. If you are someone who has previous experience with Horizon Cloud features and workflows prior to this release, additional detail is provided in For Current Customers - About this Release.

  • Enhanced administrator auditing and logging now available in the Horizon Cloud Administration Console with expanded reporting of the administrator activity and related events. This includes the capability to filter for reporting purposes and the ability to download logs.
  • Enhanced monitoring of VM health and associated sessions in real-time. You will be able to navigate to details on consumption and performance related metrics to gather more actionable details making it easier to identify, categorize and troubleshoot issues with VMs and user sessions.
  • Improved usability and optimization of the Unified Dashboard interactive map view, including more accurate reflection of the pod location and zoom functionality.
  • Enhanced alerting now available for Horizon Cloud on Microsoft Azure pods that encounter an error during pod upgrade and require customer action in order to resolve.
  • Gateways now support the creation and editing of the two-factor authentication settings post-pod deployment along with ability to delete gateways for Horizon Cloud on Microsoft Azure.
  • Support for defining Microsoft Azure resource tags when creating a new dedicated or floating desktop assignment or a new farm for Horizon Cloud on Microsoft Azure.
  • Support for high availability of the Horizon Cloud on Microsoft Azure pod managers utilizing the Microsoft Azure Database for PostgreSQL service. Existing pods can be enabled by editing the pod via the Capacity page.
    • Updated Currently, the pod HA feature is not supported for pods deployed in the following Microsoft Azure cloud environments:
      • Microsoft Azure in China
      • Microsoft Azure Germany
      • Microsoft Azure Government (US Gov Virginia, US Gov Arizona, US Gov Texas)
    • The VMware team is working on adding support for the HA feature for pods in those above listed 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, please contact your VMware representative for assistance.
  • To increase resiliency of the Horizon Agent pairing process for Horizon Cloud on Microsoft Azure, both the automated image import from the Azure Marketplace and the steps for manually building a master VM have changed. The agent status will remain 'Not Paired' until you either convert the VM to an image or reset agent pairing on the VM.

For Current Customers - About this Release

For those of you who have previous experience with Horizon Cloud features and workflows, this section describes what this release's new features and changes might mean to you. The new features related to enhancements of the Horizon Cloud Administration Console are collected at the bottom of the list. For more detailed information, see the Deployment Guide and Administration Guide.

  • Enhanced administrator auditing and logging now available in the Administration Console
    For all pod types, the pod's details page from the Capacity page includes an Audit Logs tab that displays a log of events that administrators have performed on that pod using the Administration Console. For pods in Microsoft Azure, the logged actions include pod deployments, edits, and upgrades; actions related to images, farms, and desktop assignments; changing general settings, and so on. You can download the logs from the console. A logged action is available in the system up to 90 days from the time it was logged.
  • Enhanced monitoring of VM health and associated sessions in real-time.
    Administrators can monitor the health of the VMs and associated sessions in real-time. The Administration Console's Dashboard - Sessions tab provides for viewing session and resource consumption trends, identifying high consuming VMs and poor performing sessions across multiple deployments, plus the ability to focus on a particular pod or VDI desktop assignment. Administrators can navigate to details on consumption and performance-related metrics to gather more actionable details making it easy to identify, categorize and troubleshoot issues with VMs and user sessions.
  • Specifically for cloud-connected Horizon 7 pods:
    • The Horizon 7 Cloud Connector component is used with deployments of Horizon 7.6 and later to activate subscription licenses on Horizon 7 and enable Horizon cloud services for those deployments. Version 1.4 introduces the following new features:
      • Automatic upgrade is now supported on Cloud Connector versions 1.3 and 1.4. See the Deployment Guide on how to enable this auto-upgrade feature. We recommend customers on earlier versions of Cloud Connector to upgrade to the latest to take advantage of this feature.
      • Cloud Monitoring Services (CMS) with session usage details as part of Horizon Cloud Service. For more information, see the Administration Guide.
  • Specifically for pods in Microsoft Azure:
    • The pod architecture has changed in this release. All pods at the September 2019 release's manifest version have a pod Microsoft Azure load balancer and a Microsoft Azure Database for PostgreSQL server instance (Gen 5 Memory optimized tier). This means that before you upgrade your existing pods to this release's manifest version, you must ensure that your existing networking configuration meets the DNS, ports, and protocols required to accommodate the pod Microsoft Azure load balancer and Microsoft Azure Database for PostgreSQL server instance. If you have firewalls or network security groups that block specific ports and protocols, compare your current networking configuration to the information in the following topics and update your networking configuration accordingly.
    • Enhanced alerting for pod upgrade errors that require customer actions to resolve them.
      Some things that are completely within your control can prevent a successful pod upgrade, such as not having enough cores in the pod's associated subscription to create the jump box VM which orchestrates the pod upgrade. Starting in this release, such items are identified in the Administration Console, so that you can address and clear those items.
    • Starting in this release, you can revise the following gateway-related settings on an already deployed pod: add two-factor authentication settings to a gateway that does not have them, edit a gateway's two-factor authentication settings, change the gateway's session brokering timeout setting. In previous releases, you had to configure RADIUS two-factor authentication when the pod was first deployed, and could not change those settings afterwards. Also new in this release, you can delete gateways from an already deployed pod and you can deploy a new pod to have an external gateway without a public IP address on its Azure load balancer and instead have a private IP address on that load balancer.
    • Support for defining Microsoft Azure resource tags when creating a new dedicated or floating VDI desktop assignment or a new farm for Horizon Cloud on Microsoft Azure.
    • High availability is now available. To support high availability for pods in Microsoft Azure, the pod architecture is updated to use the Microsoft Azure Database for PostgreSQL service (Updated Gen 5 Memory optimized tier), a Microsoft Azure load balancer, and an availability set. For a pod that is newly deployed in this release, you have the option to enable high availability for that pod at deployment time, or enable high availability later on. For pods that existed prior to this release, before you can enable those pods for high availability, you must first upgrade them to this release's manifest version and also update the agents in the pods' images, farms, and VDI desktop assignments to this release level. When the pod upgrade and agent updates are completed, then you can enable high availability on the pod by editing the pod from its pod details page in the Administration Console. Note: This new feature brings additional requirements for enabling the Microsoft.SQL service endpoint on the pod's management subnet when your pod uses subnets that you create yourself, and for allowing outbound access for port 5432.

      Updated Currently, this High Availability (HA) feature for pods in Microsoft Azure is only supported for pods deployed in the Microsoft Azure (standard global regions). The pod HA feature is not currently supported for pods deployed in the following Microsoft Azure cloud environments:

      • Microsoft Azure in China
      • Microsoft Azure Germany
      • Microsoft Azure Government (US Gov Virginia, US Gov Arizona, US Gov Texas)
      The VMware team is working on adding support for the HA feature for pods in those above listed 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 HA, please contact your VMware representative for assistance.

      Before upgrading an existing pod in one of the standard Microsoft Azure global regions to this release's manifest and pod architecture that uses the Microsoft Azure Database for PostgreSQL service, you must ensure the following items are in place:

    • To increase resiliency of the Horizon Agent pairing process, this release brings further evolution of moving the DaaS agent functions into the Horizon Agent. The DaaS agent has now been incorporated into the Horizon Agent. Even though both the automated Import Image workflow and manual installation of the Horizon Agents Installer install the DaaS agent's MSI into the guest operating system as they did in previous releases, starting in this release, the DaaS agent is dormant and not used. However, the service for the DaaS agent still appears in the Windows Services list. Do not start that service or unexpected results can occur.
    • Moving the DaaS agent functions into the Horizon View agent has changed both the automated Image Import from the Azure Marketplace workflow and the steps for manually building a master VM. Previously, the master image that resulted from the automated workflow was paired to the cloud at the end of the workflow, while for a manually created image, you had to manually bootstrap and pair the image. Now, for master images in a pod that is new or upgraded to this release version, the resulting master VM is listed on the Imported VMs page with an agent status of Not Paired. To pair the image, you can either:
      • Run the Reset Agent Pairing action on the VM listed on the Imported VMs page, if you want to pair it with the cloud before customizing it.
      • Run the New Image action on the VM directly, if the VM has all of the customizations you want and you are ready to publish it. In this case, the New Image workflow will first run the pairing process to make the agent active, and then you can complete the rest of the fields and click Publish to publish the image.
    • With the move of the DaaS agent functions into the Horizon View agent, the Reset Agent Pairing workflow is now available to use on imported VMs, farm server VMs, and desktop VMs in dedicated VDI desktop assignments. In a farm's details or dedicated VDI desktop assignment's details, if you see an error state in the Agent Status column for a farm server VM or desktop VM, you can use the Reset Agent Pairing action in the Administration Console to repair the pairing state of that VM. (The action is not available for floating VDI desktop assignments.) In the Imported VMs page, you can use the Reset Agent Pairing action to initially pair a VM that has not yet been paired, or repair the pairing state for a VM that was previously paired.
    • The disk encryption feature now uses the newer AzureDiskEncryption v2.2. This newer version enables support of disk encryption for VMs with in-guest proxy set up to talk to the Internet. To take advantage of this new support, update your VMs' agents to version 19.3.0 or later.
    • Updated guidance to use VM models that have a minimum of two (2) CPUs for your farms and VDI desktop assignments. VMware scale testing has shown that for production environments, using a minimum of 2 CPUs avoids unexpected end-user connection issues. Even though the system does not prevent you from choosing a VM model with a single CPU, you should use such VM models for tests or proof-of-concepts only.
    • Usability enhancements to the VM Types and Sizes page.
  • Additional items of note for current customers include:
    • Improved usability and optimization of the Unified Dashboard interactive map view, including more accurate reflection of the pod location and zoom functionality.
    • Enhancements in the reports available in the Administration Console's Reports page. The data in these reports is provided by the Cloud Monitoring Service.
    • For cloud-connected Horizon 7 pods, additional details are displayed in a pod's details page. The pod and Cloud Connector must be at the latest version to see this feature.
    • The product name formerly known as VMware User Environment Manager™ is now named VMware Dynamic Environment Manager™.

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 Administration Console is compatible with recent versions of Google Chrome, Mozilla Firefox, Microsoft Internet Explorer, and Microsoft Edge. Even though you can try using Apple Safari, use of the Administration Console in Apple Safari is not supported in this release.
  • Microsoft Azure Cloud Support: For Microsoft Azure deployments, the service is currently available in the following Microsoft Azure cloud environments:
    • Microsoft Azure (standard global regions)
    • Microsoft Azure in China
    • Microsoft Azure Germany
    • Microsoft Azure Government (US Gov Virginia, US Gov Arizona, US Gov Texas)
  • 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.
    • For RDS images used in farms: Microsoft Windows Server 2012 R2 Datacenter Edition, Microsoft Windows Server 2016 Datacenter Edition, Microsoft Windows Server 2019
    • For VDI images: For the list of supported operating system versions, see the Horizon Cloud Service Windows 10 Support information that is posted in the Documents area of the Horizon Cloud Service community.
  • Supported Horizon Client versions for Microsoft Azure deployments: This release supports the use of the following Horizon Client versions with the desktops and remote applications delivered by the service's Microsoft Azure pods, as listed below. 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/
    • With RDS-based session desktops and remote applications: Horizon Client versions 5.0, 5.1, and 5.2.
    • With VDI desktops: Horizon Client version 5.0, 5.1, 5.2.
    • 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.
  • 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.4 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 7 pods: Horizon 7 Cloud Connector 1.1 is the lowest version level needed to cloud-connect a Horizon 7 pod with Horizon Cloud and see the pod in the Horizon Cloud Administration Console. However, to obtain use of the latest features and fixes for your existing cloud-connected Horizon 7 pods, you should upgrade those pods to the latest versions of the Horizon 7 components, including the latest Horizon 7 Cloud Connector version. If you have the required licensing, you can download the latest Horizon 7 Cloud Connector appliance from http://www.vmware.com/go/download-horizon-subscription

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 Horizon Cloud 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 Administration Console during that time period. If you encounter issues logging in to the Administration 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.
  • 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 using specific ports and protocols. See VMware Horizon Cloud Service Deployment Guide for the connectivity requirements. Note: When you have a proxy configured for the pod, you must use the manual steps to create your base master VMs. You cannot use the automated Import Image wizard when your pod is configured for proxy-based authentication.
  • Subnet sizing: This release does not support expanding the size of the pod's subnets after the pod is deployed. 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, the pod's management subnet is now required to have a minimum of CIDR /27, where previously 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.
    • Desktop (tenant) subnet: Use a CIDR in the range of /24 to /21 to accommodate the VMs for your VDI desktops, the RDS images, and every server in the pod's RDS farms. For example, if you want your production pod to support up to 2,000 VDI desktop VMs, the minimum CIDR that will accommodate that is /21 (2048 IP addresses)

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

  • Before connecting a second Horizon 7 pod to Horizon Cloud, you should log in to the Horizon Cloud Administration Console and complete the Active Directory domain registration process after connecting your first Horizon 7 pod to Horizon Cloud using the Cloud Connector's onboarding process. When you pair multiple Horizon 7 pods with Horizon Cloud before completing that Active Directory domain registration, unexpected results might occur when you eventually log in to the Administration 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.
  • Automatic upgrades of Horizon 7 Cloud Connector are not supported for pods in VMware Cloud on AWS.

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 Administration 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.

Microsoft Azure deployments have the following known limitations.

  • This release does not support expanding the pod's subnets after the node is deployed. 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.
  • 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. The same FQDN can be used in both the external and internal Unified Access Gateway configurations on the same pod.
  • Your authenticated (logged in) session into the Administration Console will time out after the time setting that is configured in the Administration Console's General Settings page. The default is 30 minutes. If you have at least one cloud-connected pod in Microsoft Azure, 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 Administration 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 Administration 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, 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.3 before proceeding with upgrading the Windows operating system.
  • By default, when you use the automated Import Desktop 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 Administration Console might not reflect the data collected between the last retrieval time and the time at which you are viewing the reports in the Administration 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 Administration 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.
  • Updated 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 7.10 are contained in the release notes for that product. Horizon 7.10 documents are linked from the VMware Horizon 7 Documentation page.

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 Administration Console. (2010669)
    Due to this issue, an administrator logged into the Administration 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 Administration 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.

Cloud Connector Related Known Issues

  • When upgrading both Cloud Connector and Connection Server for a pod, make sure to monitor and verify the health of the pod during the upgrade process. Monitoring the pod's health can help with troubleshooting any issues that might arise. (2406549)
    Upgrading the Connection Server on a cloud-connected pod can sometimes result in problems with the health of that pod. If you then try to upgrade Cloud Connector on the unhealthy pod, the upgrade fails.
    Workaround: After upgrading Connection Server, verify that the pod is in good health. To view the pod's health status, first perform an Active Directory domain bind, which allows you to access the Capacity page in the Horizon Cloud Administration Console. On the Capacity page, verify that the pod shows a health status of Online or Ready. 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 Cloud Connector upgrade.

Images, Farms, Assignments Related Known Issues

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

  • Sometimes some desktop VMs out of a large floating VDI desktop assignment report unknown agent status. (2406279)
    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 Administration Console, the Agent Status column for those desktop VMs shows "Unknown" state, with reported agent errors.
    Workaround: In the Administration 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 Desktop 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.

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 VMware Identity Manager, launching a desktop from the Workspace ONE 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 VMware Identity Manager, previously when launching a desktop from the Workspace ONE portal 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 VMware Identity Manager, the two-factor authentication would be configured in VMware Identity Manager and not on the underlying Unified Access Gateway instances.
  • Launching a second desktop from the Workspace ONE portal 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 the Workspace ONE portal 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.

  • Updated When viewing the user card for a user associated with a cloud-connected Horizon 7 pod that does not have an event database configured, an error message appears that says 'Failed to fetch activities for pod'. (2441924)
    When a cloud-connected Horizon pod's Connection Server does not have an event database configured, the system cannot obtain the monitoring data for the user card. As a result, the system displays this message. However, the error message does not describe that the lack of event database is the reason. Also the Horizon Cloud product documentation does not state that the event database is a requirement for the system to obtain the data.
    Workaround: Configure an event database for the pod's Connection Server. For details on how to configure a Connection Server with an event database, see the Horizon 7 Installation Guide's event reporting topics.
  • Even though an administrator logged in to the Administration Console can view reports on the Reports page, exporting the reports fails. (2374653)
    Due to this known issue, when a person has the Customer Helpdesk or Customer Helpdesk Readonly role on their My VMware account in the General Settings page, but their Active Directory account is in a group with the Demo Administrator role on the Roles & Permissions page, having that combination of roles prevents downloading the reports. This issue applies to all types of pods.
    Workaround: Use the General Settings page to delete the person's My VMware account and then add the person back and assign them the Customer Administrator role. You must be a Super Administrator to do this. Their Active Directory account role of Demo Administrator will continue to enforce read-only access to the Administration Console, and they will be able to both view and export reports from the Reports page.
  • 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 Administration 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 Administration 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 Administration 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 Administration 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 Administration 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 Administration 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 Administration 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 Administration Console, clearing the browser cache, restarting the browser, and then logging back into the Administration Console.
  • Application names are displayed in lowercase characters when end users access them using Workspace ONE. (1967245)
    When your Horizon Cloud environment is integrated with VMware Identity Manager, your end users access their assigned desktops and applications using Workspace ONE. 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 VMware Identity Manager 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 Administration 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 Client Related Known Issues

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

  • 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.

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 Administration Console, location names are not localized. (2366913)
    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 Reports and Monitoring Related Known Issues

  • Sessions for VDI host application pools display as "RDSH Application". (2349560)
    For Horizon 7 pods, sessions for users connected to VDI host application pools are shown on the Dashboard page (Monitoring > Dashboard) as "RDSH Application", although these are not RDSH application sessions.
    This issue is resolved in this release. The label is now "VDI Application" for such sessions.

Resolved Updates to Pods in Microsoft Azure Related Known Issues

  • After the download of a new version of the Microsoft Azure pod software is triggered, the Unified Access Gateway status displayed on the node's details page is incorrect. (2036319, HD-15879)
    As described in the Administration Guide, when the download of the pod software update is triggered, the software is downloaded to your environment in Microsoft Azure. Then after the download is finished, your pod's details page shows that an upgrade is available. Due to this known issue, when the download is triggered on the backend, the information about the pod's Unified Access Gateway configurations incorrectly changes to display Pending status in the pod's details page.
    This issue is resolved in this release. The status correctly displays as Deploying instead of Pending.