Designing an Enterprise-Class XenDesktop Solution Daniel Feller – Lead Architect Twitter @djfeller Blog: virtualfeller.wordpress.com Douglas Demskis – Sr.
Nov 21, 2014
Designing an Enterprise-Class XenDesktop SolutionDaniel Feller – Lead ArchitectTwitter @djfellerBlog: virtualfeller.wordpress.com
Douglas Demskis – Sr. Architect
Why Design Is Important
• Environment that cannot support the morning user load
• A single component fails, bringing down the entire infrastructure
• Sluggish virtual desktops because of improper scale• Hypervisor• Storage• Network• CPU• Memory
Ask the right questions
• What user pattern do we expect?• Sporadic, 9-5, shifts
• System availability (9-5, 24/7)
• High-level overview of goals/user environment• Save costs, increase security, improve availability• Local, regional, branch, remote users
Agenda
• Desktop Images
• Virtualization Layer
• OS Delivery Layer
• Application Delivery Layer
• Desktop Delivery Layer
• Reference Architecture
Desktop Images
Citrix Confidential - Do Not Distribute
Desktop Specs – Operating System
• Windows XP:• Requires around 26 IOPS for startup• XenServer and ESX performed better than Hyper-V
• Windows 7 optimized for virtualized environment• More intelligent storage management• Inclusion of Host Integration Services (Hyper-V tools)
• In scalability tests from LoginVSI• With same configs (768 MB RAM)• Windows 7 performed better on Hyper-V
Users Load = Desktop SpecsUser Type OS vCPU Allocation Memory Allocation
LightWindows XP 1 512
Windows 7 1 1024
NormalWindows XP 1 1024
Windows 7 1 2048
PowerWindows XP 1 2048
Windows 7 2* 3072-4096
• Notes:• Windows 7 assumes 32bit (64 Bit requires more memory)• Windows XP base image
• Uniprocessor HAL: give 2 vCPUs and hypervisor won’t utilize• Multiprocessor HAL: use 1 vCPU and waste resources while system tries to align processors
Desktop Specs – Best Practices
• Do NOT give virtual desktops more resources than needed
• Do not overcommit the hypervisor CPUs
• Calculate for active users per core• Light: 8-10 users/core• Normal: 6-8 users/core• Power: 4-6 users/core
• Calculate users per server
• Windows XP and Server 2003’s setup process misaligns their partition by creating a signature on the first part of the disk by default and starting the actual partition at the last few sectors of the first block, misaligning the partition completely
Desktop OptimizationPartition Offset
64kB Block 64kB Block 64kB Block 64kB Block64kB Block
64kB Block 64kB Block 64kB Block 64kB Block
NTFS Partition63 Sectors
4kB
SAN Storage
Operating System
Desktop OptimizationPartition Offset
NTFS
SAN Storage
4 KB Blocks
1 READ IN VM = 2 IO ON SAN
• Use Microsoft’s diskpart tool to align the blocks• http://support.microsoft.com/kb/300415
• When the partition is aligned, every I/O from the partition results in a single I/O from the storage
Desktop OptimizationPartition Offset
64kB Block 64kB Block 64kB Block 64kB Block64kB Block
64kB Block 64kB Block 64kB Block 64kB Block
NTFS Partition128 Sectors
4kB
SAN Storage
Operating System
Desktop OptimizationPartition Offset
NTFS
SAN Storage
4 KB Blocks
ALIGNED = GOOD
Desktop Optimization
• Partition offset must be divisible by 4096
• Recommended offset:• Windows 2000, 2003, XP: 32,768• Windows Vista, 7: 1,048,576
• Determine offset with• MSINFO32• In command line: wmic partition get BlockSize, StartingOffset, Name, Index
• XP VM typically offset by 32,256• Misaligned
Partition Offset
Desktop Optimization with Provisioning Services
• XenConvert ignores existing partition offset and is optimized for NTFS by default
• Default offset in bytes = 258048 (63 * 4096)
• Utilizes XenConvert.ini to set vDisk partition offset
• Example: SAN infrastructure with 1MB partition offset[parameters]
PartitionOffsetBase=1048576
XenConvert 2.1
Desktop Optimization
• Increase service timeouts
• Disable last access time stamp
• Turn off system restore
• Disable Windows indexing service
• Zero out deleted files
• Remove unnecessary visual effects
• Disable Windows XP Tour Prompt (XP)
Desktop Optimization
• Force offscreen composition for IE
• Remove the Menu Show Delay
• Disable the Desktop Cleanup Wizard (XP)
• Disable automatic searching for Network Printers/Shares
• Turn off Automatic Updates
• Setup Pagefile Min-Max the same
• Disable hibernation
• Disable kernel memory dump
Desktop Optimizations
• Remove Windows 7 features• Media Center• DVD Maker• Table PC Components
Desktop Optimizations
• Set default start menu power button behavior
• Run XenConvert Optimizer• Will cause "complaints" from
Windows 7 Action Center• Configure Action Center to not
show warnings
Citrix Confidential - Do Not Distribute
• Windows XP Optimization Guide (CTX124239)
• Windows 7 Optimization Guide
• Linked from http://virtualfeller.wordpress.com/documents
Desktop Optimizations
Virtualization Layer
Citrix Confidential - Do Not Distribute
Scalability Influencers
• Storm Warning• Boot Storm• Logon Storm• Logoff Storm
Design Considerations
• Boot storm massive hit (26 IOPS each)
• Set workstation group peak early enough to settle down• Overcomes boot storm issues• Will try to add new idle desktops for each new logon• Event log errors if not enough resources for new idle workstations
• Make idle count = to max workstation group• Overcomes issues of new starting workstations• Set idle levels lower after morning rush over
9-5 Workday
Design Considerations
• Three shifts = three peaks• Cannot use idle settings, only 1 peak per day• Could create multiple workstation groups with different peak times
• Shift preparation• Create idle VMs to prep for next shift• Impacts current users
• Options• Have extra HW available• Approve a logon delay for users (not likely to be acceptable)
Shifts
0
500
1000
1500
2000
2500
12:00 AM
1:00 AM
2:00 AM
3:00 AM
4:00 AM
5:00 AM
6:00 AM
7:00 AM
8:00 AM
9:00 AM
10:00 AM
11:00 AM
12:00 PM
1:00 PM
2:00 PM
3:00 PM
4:00 PM
5:00 PM
6:00 PM
7:00 PM
8:00 PM
9:00 PM
10:00 PM
11:00 PM
Time
Active/Idle Desktop Graph (Three Shifts)
Active Idle
Shift Change
Shift Change
• Recommended Specs• 8 cores• X GB RAM (based on virtual desktop specs)• 6 Gbps NICs - redundancy (2 user/infrastructure,
2 storage, 2 management)
• No dedicated master
Scalability – XenDesktop on XenServer
eth0 + eth 4User and
Infrastructure traffic
Embedded (dual port) Add on (quad port)
Design - XenDesktop on XenServer
eth2 + eth5Host Management
and HA traffic
eth1 + eth3Storage traffic
Design - XenDesktop on XenServer
• Pool Size• Recommended: 1,600 VMs (16 servers per pool * 100 VMs per server)• Actual: Higher (20-40 servers per pool * 80-100 VMs per server)
• Desktop Groups• Multiple resource pools can be linked to 1 desktop group
• DOM0• Increase Dom0 RAM allocation to 2.94 GB (/boot/extlinux.conf)• Increase Xen-heap setting to xenheap_megabytes=24 (/boot/extlinux.conf)
• Virtual Center recommended specs:
• ESX 3.5: 1,700 virtual desktops
• vSphere: 2,500 virtual desktops• 4 cores• 4 GB RAM• 2 Gbps NICs (redundancy)
• Host servers recommended specs• 8 cores• X GB RAM (based on virtual desktop specs)• 6 Gbps NICs - redundancy (2 user/infrastructure, 2 storage, 2 management)
Scalability – XenDesktop on ESX
Design – XenDesktop on ESX
• vCenter limited to 3,000 VMs• VMware reference architecture: 1,000 VM blocks• User habits dictate if 2000 is feasible
• vCenter is critical to environment• Can be a single point of failure, requires a clustered solution• XD master uses API to do operational processes on VMs• Numerous calls have caused API to crash, bringing down entire VC
• Desktop Group• A XD desktop group can only point to 1 VC• Complicates design as more desktop groups required
Design – XenDesktop on ESX
• Memory over commit (Ballooning) • Disable• Risk of running out of RAM• Can cause excessive disk paging
• Transparent page sharing• Irrelevant• Not shown to help or hurt
Design – XenDesktop on Hyper-V
• Two versions• Hyper-V Free SKU for Windows 2008 R2 • Full version of Windows 2008 R2• The Free SKU supports both Hyper-V and Clustering roles
• Hyper-V Free SKU provides slightly better performance during LoginVSI tests
Design – XenDesktop on Hyper-V
• Limitations if Unclustered• 384 guests per host• Max 8 vCPUs to a single physical core
8 Cores * 8 vCPU = 64 virtual machines (MAX)
• Limitations if Clustered• 16 hosts per cluster• 64 guests per host• 1024 virtual machines per cluster (960 recommended)
• Desktop groups limited to 1 Hyper-V SCVMM
Design – XenDesktop on Hyper-V
• Recommended Cluster size: 960• XenDesktop console slows down when cluster reaches 1000+• SCVMM is single point of failure unless distributed services used• <20 Hosts - break out VMM Database from the VMM Server, Library, & Console
• Failover (live migration)• If not required, then do not implement failover clustering• Clustering adds overhead• Clustering limits scalability to 64 guests per host and 16 servers per cluster• Live migration must be started manually
Storage Recommendations
• Save state file• Disk space equal to guest’s RAM• Stored in VM directory with .BIN extension• Required file/CANNOT be disabled
• Where clustering is required• Each cluster has own volume (LUN)• Each volume is shared with all servers in cluster
Hyper-V
Storage Recommendations – All Hypervisors
• Local hypervisor storage common recommendations• Must be able to support disk I/O CRITICAL• Fast drives –15,000 RPM• Battery-backed write cache (80% write/20% read)• Verify lack of live migration acceptable• Is this enough?
Storage
Citrix Confidential - Do Not Distribute
Disk Type
• As VHD expands • Disk can become fragmented on physical media• Expansion algorithm wreaks havoc on SAN as VMs booted for first time and
page file added
• Alignment issues• Constructed with extra byte at end of file • Dynamic VHD WILL mis-align disk with storage
• Recommendation: Only use fixed-size VHDs for write cache and Provisioning services vDisk
Dynamic VHD
Storage Recommendations
• Quick and Dirty estimates• 5 simultaneous bootups per spindle• 12 simultaneous logons per spindle• 14 simultaneous logoffs per spindle• 18 simultaneous users per spindle
• IOPS calculations impacted by• Disk speed• RAID level• Read/Write % (20/80)• Activity
Activity IOPS
Startup 26
Logon 12.5
Working 8
Logoff 10.7
RAID Level IO/Write
0 1
1 or 10 2
5 4
Disk Speed Random IOPS
15,000 150
10,000 110
5,400 50
Citrix Confidential - Do Not Distribute
Write Cache Storage Location
Boot Logon Working Logoff
RAID 0 5 12 18 14
RAID 1 3 6 9 7
RAID 5 1 3 4 4
Virtual Desktops per Spindle
Boot Logon Working Logoff
RAID 0 12 5 2 4
RAID 1 20 10 4 9
RAID 5 60 20 7 15
Spindles required for 60 desktop loadWorking
3
7
15
2 Drive Bays!!!
Citrix Confidential - Do Not Distribute
IOPS Calculations
Storage Recommendations
• Virtual desktops are WRITE intensive (not READ)• 20% Read• 80% Write
• Need RAID that supports heavy writes• RAID 1 for 2 disks• RAID 10 (1+0) for 4+ disks
• RAID 5 is meant for read intensive operations • Databases• Provisioning services vDisk storage
Storage Recommendations
• Throughput:• HBA must support disk throughput• Estimate 125KB/s per desktop
• Quick and Dirty HBA Estimates• 1 Gbps HBA ≈ 800 active desktops• 1 blade enclosure = 16 blades• 1 blade ≈ 50-80 VMs• 1-2 HBAs to support load (not including redundancy)
OS Delivery Layer
Citrix Confidential - Do Not Distribute
Provisioning Services
vDisk Cache
Citrix Confidential - Do Not Distribute
• Windows 7 boots to logon screen (200 MB)
• User logs on and sets up their desktop environment (50 MB)
• User runs Office and other applications (1 GB) • Streamed applications little impact• Installed applications huge impact
• User logs off and/or shuts down Windows 7 (150 MB)
Provisioning Services System Cache
Citrix Confidential - Do Not Distribute
• Goal: Use cache and not disk
RAM = OS + OS_Cache_Req + (#_Active_vDisks *
Avg_Data_Read_per_vDisk)
• 2 vDisks: 2GB + 512 MB + (2 * 2 GB) = 6.5 GB
• 4 vDisks: 2GB + 512 MB + (4 * 2 GB) = 10.5 GB
Optimizing Provisioning Services with System Cache
• Recommended Specs: 1200-1500 streams• 8 cores• 2 GB + 2 GB RAM per vDisk (estimate)• 3 Gbps NICs teamed
• Every 1Gbps NIC ≈ 500 streams
• More streams = longer failover process• 1,000 streams ≈ 5 minutes• 1,500 streams ≈ 8 minutes
Scalability – Provisioning Services
Operating System Delivery – Data Transferred
vDisk OS
Average Transferred Data (MB)
Device Cache Server Cache
XP SP2 x32 85 90
XP SP2 x64 110 115
2003 Server SP1 x32* 95 100
2003 Server SP1 x64* 120 130
Windows 7 or Vista Enterprise x32 180 190
Windows 7 or Vista Enterprise x64 220 240
Citrix Confidential - Do Not Distribute
• DHCP• Option 66: TFTP Server• Option 67: Bootstrap file
• PXE boot services
• Boot Device Manager• Bypasses TFTP/PXE services• Allows for easier integration• Must maintain BDM.ISO file
Boot Options
vDisk Images
• Goal 1 vDisk, but more is likely
• Estimate 3-4 vDisks per image• Gold• Production• Pre-production• Development
Dev/TestPVS Server
Production PVS ServerLibrary NAS
A0A0
Use Staging Approach …
A0 A1
Update vDisk in Private Image modeCopy the vDisk to Dev/Test Environment
A1
Copy to Library and to Production
A1Automatically Update Target Devices Upon Next Reboot
A1 A0
Operations
Application Delivery
SAN, NAS
XenServer XenApp
PVS
Virtual Machine
App cab files
Decompressed Rade Cache
Write Cache Storage
vDisk
Swap/temp files
App StreamProfile
SMB/CIFS File share
Application Delivery
SAN, NAS
XenServer XenApp
PVS
Virtual Machine
Write Cache Storage
vDisk
Swap/temp files
App StreamProfile
SMB/CIFS File share
Decompressed Rade Cache
• Planning• Start with write cache on PVS Server• Start with initial size of 2 GB + swap file
• Designing• If “target device write cache” is chosen, available space must be sufficient or
OS may blue screen• Minimize network impact (limit number of hops)
• Implementing• Do NOT use PVS server• Do NOT use RAM• Use local disk (shared/local)
Write Cache Sizing Considerations
Optimizations
• Fixed vDisks: Fragmentation risk of dynamic vDisk during updates when size is increased
• Disable TCP Large Send Offload• Adds latency as packets re-segmented• Must be set on server and target
• No auto-negotiation • Causes latency in handshake• Can cause PXE timeout• Hard-set server/target NIC and switch ports appropriately
Optimizations
• File Caching• If PVS server sees drive as local drive, OS will cache• If PVS server sees drive as network drive, OS will not cache• If connection between PVS and storage is CIFS, OS will not cache
• Differential disks• Do not use• Observable decrease in responsiveness in virtual desktops
Desktop Delivery Layer
Citrix Confidential - Do Not Distribute
Citrix Confidential - Do Not Distribute
XenDesktop Connection Reference
Scalability – XenDesktop 4.0
• Influencers• XML response times• Session logon times• Hypervisor cluster / pool size
• Farm Master recommended specs: 5,000 desktops• 2 cores (1.8GHz+)• 8 GB RAM• 2 Gbps NICs (Redundancy)
• XML Controllers recommended specs: 5,000+ desktops• 2 cores (1.8GHz+)• 4 GB RAM• 2 Gbps NICs (Redundancy)
Design Challenges
Citrix Confidential - Do Not Distribute
XenServerXenDesktop Design Challenges
• Aggregating multiple pools (if more than 16 XS hosts needed)• XenDesktop Setup Wizard can only communicate to a single pool• VM templates need to be copied to each pool
• Add backup pool master for high availability
• XenServer Storage - IOPS, Write Cache disks, HBAs, StorageLink, local RAID
• XenServer Networking - VLANs, NIC bonding, segregated networks (NFS/iSCSI)
• Host / VM Sizing – no memory overcommit so size VMs properly
• Delegated administration - Who should have access?
ESXXenDesktop Design Challenges
• Pool Management start 10% of the total pool size
• Can overwhelm vCenter
• Edit Pool Management Service configuration file:• C:\Program Files\Citrix\VMManagement\CdsPoolMgr.exe.config• Modify the <appSetting> section• <add key=”MaximumTransitionRate” value=”20”/>
• Value:• VMware DRS used: 20• VMware DRS not used: 40
XenDesktop Design Challenges
• SCVMM templates• Added a local write cache disk template• Disk dropped during create wizard• PowerShell scripts needed to copy/add write cache VHD to all virtual
machines after created• Process consumes about 3 hrs for 1,000 virtual machines
Hyper-V
XenDesktop Design Challenges
• SCVMM server is able to run jobs asynchronously • Run multiple instances of the XD Setup Tool • Speeds up the VM creation
• Caution: the tool divides the number of virtual machines to be created equally across all the hosts on the SCVMM server
Hyper-V
XenDesktop Design Challenges
• Rebooting causing huge spike in disk activity
• Rebooting all desktops from SCVMM does all VMs at once
• XenDesktop console staggers reboots, minimizes impact to storage
Hyper-V
Reference Architecture
Citrix Confidential - Do Not Distribute
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)XD Controller (XML2)
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
1,750 Hosted VM-Based VDI Desktops
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)XD Controller (XML2)
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
3,500 Hosted VM-Based VDI Desktops
PVS Server
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)XD Controller (XML2)
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
5,000 Hosted VM-Based VDI Desktops
PVS Server PVS Server
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)XD Controller (XML2)
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
6,750 Hosted VM-Based VDI Desktops
XD Controller XD Controller (XML1)XD Controller (XML2)
PVS Server PVS Server PVS Server
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)XD Controller (XML2)
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
8,500 Hosted VM-Based VDI Desktops
XD Controller XD Controller (XML1)XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)XD Controller (XML2)
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
2000 Desktops
VDI Desktop Server
VDI Desktop Server
VDI Desktop Server
X Number of Desktops
10,000 Hosted VM-Based VDI Desktops
XD Controller XD Controller (XML1)XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
Provisioning Services High Availability ClusterPVS Server PVS Server
XD Controller XD Controller (XML1)
XD Controller (XML2)
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
Web Interface 3Web Interface 4
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
XD Controller XD Controller (XML1)
XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
20,000 Hosted VM-Based VDI Desktops
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)
XD Controller (XML2)
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
XD Controller XD Controller (XML1)
XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
Provisioning Services High Availability ClusterPVS Server PVS Server
XD Controller XD Controller (XML1)
XD Controller (XML2)
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
Web Interface 3Web Interface 4
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
XD Controller XD Controller (XML1)
XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
40,000 Hosted VM-Based VDI Desktops
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)
XD Controller (XML2)
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
XD Controller XD Controller (XML1)
XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
Provisioning Services High Availability ClusterPVS Server PVS Server
XD Controller XD Controller (XML1)
XD Controller (XML2)
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
Web Interface 3Web Interface 4
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
XD Controller XD Controller (XML1)
XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
Shared Storage
Provisioning Services High Availability ClusterPVS Server
Shared Storage
PVS Server
XD Controller XD Controller (XML1)
XD Controller (XML2)
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
Web Interface 1DataStore Server
Web Interface 2License Server
Control Services
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop S
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
2000 Desktops
VDI Desktop ServerVDI Desktop ServerVDI Desktop
X Number of Desktops
XD Controller XD Controller (XML1)
XD Controller (XML2)
PVS Server PVS Server PVS Server PVS Server PVS Server
Summary
Citrix Confidential - Do Not Distribute
Citrix Confidential - Do Not Distribute
• Proper design requires proper understanding• Philosophy: Are you building a desktop or a server?• Users: Light, normal, power• Hardware: Bigger isn’t always better• Availability: If something fails, will anyone notice• Storms: Uncontrollable and can impact infrastructure• Operations: Who controls what?
Desktop Virtualization Done Right
Additional Information• White Papers
• Virtual Desktop Articles: virtualfeller.wordpress.com/documents
• Community• Ask the Architects: Citrix.com/AtA• Follow Daniel on Twitter: @djfeller • Virtualize My Desktop: virtualfeller.wordpress.com • Email Questions to: [email protected]
I knew we wouldn’t be left out this
year!
Before you leave…
Before you leave…
• Recommended related breakout sessions and workshops: • SYN418W - Designing a XenDesktop Architecture• SYN332 - To 10,000 virtual desktops and beyond: best practices for scaling XenDesktop• SYN322 - Get the answers before the pilot – what you need to know before you start
your VDI project
• Continue your learning – visit www.citrix.com/SynergyEDU for more information
• Session surveys are available online at www.citrixsynergy.com starting Thursday, May 13• Provide your feedback and pick up your complimentary Starbucks or iTunes gift card at the registration
desk
• Download presentations starting Friday, May 21, from your My Schedule Tool located in your My Synergy Microsite event account