Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Horizon on VMware Cloud on AWS Support (58539)

Last Updated: 3/19/2024Categories: InformationalTotal Views: 25758Language:
English

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Purpose

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.

Resolution

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:

Feature

Notes

View Composer Linked Clones

Not 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 Servers

Not supported. Use Unified Access Gateway (UAG) instead.

Persona

Not supported. Deprecated with Horizon 8.  Use DEM instead.

vTPM

Full 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 OS

Supported on i3en and i4i host types, not supported on i3 host type.

Mixed IPv4 / IPv6

Not yet supported.

FIPS

Unsupported in Commercial.
Supported in GovCloud (US).

vGPU

Not 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 AWS

Unsupported 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 Licensing

Horizon 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 AWS

Amazon 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).

Related Information

For more information, see the VMware Interoperability Matrices.
Page last reviewed: February 2024
Next review due: April 2024

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

VMware Cloud on AWS

Related Versions:

VMware Horizon 8

VMware Horizon 7

Take Our Survey

Support Assistant