A typical Horizon 7 architecture design uses a pod strategy. Pod definitions can vary, based on hardware configuration, Horizon 7 and vSphere software versions used, and other environment-specific design factors.
The examples in this document illustrate a scalable design that you can adapt to your enterprise environment and special requirements. This chapter includes key details about requirements for memory, CPU, storage capacity, network components, and hardware to give IT architects and planners a practical understanding of what is involved in deploying a Horizon 7 solution.
Important: This chapter does not cover the following topics:
| Architecture design for hosted applications | A Horizon 7 pod can support farms of Microsoft RDS hosts, where each farm contains RDS hosts. For more information, see Setting Up Published Desktops and Applications in Horizon 7. If you plan to use virtual machines for RDS hosts, also see RDS Host Virtual Machine Configuration. |
| Architecture design for Horizon 7 Agent Direct Connect Plugin | With this plugin running on a remote virtual machine desktop, the client can connect directly to the virtual machine. All the remote desktop features, including PCoIP, HTML Access, RDP, USB redirection, and session management work in the same way, as if the user had connected through View Connection Server. For more information, see Horizon 7 Agent Direct-Connection Plugin Administration. |
