| VMware Horizon Cloud Service | 25 OCT 2022 Horizon Cloud on Microsoft Azure 2210 Pod Manifest 3821.x | 25 OCT 2022 Horizon Cloud Connector 2.3.x | 20 OCT 2022 Horizon Universal Broker Plugin Installer 22.01 | 10 MAY 2022 Horizon Agents Installer 22.3.x | 25 OCT 2022 Check for additions and updates to these release notes. |
This page describes key release-related information for Horizon Cloud Service - first generation. When you are looking for the Horizon Cloud Service - next-gen Release Notes, visit the page VMware Horizon Cloud Service - next-gen Release Notes.
From this Horizon Cloud Service - first generation page, learn about new features and the enhancements made in each release of the service and its related products. For a list of currently known issues in Horizon Cloud Service - first generation, see Horizon Cloud - Known Issues.
This document is revised periodically as needed with information about the service. Check back regularly for additions and updates to these release notes. The latest versions of the key binaries are listed in this page's most recent monthly section. New versions of each key binary are made available at various times.
Viewing and generating of perpetual keys for VMware foundational products such as vSphere, vSAN, and vCenter now includes support for vSphere 8, vSAN 8, vCenter 8, and VMware Workstation 16 Pro for Linux and Windows.
A known issue about Horizon Cloud Connector is added to the Horizon Cloud - Known Issues page. For additional details and steps to remediate, see KB 90505.
VMware Horizon Cloud Service on Microsoft Azure 2210 | pod manifest 3821.x | VMware Horizon Cloud Connector 2.3.x | VMware Horizon Universal Broker Plugin Installer 22.01 | VMware Horizon Agents Installer (HAI) 22.3.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3821.x. Running the Import VM wizard in a pod of 3821.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3821.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
In addition to the release of Horizon Cloud Connector 2.3.x, below are this update's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact horizoncloudservice@vmware.com. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the October 2022 section of the documentation topic About the Latest Horizon Cloud Release.
For Horizon Cloud on Microsoft Azure deployments, administrators can now choose to have the Unified Access Gateway instances inherit NTP settings from the pod configuration.
For Horizon deployments starting with Horizon 8 2209, depending on how you want your golden image to be managed, you can change the golden image and snapshot source in your pools from vCenter to Image Catalog or the reverse. To leverage this new feature, use the VMware Horizon Console operations for editing existing pools and farms and instant clone maintenance to change the relevant source entity. See the Horizon 8 2209 documentation set at the following locations Creating and Managing Automated Full-Clone Desktop Pools, Patching an Instant-Clone Pool, Schedule Maintenance for an Automated Instant-Clone Farm in Horizon.
VMware Horizon Cloud Service on Microsoft Azure 2207 | pod manifest 3622.x | VMware Horizon Cloud Connector 2.2.x | VMware Horizon Universal Broker Plugin Installer 22.01 | VMware Horizon Agents Installer (HAI) 22.2.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3622.x. Running the Import VM wizard in a pod of 3622.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3622.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Notes:
To avoid effects from Microsoft Azure Cloud's upcoming retirement of some VM models and make it easier to import GPU-capable VMs, some of the default VM models used by the automated Import VM from Marketplace wizard have changed. For the list of the VM models used by the wizard, see the updated Golden Images section in Microsoft Azure Virtual Machine Requirements for a Horizon Cloud Pod in Microsoft Azure. Before using the automated wizard, please verify the VM family quotas in your pods' Azure subscriptions can accomodate the new defaults.
The transient pod deployment engine, also known as the jump box, is removed from the architecture for new Horizon Cloud on Microsoft Azure deployments and updates. Capacity for a transient jump box would be required only if you open a support request and VMware Support determines the way to service that request is to deploy a support-related jump box VM, under their supervision.
If your existing Horizon Cloud on Microsoft Azure deployments use custom roles for the subscription's service principal (atypical case, usually the Contributor role is used), then before upgrading to this release's manifest, you might need to add these following two permissions to those custom roles prior to starting the upgrade process. An enhancement that makes the upgrade process run faster requires these permissions.
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/read
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/writeBelow are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact horizoncloudservice@vmware.com. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the August 2022 section of the documentation topic About the Latest Horizon Cloud Release.
Horizon customers with deployments on VMware Cloud on AWS can now replicate images using the Multi-Pod Images capabilities.
Administrators can now configure the cipher suites that will be accepted when clients connect to the Unified Access Gateway machines.
During upgrade maintenance, Unified Access Gateway session counts will be used to optimize timing to reduce end-user session interruptions.
Because every subscription includes a Workspace ONE Access tenant which can be added using the Horizon Universal Console, the capability of new Workspace ONE Access tenant creation from within the Horizon Universal Console is removed.
Starting today, the URL for the original Horizon Cloud Service Documentation page at https://docs.vmware.com/en/VMware-Horizon-Cloud-Service/index.html is redirected to the new unified Horizon Documentation page at https://docs.vmware.com/en/VMware-Horizon/index.html. The new unified Horizon Documentation page brings together the documentation for all of the Horizon-related product lines, such as Horizon Connection Server, Horizon Clients, and Horizon Cloud Service. A video on the new unified page describes the changes. Scroll through the left hand navigation of the new unified page to locate the Horizon Cloud Service documents.
Note: If you do not automatically see the new unified Horizon Documentation page with its embedded video, please clear your browser cache or try using an incognito or private browser window.
The URLs for the individual Horizon Cloud Service documents, such as the Release Notes and guides, remain their original URLs.
Logging into the Horizon Universal Console has an updated user experience. This new flow incorporates the VMware standard authentication with VMware Cloud Services. Your login experience might look differently when you take the first login step at the console address, cloud.horizon.vmware.com. The change has no effect on your existing credentials. Log in using the same credentials that you have been using to log in to the console. If you experience an issue when opening cloud.horizon.vmware.com in your browser, try clearing the browser cache or using an incognito or private browser window and re-loading the URL.
A required DNS name is added to the set of required DNS names (host names) for Horizon Cloud on Microsoft Azure deployments. The purpose is for VMware system monitoring.
| Subnet Source |
Destination |
Ports/Protocol |
|---|---|---|
| Management subnet - pod manager VMs, Unified Access Gateway VMs, gateway connector VM, Horizon Edge Virtual Appliance |
If your firewall or network security group (NSG) supports the use of service tags, apply Azure service tag AzureCloud. If your firewall or NSG does not support the use of service tags, use the host name monitor.horizon.vmware.com |
1514 and 1515 / TCP |
In the upcoming week, a new authentication flow will be enabled for logging into the Horizon Universal Console. This new flow incorporates the VMware standard authentication with VMware Cloud Services. The change will have no effect on your existing credentials. As a result of this change, your login experience might look differently when you take the first login step at the console address, cloud.horizon.vmware.com.
VMware Horizon Cloud Service on Microsoft Azure 2204 | pod manifest 3498.x | VMware Horizon Cloud Connector 2.2.x | VMware Horizon Universal Broker Plugin Installer 22.01 | VMware Horizon Agents Installer (HAI) 22.1.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3498.x. Running the Import VM wizard in a pod of 3498.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3498.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Notes:
If your existing Horizon Cloud on Microsoft Azure deployments use custom roles for the subscription's service principal (atypical case, usually the Contributor role is used), then before upgrading to this release's manifest, you might need to add these following two permissions to those custom roles prior to starting the upgrade process. An enhancement that makes the upgrade process run faster requires these permissions.
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/read
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/writeTo avoid effects from a Microsoft Azure hypervisor issue (KB 88343), some of the default VM models used by the automated Import VM from Marketplace wizard have changed. For the list of the VM models used by the wizard, see the updated Golden Images sections in Microsoft Azure Virtual Machine Requirements for a Horizon Cloud Pod in Microsoft Azure. Before using the automated wizard, please verify the VM family quotas in your pods' Azure subscriptions can accomodate the new defaults.
In support of our commitment to accessibility, we have updated a number of pages in the Deployment Guide, Administration Guide, and Managing Images from the Cloud Guide to add ALT text to all images. Due to this activity, the "Updated on" date that appears at the tops of the HTML pages will reflect the date of those ALT text updates, even when the page's visible text content is unchanged for this release.
Below are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact horizoncloudservice@vmware.com. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the May 2022 section of the documentation topic About the Latest Horizon Cloud Release.
Windows 11 guest OS is supported with some requirements and limitations. (Learn more)
New Horizon Cloud on Microsoft Azure pods will always be deployed with High Availability.
Multi-pod images will now leverage configured proxy settings for any image operation originating from the customer network to the internet (such as importing image from the Azure Marketplace).
Administrators can import VMs with AMD GPU and graphics drivers for use as images.
In existing dedicated assignments, you can now adjust a provisioned VM's workload CPU, memory, or disk based on individual user needs. When you do this, the pool type will change to Mixed type.
The recommended Horizon Agents Installer version is now displayed on the Capacity screen. Regular notifications will be generated to remind admins to keep agents up to date.
Azure VMs that enter a Stopped state due to a guest OS shutdown will now automatically be transitioned to a Deallocated state to prevent continued billing.
Applications can now be delivered on-demand when a user clicks to launch the application from the desktop and Start menu just as if the application was already installed natively on the Windows machine. The setting is available for newly created packages. The admin has an option to select on-demand for this new type of delivery or select classic to have the user and computer assigned applications delivered at login and start-up as they have in the past.
VMware Horizon Cloud Service on Microsoft Azure 2203 | pod manifest 3328.x | VMware Horizon Cloud Connector 2.1.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.3.x | Unless otherwise noted in the documentation, this HAI version is built into this pod manifest and running the Import VM wizard in the pod will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of that manifest. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Note: When downloading the latest binaries for the Horizon Cloud Connector and Horizon Universal Broker Plugin Installer from VMware Customer Connect, in the list of Product Downloads, look for the December 2021 release date. The versions of those binaries are located in the downloads pages with that date. For the latest HAI from the list of Product Downloads, look for the binary under the Horizon Cloud Service on Microsoft Azure November 2021 release date.
No feature highlights have been provided for this release. If any questions, please contact horizoncloudservice@vmware.com.
If you are a current customer that has existing cloud-connected pods prior to this date, please refer to release information in the March 2022 section of the documentation topic About the Latest Horizon Cloud Release.
Note: If your existing Horizon Cloud on Microsoft Azure deployments use custom roles for the subscription's service principal (atypical case, usually the Contributor role is used), then before upgrading to this release's manifest, you might need to add these following two permissions to those custom roles prior to starting the upgrade process, if they are not already set in the custom roles. An enhancement that makes the upgrade process run faster requires these permissions.
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/read
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/writeVMware Horizon Cloud Service on Microsoft Azure 2201 | pod manifest 3254.x | VMware Horizon Cloud Connector 2.1.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.3.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3254.x. Running the Import VM wizard in a pod of 3254.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3254.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Note: When downloading the latest binaries for the Horizon Cloud Connector and Horizon Universal Broker Plugin Installer from VMware Customer Connect, in the list of Product Downloads, look for the December 2021 release date. The versions of those binaries are located in the downloads pages with that date. For the latest HAI from the list of Product Downloads, look for the binary under the Horizon Cloud Service on Microsoft Azure November 2021 release date.
Note: If your existing Horizon Cloud on Microsoft Azure deployments use custom roles for the subscription's service principal (atypical case, usually the Contributor role is used), then before upgrading to this release's manifest, you might need to add these following two permissions to those custom roles prior to starting the upgrade process. An enhancement that makes the upgrade process run faster requires these permissions.
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/read
Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/writeBelow are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact horizoncloudservice@vmware.com. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the February 2022 section of the documentation topic About the Latest Horizon Cloud Release.
LDAPS can now be selected as the protocol when registering Active Directory. This feature is available when your tenant is explicitly enabled for it and the pods are on this release's manifest level. To request enablement, you must file a support request as described in VMware KB article 2006985.
Dynamic Environment Manager can now distinguish between internal and external users when connecting through Universal Broker.
Session data for users connecting through Universal Broker will now show breakdown of logon segments.
A notice will now be shown in the Horizon Universal Console to the administrator if the Unified Access Gateway is upgraded and there may be a need to update the configuration for RADIUS to address changes to the IP addresses.
When using Image Management Service (IMS) with Horizon pods, you can now select which pods the multi-pod images are copied to.
Windows Server 2019 is now a supported OS for Horizon pods.
A critical vulnerability in Apache Log4j identified by CVE-2021-44228 has been addressed in this version. Review VMSA-2021-0028 for more details.
VMware Horizon Cloud Service on Microsoft Azure 2111 | pod manifest 3139.x | VMware Horizon Cloud Connector 2.1.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.3.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3139.x. Running the Import VM wizard in a pod of 3139.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3139.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Below are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact horizoncloudservice@vmware.com. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the November 2021 section of the documentation topic About the Latest Horizon Cloud Release.
For existing provisioned VDI VMs, administrators can now adjust the VM type as needed (to supported alternate VM specifications).
Administrators can move individual VMs between assignments in the same pod. This feature is enabled for tenants by request.
For greenfield deployments of Horizon Cloud on Microsoft Azure, Universal Broker is enabled as the default.
Horizon Agent Update for Horizon Cloud pods on Microsoft Azure now supports remediating incomplete or failed agent updates in cases where the agent is stopped.
Administrators can now specify non-admin email addresses for receiving service alerts and notifications.
Multi-pod image management now supports use of multi-session Windows OSes with farms for Horizon Cloud pods on Microsoft Azure.
In Horizon on VMware Cloud on AWS, administrators can configure App Volume content replication between two or more VMware Cloud on AWS instances. Horizon Universal License is required. This feature is available as a beta preview.
If your Horizon Universal License includes SDDC components such as VMware vCenter, vSAN, and vSphere, you can retrieve these keys using the Horizon Universal Console.
App Volumes now supports Dynamic Environment Manager with Windows 10 multi-session OS.
App packages will now be automatically detached as the last assigned user of that app logs off a Windows 10 multi-session system.
VMware Horizon Cloud Service on Microsoft Azure 2110 | pod manifest 3000.x | VMware Horizon Cloud Connector 2.0.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.2.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3000.x. Running the Import VM wizard in a pod of 3000.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3000.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Note: When downloading the latest binaries for the Horizon Cloud Connector, Horizon Universal Broker Plugin Installer, and HAI from VMware Customer Connect, look for the July 15, 2021 release date. The versions of the relevant binaries are located in the downloads pages with that date.
Below are this release's highlights provided by the Product Management Team. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the October 2021 section of the documentation topic About the Latest Horizon Cloud Release.
Horizon Universal Console now supports narrow scope permissions to desktop assignments and farms for the built-in predefined roles.
Administrators can now select to use either 8443 or 443 as the TCP port for Blast Extreme on the Unified Access Gateways which are deployed as part of the Horizon Cloud pod on Microsoft Azure.
Universal Broker now supports the ability to restrict the launching of virtual desktops, published desktops, and published applications to specific clients and versions and provide warning messages to clients.
Universal Broker and multi-cloud assignments now support brokering of desktops and apps on Google Cloud VMware Engine.
Universal Broker now supports the ability for end users to connect to their VDI desktops and published desktops using the RDP protocol from within the Horizon Client.
Horizon Cloud Connector adds support for Google Cloud VMware Engine and Amazon Elastic Compute Cloud (EC2), enabling customers to deploy Horizon Enterprise with a federated architecture on these cloud platforms.
VMware Horizon Cloud Service on Microsoft Azure 2109 | pod manifest 3000.x | VMware Horizon Cloud Connector 2.0.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.2.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 3000.x. Running the Import VM wizard in a pod of 3000.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 3000.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Note: When downloading the latest binaries for the Horizon Cloud Connector, Horizon Universal Broker Plugin Installer, and HAI from VMware Customer Connect, look for the July 15, 2021 release date. The versions of the relevant binaries are located in the downloads pages with that date.
Below are this release's highlights provided by the Product Management Team. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the September 2021 section of the documentation topic About the Latest Horizon Cloud Release.
Horizon Agent Update for Horizon Cloud pods on Microsoft Azure now supports targeting agent updates on the individual desktops within the assignment.
A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for performance and reliability.
VMware Horizon Cloud Service on Microsoft Azure 2108 | pod manifest 2955.x | VMware Horizon Cloud Connector 2.0.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.2.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 2955.x. Running the Import VM wizard in a pod of 2955.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 2955.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Note: When downloading the latest binaries for the Horizon Cloud Connector, Horizon Universal Broker Plugin Installer, and HAI from VMware Customer Connect, look for the July 15, 2021 release date. The versions of the relevant binaries are located in the downloads pages with that date.
Below are this release's highlights. If you are a current customer that has existing cloud-connected pods prior to this date, additional details August 2021 section of the documentation topic About the Latest Horizon Cloud Release.
Integration with the VMware Workspace ONE® Assist for Horizon® product enables Horizon Cloud administrators to launch remote support sessions directly from the Help Desk Tool from the Horizon Universal Console. With this feature, administrators can assist employees with virtual desktop sessions and issues, with remote view and control capabilities. Because Workspace ONE Assist for Horizon is part of the VMware Workspace ONE UEM product line, the documentation about Workspace ONE Assist for Horizon can be found within the document titled Workspace ONE Assist for Horizon and Horizon Cloud located within the set of Workspace ONE UEM Product Documentation.
For Horizon Cloud pods in Microsoft Azure, a change related to the set of operations that the service principal should be allowed to perform. Two additional operations are added to the set of operations that the service principal needs to use in your subscription, as described in Operations Required by Horizon Cloud in Your Microsoft Azure Subscriptions. These two additional operations are to support an upcoming feature by which the service can reduce the time it takes for a new pod deployment and for a pod upgrade by using pre-configured images in the Microsoft Azure Marketplace. When your service principal uses a custom role, that role will need the ability to perform these two additional operations.
A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for performance and reliability.
Use of the Image Management Service (IMS) with Horizon pods deployed in VMware Cloud on AWS is not yet supported. This release notes page and the Managing Images from the Cloud guide will be updated when support for that use case becomes available.
VMware Horizon Cloud Service on Microsoft Azure 2106 | pod manifest 2915.x | VMware Horizon Cloud Connector 2.0.x | VMware Horizon Universal Broker Plugin Installer 21.06 | VMware Horizon Agents Installer (HAI) 21.2.0 | Unless otherwise noted in the documentation, this HAI version is built into manifest 2915.x. Running the Import VM wizard in a pod of 2915.x will install the agents from this HAI version. This HAI version is also supported for manual installation for imported VMs in pods of manifest 2915.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.
Note: When downloading the latest binaries for the Horizon Cloud Connector, Horizon Universal Broker Plugin Installer, and HAI from VMware Customer Connect, look for the July 15, 2021 release date. The versions of the relevant binaries are located in the downloads pages with that date.
If you are a current customer that has existing cloud-connected pods prior to this date, additional detail is provided in the July 2021 section of the documentation topic About the Latest Horizon Cloud Release.
Multi-pod image management provides an easy method for publishing and replicating single-session VDI images to two or more Horizon Cloud pods in Microsoft Azure and for updating multiple assignments with a single operation. This feature is only available to tenants using multi-cloud assignments. Documentation about this feature can be found in Managing Horizon Images From the Cloud.
Horizon Cloud Connector 2.0 adds service-level fault tolerance for the license service. Documentation about this feature is linked from the July 2021 section in the Deployment Guide topic About the Latest Horizon Cloud Release.
Horizon Cloud Connector 2.0 adds support for SNMP. Administrators can use a standards-based monitoring function to proactively monitor and receive alerts on critical connector-related services, such as licensing, upgrade, and connector life cycle, even if they are not logged into the Horizon Universal Console. Documentation about this feature is linked from the July 2021 section in the Deployment Guide topic About the Latest Horizon Cloud Release.
A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for supportability and reliability.
The release notes sections for releases prior to July 2021 are deprecated. To allow you sufficient time for updating existing links or bookmarks, the deprecated information will be located at this URL for a period of time.
