OPERATIONAL DEFECT DATABASE
...
...
Starting with version 7.5, Horizon can be deployed on VMware Cloud on AWS. This article discusses the support details including interoperability with VMware Cloud on AWS versions as well as feature parity between Horizon on-premises and Horizon on VMware Cloud on AWS.
Feature Parity Support for on-premises and on VMware Cloud on AWS are in the same Horizon product. Any Horizon feature, unless otherwise listed below, can be assumed to work and is supported on both on-premises and on VMware Cloud on AWS. vRealize for Horizon (Monitoring) is supported but not tested.The table below lists the Horizon features that are not yet supported or we do not plan to support on VMware Cloud on AWS: FeatureNotesView Composer Linked ClonesNot supported. Use Instant Clone instead (Horizon 7.7 is the minimum).Content Based Read Cache (CBRC)Not supported. Not needed for performance on VMware vCloud on AWS.Security ServersNot supported. Use Unified Access Gateway (UAG) instead.PersonaNot supported. Deprecated with Horizon 8. Use DEM instead.vTPMFull Clones - Supported Instant Clones - supported with Horizon 8 and VMware Cloud on AWS version 1.19 and later. Horizon 8 2206 or later is required for Instant Clone support with vTPM on VMC on AWS and requires the workaround detailed in [1] below when using Horizon 8 2306 or earlier.Windows 11 Guest OSSupported on i3en and i4i host types, not supported on i3 host type.Mixed IPv4 / IPv6Not yet supported.FIPSUnsupported in Commercial. Supported in GovCloud (US).vGPUNot yet supported. Pending vGPU availability on VMware Cloud on AWS. [1] Connect to the Horizon ADAM DB. Navigate to OU=Properties, OU=Global, CN=Common Properties. Edit pae-DeploymentFeatureMap and change AWS to 6019. Restart all Connection Servers in the pod. This may also be required if you do an in-place upgrade from an earlier release to 2309. Interoperability of Horizon Enterprise and VMware Cloud on AWS See VMware Interoperability Matrix.To use Instant clones on VMware Cloud on AWS, must have Horizon 7.7 or later.To use App Volumes on VMware Cloud on AWS, must have App Volumes 2.15 or later.High Availability on UAG is supported on VMware Cloud on AWS but requires Unified Access Gateways be on the same segment using multicast.vIDM support on VMware Cloud on AWS Supported configuration: vIDM SaaS version, vIDM non-SaaS version deployed on-premise and extended to work with desktops deployed on VMware Cloud on AWSUnsupported configuration: vIDM non-SaaS version deployed directly on VMWare Cloud on AWS or on AWS EC2 Use Horizon Cloud Connector to enable Horizon Universal Subscription and Subscription Licenses for Horizon on VMware Cloud on AWS when connecting to Horizon Control Plane first-gen, be sure to download the right version – if you are running the Horizon Connection Server in native AWS, download the EC2 version of the Cloud Connector. Horizon Control Plane first-gen services supported with Horizon 8 on VMware Cloud on AWS include: • Universal Broker • Helpdesk • Cloud Monitoring Service (CMS) • Subscription LicensingHorizon Control Plane first-gen services not supported with Horizon 8 on VMware Cloud on AWS include: • Image Management Service (IMS) • HLCM (Horizon Lifecycle Management)Be aware of the HCS first-gen Control plane EOL timelines (KB92424)Use the Horizon Edge to enable Horizon Universal Subscription and Horizon Plus for Horizon 8 on VMware Cloud on AWS when connecting to Horizon Control Plane next-gen. This is supported with both All-in-SDDC and Federated deployment models.Horizon Control Plane next-gen services supported for Horizon 8 on VMware Cloud on AWS include: • Subscription Licensing • Monitoring You may extend your on-premises Horizon Pod to manage one or more VMware Cloud on AWS SDDCs without having to deploy a separate Horizon Pod on AWS. This is enabled by the Horizon Remote Agent feature. For more details, see https://kb.vmware.com/s/article/86304 AWS Managed Microsoft AD Horizon Agent installation requires local administrative rights. Note: The 'Domain Admins' group in AWS AD is not a member of the local 'administrators' group by default, when a computer is joined to the domain. If required, you can provide a user account with local administrative rights when the Horizon Agent installer prompts for administrator credentials. When creating an Instant Clone pool, the default Active Directory container in the guest customization wizard is 'CN=computers', however due to permission differences in AWS AD this location cannot be used, so you will need to change this location using the 'browse' option in the Horizon Administrator or Horizon Console when creating the pool. AWS RDS (Relation Database Service) MS-SQL TrueSSO is not supported while using AWS RDS, normal SSO with password can be used instead. Amazon FSx for NetApp ONTAP Amazon FSx for ONTAP is supported for use with Horizon on VMware Cloud on AWSAmazon FSx for ONTAP can be used with VMware Cloud on AWS for App Volumes replication via Storage Groups. The FSx datastore must be set as “Not Attachable” in the App Volumes Manager. Writable Volumes are not supported on FSx for ONTAP with VMC at this time. Impact to Horizon Enterprise during VMware Cloud on AWS SDDC Upgrade For more information, see Impact to Horizon Enterprise during VMware Cloud on AWS SDDC Upgrade (74599).
For more information, see the VMware Interoperability Matrices.Page last reviewed: February 2024Next review due: April 2024
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
