A typical View architecture design uses a pod strategy that consists of components that support up to 10,000 remote desktops using a vSphere 5.1 or later infrastructure. Pod definitions can vary, based on hardware configuration, View 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 View solution.

Important: This chapter does not cover the following topics:
Architecture design for hosted applications A View pod can support up to 200 farms of Microsoft RDS hosts, and each farm can contain up to 200 RDS hosts. Supported operating systems for RDS hosts include Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. For more information, see the Setting Up Desktop and Application Pools in View. If you plan to use virtual machines for RDS hosts, also see RDS Host Virtual Machine Configuration.
Architecture design for View 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 View Agent Direct-Connection Plugin Administration.