上QQ阅读APP看书，第一时间看更新

VMware Horizon components

VMware Horizon is a family of desktop and application virtualization solutions designed to deliver end user computing services, from both on-premises data centers and from cloud providers such as Amazon Web Services (AWS). The following section will provide a high-level overview of the components in the Horizon family of products that we will cover in this book, which includes the following:

VMware Horizon Connection Server, Security Server, and Unified Access Gateway
VMware Horizon Help Desk Tool
VMware Horizon Just-in-Time Management Platform (JMP)
VMware Horizon Composer
VMware Horizon Agent
VMware Horizon Client
VMware vSphere, including vCenter Server
VMware App Volumes
VMware User Environment Manager
VMware Horizon PowerCLI

Refer to the VMware Horizon product page for a list of all of the products that are part of the Horizon family ( https://www.vmware.com/products/horizon.html).

The following diagram shows where each component of a typical Horizon installation resides within the data center. The only components that are not shown but are discussed in this book are the VMware App Volumes servers and the Windows-based files servers used for hosting VMware User Environment Manager data. If they were to be shown, both of these components would be located on the internal network, along with the Horizon Connection Server, vCenter Server, virtual desktops, and Microsoft Windows Remote Desktop Session (RDS) servers.

While this book focuses on deploying an on-premises installation of VMware Horizon and other components, VMware has partnered with Amazon Web Services ( AWS) to make it possible to do so in the cloud as well. Consult the VMware document Deploying Horizon 7 on VMware Cloud on AWS ( https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vmw-deploy-horizon-seven-on-vmware-cloud-on-aws.pdf) for examples of how to deploy a vSphere-based Software Defined Datacenter ( SDDC) on AWS, which you would use to host your Horizon infrastructure. Note that VMware does not intend for this to be your only Horizon Pod, but rather one used to expand your existing Horizon infrastructure, meet disaster recovery or business continuity requirements, or for data locality purposes (place applications closer to the resources they rely on). Since you are leveraging vSphere within AWS, the Horizon deployment process is no different.