A Connection Server can sustain no more than 2000 active PCoIP sessions. This counter includes PCoIP as well as RDP connetions being brokered by this connection server.
View is typically licensed per concurrent user, with unlimited licenses for Connection and Security servers. If your active session count is high, add additional Connection or Security Servers
View supports up to 7 Connection Servers (5 actively serving users, 2 standby) per Pod.
Multiple Connection Servers must be load balanced using a support load balaning mechanism including DNS Round Robin, Network Load Balancing, or a software/hardware load balancing appliance. ]]>
When creating automated pools, use dedicated assignment and create the pool only for desktops that are intended to be used in local mode. Virtual machines that are intended for use in local mode can be placed on datastores with lower IOPS than storage intended to support large numbers of remote View desktops.
Also, because assigning ThinApp packages to local desktops is not supported, a best practice is to assign ThinApp packages to pools that do not contain any local desktops.
As a standard best practice for desktops, make sure that a unique password is created for the local Administrator account on each View desktop that you plan to use in local mode.
If you configure the desktop to use RSA authentication, end users are prompted for the RSA token when they have a network connection to View Connection Server, but are not prompted when they do not have a network connection.]]>