This chapter discusses architecture design elements and planning guidelines that 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 8 solution.
For details on how to architect a Horizon 8 deployment, see Workspace ONE and Horizon Reference Architecture.
Important: This chapter does not cover the following topics:
| Topic | Description |
|---|---|
| Architecture design for hosted applications | A Horizon 8 pod can support farms of Microsoft RDS hosts, where each farm contains RDS hosts. For more information, see the Desktops and Applications in Horizon 8 document. If you plan to use virtual machines for RDS hosts, also see RDS Host Virtual Machine Configuration. |
| Architecture design for View Agent Direct-Connection 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, Omnissa Horizon Web Client, RDP, USB redirection, and session management work in the same way, as if the user had connected through the connection broker. For more information, see the Horizon Agent Direct-Connection Plug-In document. |
Note: Horizon Web Client is available with Horizon 8 versions 2412 and later. For Horizon 8 versions 2406 and earlier, Horizon Web Client is called "HTML Access." This documentation page uses the name "Horizon Web Client" to refer to both Horizon Web Client and HTML Access.
Was this page helpful?