Redbook - Pano System on Citrix XenDesktop - Pano Logic

DEPLOYING PANO SYSTEM ON CITRIX XENDESKTOP
Table 8: Summary of Software Needed for a Sample 1,000-Seat Deployment
Component Number Description
<strong>Pano</strong> Controller VM 2 or 3
Two required for a <strong>Pano</strong> Controller scalability
group; add one more for a failover group. (For
redundancy, install additional <strong>Pano</strong> Controller
instances on separate servers.)
XenServer/ESX
Hypervisor
32-44
One per server is required for both desktop and
infrastructure servers.
XenDesktop Controller 1 or 2
For scalability, should be hosted on different
servers than the DVMs and <strong>Pano</strong> Controller.
Additional redundant Controller instances will
be needed if you use a <strong>Pano</strong> Controller group
or use multiple servers for higher availability.
Citrix Provisioning
Services (PVS)
Machine Creation
Services (MCS)
1
1
Image cloning is optionally recommended at
this deployment size to conserve storage
space.
Required for Pooled or Dedicated desktops.
(XenDesktop 5 only)
NetScaler 1
Required to load balance connections from
<strong>Pano</strong> Controller VMs to multiple XenDesktop
Controller instances.
XenDesktop Controller Redundancy and NetScaler
Deployments of this size may require more than one XenDesktop Controller. Multiple
Controller instances can both increase performance or scalability and improve availability,
when the Controllers are installed on different physical servers. If more than one
XenDesktop Controller instance is deployed, a load balancer like NetScaler will also be
needed so that <strong>Pano</strong> Controller can connect to all of them. See “Scalability and
Redundancy on XenDesktop” on page 5 for information about XenDesktop Controller and
NetScaler.
PANO LOGIC: REDBOOK PAGE 12