First-Gen Omnissa Horizon Cloud Release Notes

Horizon Cloud - first-gen | 22 MAY 2025

Horizon Cloud on Microsoft Azure 2501 Pod Manifest 5041.1 | 22 MAY 2025

Horizon Cloud Connector 2.5.x | 21 MAY 2025

Horizon Universal Broker Plugin Installer 24.12 | 21 MAY 2025

Horizon Agents Installer 25.1.x | 30 APR 2025

Check for additions and updates to these release notes.

Regional Control Plane Instance Shutdown

Beginning on June 28, 2025, Omnissa is initiating a controlled, region-by-region decommissioning of the First-Gen platform. Customers in each region must migrate to the Horizon Cloud platform and fully shut down the First-Gen infrastructure to avoid service disruption. See KB 6000900 for details about the shutdown and required migration.

What's in the Release Notes

This page describes key release-related information for Horizon Cloud - first generation for existing customers in the first-generation Horizon Cloud control plane.

New customers should onboard to Horizon Cloud.

When you are an existing customer in the first-gen Horizon Cloud control plane, use this page to learn about changes made in each release of the service and its related products. For a list of currently known issues in the first-generation service, see First-Gen 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.

Important: For Horizon Cloud on Microsoft Azure deployments starting from release v2303 and pod manifest 4136.x, the weaker Kerberos encryption Etypes DES and RC4-HMAC (16 and 23) are unsupported.

If you are still using those weaker Etypes for the Active Directory domains that you have registered with your tenant for use with the Horizon Cloud on Microsoft Azure deployments, then after you upgrade your existing deployments to manifest 4136.x or doing brand new deployments, issues related to Horizon Cloud Active Directory workflows will occur.

To avoid issues, update the encryption types used in your Active Directory domains to avoid using those weaker encryption ETypes. Refer to the Microsoft article KB5021131: How to manage the Kerberos protocol changes related to CVE-2022-37966

Important Service Changes

As stated in the box above, on August 27, 2024 we transitioned to new URL endpoints which are required for the operation of the service. These changes are also described in KB 6000056.

For Horizon Cloud Connector Deployments:

For all instances of the pre-Omnissa counterpart to *.horizon.omnissa.com (such as *.horizon.<name>.com) that you currently include in allow lists, also include *.horizon.omnissa.com itself.
For all instances of the pre-Omnissa counterpart to *connector-azure-*.omnissahorizon.com (such as *connector-azure-*.<name>horizon.com) that you currently include in allow lists, also include *connector-azure-*.omnissahorizon.com itself.

The above guidance is also documented in page First-Gen Tenants - DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod

For Horizon Cloud on Microsoft Azure Deployments:

For all instances of the pre-Omnissa counterpart to *.horizon.omnissa.com (such as *.horizon.<name>.com) that you currently include in allow lists, also include *.horizon.omnissa.com itself.
For all instances of the pre-Omnissa counterpart to softwareupdate.omnissa.com (such as softwareupdate.<name>.com) that you currently include in allow lists, also include softwareupdate.omnissa.com itself.
For all instances of the pre-Omnissa counterpart to sauron*.horizon.omnissa.com (such as sauron*.horizon.<name>.com) that you currently include in allow lists, also include sauron*.horizon.omnissa.com itself.
For all instances of the pre-Omnissa counterpart to api.artemis.omnissa.com (such as scapi.<name>.com) that you currently include in allow lists, also include api.artemis.omnissa.com itself.

The above guidance is also documented in page First-Gen Tenants - Horizon Cloud on Microsoft Azure Deployments - Host Name Resolution Requirements, DNS Names

May 22, 2025 Update (v2501, v2.5.x, v24.12, v25.1.x)

Omnissa Horizon Cloud on Microsoft Azure 2501 | pod manifest 5041.1 | Omnissa Horizon Cloud Connector 2.5.x | Horizon Universal Broker Plugin Installer 24.12 | Horizon Agents Installer (HAI) 25.1.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 5041.1. Running the Import VM wizard in a pod of 5041.1 will install the agents from this HAI version. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.

Note: Horizon Cloud Connector version 2.4.x and earlier and Universal Broker Plugin version 22.01 and earlier are no longer generally available for download. To obtain those binaries, customers with active support agreements can contact Omnissa Support.

Below are this release's highlights.

A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes support for Omnissa branding.
This pod manifest enables upgrade to Azure PostgreSQL Flexible Server for Horizon Cloud pods in Microsoft Azure. This upgrade is critical to customers who will not complete migration to Horizon Cloud by March 28, 2025. For more details, refer to KB article 6000765.
A new Horizon Agents Installer (HAI) version that is compatible with this release's pod manifest.

Important
If your organization uses Cloud Monitoring Service (CMS) today for dashboards and reports, Omnissa recommends remaining on your current version of Horizon Agent and not upgrade to HAI version 24.4.x or later versions. Upgrading to versions 24.4.x or later will remove the Horizon telemetry from your Workspace ONE Intelligence dashboards and reports. As you migrate your deployments to Horizon Cloud, you must upgrade to HAI 24.4.x and later. For more information, refer to KB article 6000673.

May 21, 2025 Update - Horizon Cloud Connector 2.5, Horizon Universal Broker Plugin Installer 24.12

This update is specifically for:

Release of a new build of Horizon Cloud Connector 2.5.0 (horizon-cloud-connector-2.5.0.0-20052025.ova).
Release of Horizon Universal Broker Plugin Installer 24.12.

New Horizon Cloud Connector 2.5 build

Because an issue was identified in the build previously released on April 25, the build is replaced in Omnissa Customer Connect. The issue caused the OVA installation to fail due to missing libraries that were not packaged with the OVA. The replacement build corrects this issue.

If you downloaded the earlier OVA, please replace it with the updated version horizon-cloud-connector-2.5.0.0-20052025.ova to ensure a successful installation.

Horizon Universal Broker Plugin Installer 24.12

This 24.12 version is compatible with Horizon Connection Server 2412 or later.
You only have to upgrade to this version 24.12 when you upgrade your Horizon Connection Server to version 2412 or later. When running Horizon Connection Server of versions earlier than version 2412, your existing compatible Horizon Universal Broker Plugin of version earlier than 24.12 will continue to work.
When you upgrade your Horizon Connection Server to version 2412 or later, you must adhere to this sequence on the Horizon Connection Server for installing Horizon Universal Broker Plugin 24.12 or later:
1. Uninstall the existing installed Horizon Universal Broker Plugin.
2. Upgrade the Horizon Connection Server to 2412 or later.
3. Then install the latest Horizon Universal Broker Plugin (version 24.12 or later).

April 25, 2025 Update - Horizon Cloud Connector 2.5

This update is specifically for Horizon Cloud Connector 2.5 release. Below are the Horizon Cloud Connector 2.5 release's highlights.

The operating system of the Horizon Cloud Connector has changed from Photon OS to Alma Linux OS.
Enabled new Omnissa URL endpoints as described in KB 6000056.

Notes:

The Horizon Cloud Connector’s key box service is sunset. In Horizon Cloud Connector 2.5, the key box service is inactive.
The Connection Server Monitoring Service (CSMS) is sunset. In Horizon Cloud Connector 2.5, the CSMS service is inactive.
The auto-upgrade feature is unsupported for upgrading to Horizon Cloud Connector 2.5. Now you need to perform the manual upgrade.
We no longer support deploying the Horizon Cloud Connector on platforms other than vSphere. For deployments on other platforms, migrate to Horizon Cloud and deploy the Horizon Edge Gateway to maintain compatibility and feature support.
Prior versions of Horizon Cloud Connector are no longer supported.

January 2025 Update

The Horizon Cloud Connector configuration portal UI is rebranded with Omnissa branding. To see the latest Horizon Cloud Connector configuration portal UI in your browser, clear the browser cache and re-load the configuration portal in your browser.

September 17, 2024 Update (v2408, v2.4.1, v22.01, v24.2.x)

Omnissa Horizon Cloud on Microsoft Azure 2408 | pod manifest 5041.0 | Omnissa Horizon Cloud Connector 2.4.x | Horizon Universal Broker Plugin Installer 22.01 | Horizon Agents Installer (HAI) 24.2.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 5041.0. Running the Import VM wizard in a pod of 5041.0 will install the agents from this HAI version. 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 above binary versions for the Horizon Cloud Connector and Horizon Universal Broker Plugin Installer from Customer Connect, look for the January 2024 release date. The latest versions of the relevant binaries are located in the downloads pages with that date.

Below are this release's highlights.

The pod managers now support Azure PostgreSQL Flexible Server. This support is available via an upgrade to the latest version of the pod managers. This upgrade is being made available to customers who will not complete migration to Horizon Cloud by the End of Life date of Horizon Cloud first-gen by January 31, 2025.

May 30, 2024 Update

The first-gen documentation is updated according to the items described in the preceding Important Service Changes section.

May 6, 2024 Update

The end-user computing (EUC) division is transitioning from pre-Omnissa-hosted systems to Omnissa EUC-hosted systems, which affects product interfaces, links, and documentation, for example:

If you were previously using Workspace ONE Cloud Admin Hub to access the Horizon Universal Console, then the access URL has been updated to https://connect.omnissa.com. Please update your bookmarks or saved links accordingly. Also see the Required Actions below because, depending on how you authenticate to the Horizon Universal Console, you might have to perform an action in order to log in to the service.
If you were using a pre-Omnissa address to access the Horizon Universal Console, you can continue to use that address until we notify you otherwise. Also see the Required Actions below because, depending on how you authenticate to the Horizon Universal Console, you might have to perform an action in order to log in to the service.

Required Actions

If your access previously used Enterprise Federation with pre-Omnissa cloud services, no changes are required to access your service using connect.omnissa.com or the pre-Omnissa URL.
If you previously used a pre-Omnissa ID to access pre-Omnissa cloud services, you must first update your password by resetting it. Your previous password will no longer work. To reset your password for this purpose:

In your browser, navigate to https://connect.omnissa.com
Type in your email (ID) and click Next to the screen which asks for your password.
Click the Forgot Password link (instead of typing your existing password). (This step ensures that after you complete the reset password flow, you'll be able to continue accessing your services without issues.) The Forgot Password UI will be displayed.
In the Forgot Password UI, enter your registered email and click the Send Authentication Code button to receive the code.
Check your email account for the email with the authentication code and use it in the Forgot Password UI.
Follow the on-screen prompts to enter a new password.
After the new password is established, the UI changes to display your Cloud Services, and you can navigate to the Horizon Cloud tile within your services.

After your password is reset using the above steps, if you were using pre-Omnissa URL to access the Horizon Universal Console, you can continue with that method.

Note: If you use the same ID to log in to Customer Connect and Cloud Services, you only need to reset your password once.

For details regarding Omnissa Customer Connect, https://customerconnect.omnissa.com, see KB article 97841.
For first-gen Horizon Cloud, in the Horizon Universal Console, generating and viewing the license keys for both pre-Omnissa foundational products and Omnissa products that were previously available through the View Perpetual Keys functionality is temporarily deactivated. If you need assistance with obtaining your license keys, please see the guidance in KB article 6000014.
The previously displayed in-product feedback icon is not available in the first-gen Horizon Universal Console.

April 18, 2024 Update (v2404, v2.4.1, v22.01, v23.4.1)

Omnissa Horizon Cloud on Microsoft Azure 2404 | pod manifest 5021.x | Omnissa Horizon Cloud Connector 2.4.x | Horizon Universal Broker Plugin Installer 22.01 | Horizon Agents Installer (HAI) 23.4.1 | Unless otherwise noted in the documentation, this HAI version is built into manifest 5021.x. Running the Import VM wizard in a pod of 5021.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 5021.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.

A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for performance and reliability.
A new Horizon Agents Installer (HAI) version that is compatible with this release's pod manifest.

January 9, 2024 Update

Important:

The latest version of Horizon Cloud Connector available in Customer Connect addresses a critical update to Apache Struts identified in Apache Struts Security Bulletin S2-066, for CVE-2023-50164. We recommend you upgrade to this latest version. In Customer Connect, look for the January 2024 release date.

November 16, 2023 Update (v2310, v2.4.x, v22.01, v23.3)

Omnissa Horizon Cloud on Microsoft Azure 2310 | pod manifest 4361.x | Omnissa Horizon Cloud Connector 2.4.x | Horizon Universal Broker Plugin Installer 22.01 | Horizon Agents Installer (HAI) 23.3.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 4361.x. Running the Import VM wizard in a pod of 4361.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 4361.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 above binary versions for the Horizon Cloud Connector and Horizon Universal Broker Plugin Installer from Customer Connect, look for the January 9, 2024 release date. The latest 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 any questions about these highlight bullets, contact your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the November 2023 section of the documentation topic About the Latest Horizon Cloud Release

A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for performance and reliability.

November 2, 2023 Update

The first-gen Horizon Universal Console is updated in alignment with the items described in KB article 92424 that are related to the end of availability (EOA) of the first-gen control plane. The first-gen Horizon Cloud documentation about pod deployments is also updated in alignment.
The first-gen Horizon Cloud documentation is updated in alignment with KB article 93762.

July 3, 2023 Update

As described in KB article 91183, starting on June 30, 2023, the historical dashboards and reports which were powered by the Cloud Monitoring Service (CMS) are only available through Omnissa Intelligence. See the KB article for details and the steps to take to configure the integration of your first-generation Horizon Cloud tenant with Omnissa Intelligence.

The First-Gen Horizon Cloud Administration Guide pages related to this update are now updated to match the resulting changes in the first-gen Horizon Universal Console.

May 4, 2023 Update (v2303, v2.4.x, v22.01, v23.1)

Omnissa Horizon Cloud on Microsoft Azure 2303 | pod manifest 4136.x | Omnissa Horizon Cloud Connector 2.4.x | Horizon Universal Broker Plugin Installer 22.01 | Horizon Agents Installer (HAI) 23.1.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 4136.x. Running the Import VM wizard in a pod of 4136.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 4136.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 above binary versions for the Horizon Cloud Connector and Horizon Universal Broker Plugin Installer from Customer Connect, look for the May 4, 2023 release date. The versions of the relevant binaries are located in the downloads pages with that date.

Note: This May update adds the release of Horizon Cloud Connector 2.4.x to the previously released Horizon Cloud on Microsoft Azure 2303 pod manifest and HAI versions. The content of the April 2023 section is included here for convenience in having it all together in this section.

Important:

For Horizon Cloud on Microsoft Azure deployments starting from release v2303 and pod manifest 4136.x, the weaker Kerberos encryption Etypes DES and RC4-HMAC (16 and 23) are unsupported.

Below are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the May 2023 and April 2023 sections of the documentation topic About the Latest Horizon Cloud Release

Administrators can now change the Connection Server credentials configured in the Horizon Cloud Connector when Active Directory is registered.
Administrators can now configure a certificate in the Horizon Cloud Connector to allow a connection to the Horizon Cloud control plane when SSL offloading is configured for outbound traffic.
Administrators will now receive a notification when the Horizon Cloud Connector's internal Kubernetes certificate is approaching its expiration date. Administrators can choose to renew the certificate ahead of time. If the renewal is not executed ahead of time then the renewal will proceed automatically prior to expiration to prevent service interruption.
In April 2023 release: A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for performance and reliability.
In April 2023 release: The operating system of the pod managers has been updated to Ubuntu 20.04 as of manifest 4136.
In April 2023 release: Guest OS support added for the following Windows flavors:
- Windows 10 Enterprise, 22H2
- Windows 10 Enterprise Multi-session, 22H2
- Windows 11 Enterprise, 22H2
- Windows 11 Enterprise Multi-session, 22H2
- Windows Server 2022 Data Center

April 27, 2023 (v2303, v2.3.x, v22.01, v23.1)

Omnissa Horizon Cloud on Microsoft Azure 2303 | pod manifest 4136.x | Omnissa Horizon Cloud Connector 2.3.x | Horizon Universal Broker Plugin Installer 22.01 | Horizon Agents Installer (HAI) 23.1.x | Unless otherwise noted in the documentation, this HAI version is built into manifest 4136.x. Running the Import VM wizard in a pod of 4136.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 4136.x. For pods at earlier manifests, the Import VM from Marketplace wizard uses the HAI version that was built into their respective pod manifests.

Important:

For Horizon Cloud on Microsoft Azure deployments starting from release v2303 and pod manifest 4136.x, the weaker Kerberos encryption Etypes DES and RC4-HMAC (16 and 23) are unsupported.

Note: When downloading the latest binaries for the Horizon Cloud Connector and Horizon Universal Broker Plugin Installer from Customer Connect, look for the October 20, 2022 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 any questions about these highlight bullets, contact your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. If you are a current customer that has existing cloud-connected pods prior to this date, additional release items are described in the April 2023 section of the documentation topic About the Latest Horizon Cloud Release

A new pod manifest version for Horizon Cloud pods in Microsoft Azure includes platform code improvements for performance and reliability.
The operating system of the pod managers has been updated to Ubuntu 20.04 as of manifest 4136.
Guest OS support added for the following Windows flavors:
- Windows 10 Enterprise, 22H2
- Windows 10 Enterprise Multi-session, 22H2
- Windows 11 Enterprise, 22H2
- Windows 11 Enterprise Multi-session, 22H2
- Windows Server 2022 Data Center

March 9, 2023 Update

The guide entitled Self-Service Migration of First-Generation Horizon Cloud on Microsoft Azure Deployments to Horizon Cloud is now available.

February 21, 2023

The February 15, 2023 documentation issue is resolved. The Proxy Traffic column in the page titled Horizon Cloud on Microsoft Azure Deployments - Host Name Resolution Requirements, DNS Names is updated with up-to-date data.

February 15, 2023

New documentation issue: Even though a Proxy Traffic column is now added to the DNS Requirements table in the page titled Horizon Cloud on Microsoft Azure Deployments - Host Name Resolution Requirements, DNS Names, some of the rows for that Proxy Traffic column contain inaccurate data. This issue will be fixed in an upcoming documentation revision.

February 8, 2023 Update

A new menu option is added to the Horizon Universal Console to support the features of the upcoming self-service migration of Horizon Cloud on Microsoft Azure deployments to Horizon Cloud ( Pairing Code menu option).

January 11, 2023 Update

Viewing and generating of perpetual keys for Broadcom foundational products such as vSphere, vSAN, and vCenter now includes support for vSphere 8, vSAN 8, vCenter 8, and 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.

October 25, 2022 (v2210, v2.3.x, v22.01, v22.3)

Omnissa Horizon Cloud on Microsoft Azure 2210 | pod manifest 3821.x | Omnissa Horizon Cloud Connector 2.3.x | Horizon Universal Broker Plugin Installer 22.01 | 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 your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. 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 Horizon Console operations for editing existing pools and farms and instant clone maintenance to change the relevant source entity. See the section Creating and Managing Automated Full-Clone Desktop Pools in the Horizon 8 Desktops and Applications guide within the Horizon 8 documentation.

August 9, 2022 (v2207, v2.2.x, v22.01, v22.2)

Omnissa Horizon Cloud on Microsoft Azure 2207 | pod manifest 3622.x | Omnissa Horizon Cloud Connector 2.2.x | Horizon Universal Broker Plugin Installer 22.01 | 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 accommodate 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 our Technical 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/write

Below are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. 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 VMC 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 an Omnissa Access tenant which can be added using the Horizon Universal Console, the capability of a new tenant creation from within the Horizon Universal Console is removed.

July 20, 2022 Update

Starting today, the URL for the original Horizon Cloud Documentation page is redirected to a unified Horizon Documentation page.

June 26, 2022 Update

Logging into the Horizon Universal Console has an updated user experience. This new flow incorporates the standard cloud services authentication. Your login experience might look differently when you take the first login step at the console address in your browser. 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 the console 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 Horizon Cloud 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.omnissa.com	1514 and 1515 / TCP

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.omnissa.com

1514 and 1515 / TCP

June 21, 2022 Update

In the upcoming week, a new authentication flow will be enabled for logging into the Horizon Universal Console. This new flow incorporates the standard cloud services authentication. 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.

May 10, 2022 (v2204, v2.2.x, v22.01, v22.1)

Omnissa Horizon Cloud on Microsoft Azure 2204 | pod manifest 3498.x | Omnissa Horizon Cloud Connector 2.2.x | Horizon Universal Broker Plugin Installer 22.01 | 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/write
```
To 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 accommodate 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 your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. 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.

March 9, 2022 (v2203, v2.1.x, v21.06, v21.3)

Omnissa Horizon Cloud on Microsoft Azure 2203 | pod manifest 3328.x | Omnissa Horizon Cloud Connector 2.1.x | Horizon Universal Broker Plugin Installer 21.06 | 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 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 on Microsoft Azure November 2021 release date.

No feature highlights have been provided for this release.

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/write

February 3, 2022 (v2201, v2.1.x, v21.06, v21.3)

Omnissa Horizon Cloud on Microsoft Azure 2201 | pod manifest 3254.x | Omnissa Horizon Cloud Connector 2.1.x | Horizon Universal Broker Plugin Installer 21.06 | 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: 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/write

Below are this release's highlights provided by the Product Management Team. If any questions about these highlight bullets, contact your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. 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 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.

November 30, 2021 (v2111, v2.1.x, v21.06, v21.3)

Note: A critical vulnerability in Apache Log4j identified by CVE-2021-44228 has been addressed in this version. Review VMSA-2021-0028 for more details.

Omnissa Horizon Cloud on Microsoft Azure 2111 | pod manifest 3139.x | Omnissa Horizon Cloud Connector 2.1.x | Horizon Universal Broker Plugin Installer 21.06 | 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 your Horizon Cloud representative or open a Horizon Cloud support request with your Omnissa Customer Connect account. 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 VMC on AWS, administrators can configure App Volume content replication between two or more VMC 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 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.

October 12, 2021 (v2110, v2.0, v21.06, v21.2)

Omnissa Horizon Cloud on Microsoft Azure 2110 | pod manifest 3000.x | Omnissa Horizon Cloud Connector 2.0.x | Horizon Universal Broker Plugin Installer 21.06 | 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 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 GCVE.
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 GCVE and Amazon Elastic Compute Cloud (EC2), enabling customers to deploy Horizon Enterprise with a federated architecture on these cloud platforms.

September 7, 2021 (v2109, v2.0, v21.06, v21.2)

Omnissa Horizon Cloud on Microsoft Azure 2109 | pod manifest 3000.x | Omnissa Horizon Cloud Connector 2.0.x | Horizon Universal Broker Plugin Installer 21.06 | 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.

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.

August 10, 2021 (v2108, v2.0, v21.06, v21.2)

Omnissa Horizon Cloud on Microsoft Azure 2108 | pod manifest 2955.x | Omnissa Horizon Cloud Connector 2.0.x | Horizon Universal Broker Plugin Installer 21.06 | 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.

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 Omnissa 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 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.
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 First-Gen Tenants - When Your Organization Prefers to Use a Custom Role. 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.

August 3, 2021 Update

Use of the Image Management Service (IMS) with Horizon pods deployed in VMC 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.

July 15, 2021 (v2106, v2.0, v21.06, v21.2.0)

Omnissa Horizon Cloud on Microsoft Azure 2106 | pod manifest 2915.x | Omnissa Horizon Cloud Connector 2.0.x | Horizon Universal Broker Plugin Installer 21.06 | 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.

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 First-Gen - Image Management Service Guide.
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.

Documentation

For Omnissa Horizon Cloud documentation, go to Omnissa Horizon Cloud

Internationalization

See Omnissa KB article 6000664 Announcing Omnissa Localization Support for information about localized content for product UIs and documentation.

Questa pagina è stata utile?