Your SlideShare is downloading. ×
0
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
TechNet Live spor 1   sesjon 6 - more vdi
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

TechNet Live spor 1 sesjon 6 - more vdi

446

Published on

Hvordan administrerer og bruker du din VDI-løsning best mulig? Hva kan Microsoft tilby av VDI-drift og hvordan benyttes det i praksis? Vi ser på hvordan bl.a. System Center kan benyttes i en …

Hvordan administrerer og bruker du din VDI-løsning best mulig? Hva kan Microsoft tilby av VDI-drift og hvordan benyttes det i praksis? Vi ser på hvordan bl.a. System Center kan benyttes i en VDI-løsning.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
446
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. MORE VDI!Morgan Simonsen, Atea
  • 2. Agenda• VDI Configuration• Management• Solution sizing• Sessions vs. VDI smackdown
  • 3. CONFIGURING MS VDI
  • 4. Checklist: Deploy VDI1. Install RD Session Host role service2. Install RD Virtualization Host role service3. Install RD Connection Broker role service4. Install RD Web Access role service5. Create virtual desktop VM6. Configure TS Web Access Computers group on RD Connection Broker7. Configure RD Web Access8. Assign a Personal Desktop to a user9. Configure RemoteApp and Desktop Connection
  • 5. Connecting to a PVD1. A user initiates the connection to the personal virtual desktop by using RD Web Access or by using RemoteApp and Desktop Connection2. The request is sent to the RD Session Host server running in redirection mode3. The RD Session Host server running in redirection mode forwards the request to the RD Connection Broker server4. The RD Connection Broker server queries Active Directory Domain Services and retrieves the name of the virtual machine that is assigned to the requesting user account5. The RD Connection Broker server sends a request to the RD Virtualization Host server to start the virtual machine6. The RD Virtualization Host server returns the IP address of the fully qualified domain name to the RD Connection Broker server. The RD Connection Broker server then sends this information to the RD Session Host server running in redirection mode7. The RD Session Host server running in redirection mode redirects the request to the client computer that initiated the connection8. The client computer connects to the personal virtual desktop
  • 6. VDI AND SESSIONS SIZING
  • 7. VDI Capacity Planning Caveats and Objectives Performance is very subjective with many variables• Caveats – Data provided is based on benchmark results and is not reflective of many real-life deployment considerations: • Is based on specific usage scenarios • Does not account for necessary “cushion” to deal with temporary peaks in resource usage – Recommend piloting for performance planning – Multiple factors determine actual performance • Variations in hardware • Driver versions • Desktop Workloads • Application quality• What we used: – Two differently configured AMD servers – Fiber Channel SAN• Objectives to be determined: – An indication of VM’s per server that could VDI scale to • Processor, Disk and Memory requirements • Network requirements – Service Placement – Comparison against Session Virtualization scale on same hardware
  • 8. What bottlenecks do you hit first?• In order, generally that is: – Disk IO – Memory pressure – Processor• Disk IO is a performance and density related impact• Memory is a density impact• Processor is a performance and density related impact
  • 9. VDI Capacity Planning Disk IO Rule of thumb: SANs are your new best friends• Disk performance is the most critical factor in achieving density• Internal testing showed Windows 7 having lower Disk IO than Windows XP• SAN makes significant difference. Highly recommended – Plenty of cache – Consider de-duplication support especially if persistent – De-duplication allows the benefits of individual images at the cost of differencing disk – Managing images on a SAN is way faster and easier than over network (provisioning is faster) – We mean real SAN (iSCSI or FC) not NAS across the network… – Remember RDS does not require this huge SAN investment…• If you have low complexity requirements: – Think about cheaper DAS – RAID 0+1 offers better read and write performance than RAID 5 – Make sure to consider RDS
  • 10. VDI Capacity Planning Disk IO 64 Read Write Read+Write VMs Mbytes/sec Ops/sec Mbytes/sec Ops/sec Mbytes/sec Ops/sec Avg Peak Avg Peak Avg Peak Avg Peak Avg Peak Avg Peak Logon 10 220 350 2500 8 75 350 2500 18 224 700 3500 Steady .8 3.6 40 260 3.3 10 130 220 4 12 170 400 State• Peak of read/write @ 3500 IOPs on single un-clustered server (Starting 64 VMs simultaneously) – Multiply that by number of servers – Result is the rough guidance for the maximum SAN disk IOPS you need – Test for the most demanding user logon pattern (for example: 9 am scenario) – This test based on Windows 7 Enterprise• Why use IOPS as a measurement? – Trying to calculate drive perf differences based on seek, latency and transfer rate is hard – IOPS is an easier way of understanding disk/SAN performance – Reference: http://en.wikipedia.org/wiki/IOPS
  • 11. VDI Capacity Planning Memory Rule of thumb: More is better• Biggest constraint of upper limit VM density (not performance related) – Constrained by: • Available memory slots in servers • Largest Available DIMMs – Creates an artificial scale ceiling• Buy as much RAM as you expect to scale the number of VM’s• Plan for and allocate at least 1GB per Windows 7 VM – Memory allocation should be determined by upper maximum limit of running apps – Allocate enough RAM to prevent the VM paging to disk – 1GB actually covers a fair amount of app use….• Also refer to: http://www.microsoft.com/whdc/system/sysperf/Perf_tun_srv- R2.mspx.
  • 12. VDI Capacity Planning Processor Rule of thumb: If it doesn’t have SLAT don’t buy it• # of VMs per core is highly dependent on user scenarios – Application specific usage play a big role• Hyper-V supports: – 64 VMs per Server in Clustered scenarios – 384 VMs per Server in non-Clustered scenarios – 8 VM’s per Core • 8 VM’s/core is not an architectural limitation but what we have tested and support• SLAT enabled processors provide up to 25% improvement in density• What is Second Level Address Translation (SLAT)? – Intel calls it Extended Page Tables (EPT) – AMD calls it Nested Page Tables (NPT) or Rapid Virtualization Indexing (RVI) – Processor provides two levels of translation • Walks the guest OS page tables directly • No need to maintain Shadow Page Table • No hypervisor code for demand-fill or flush operations – Resource savings • Hypervisor CPU time drops to 2% • Roughly 1MB of memory saved per VM
  • 13. VDI Capacity Planning Processor Single (Unclustered) server results: – Win7 VMs using 512 MBs RAM per instance – not supported! – Only supported with 8 VM’s per core • Though lab benchmark testing went as high as 11 VMs per Core at the limit – Note: Requirements for clustering will limit VDI VM supported capacity to 64 VMs per server Server Cores SLAT VDI RDSH (TS) RDSH/VDI VMs/Users Users Ratio SERVER1 16 ON 175 310 ~1.75 SERVER1 16 OFF 140 N/A N/A SERVER2 8 N/A 80 160 ~2.Server Hardware:Server CPU model Sockets Cores Core speed RAM HBASERVER1 AMD 8378 4 16 (4x4) 2.4 GHz 128 GB EMC LP 1150 4 GbpsSERVER2 AMD 8216 4 8 (4x2) 2.4 GHz 64 GB EMC LP 1150 4 Gbps
  • 14. VDI Capacity Planning Processor – “Real World”Real world deployments reflect higher RDS scaleOur customer engagement feedback indicates differencesbetween tests and real world deployments: • VM’s per core are higher in our tests than in typical production VDI deployments • Production Session Virtualization scale tends to be higher than our lab tests in users per server • Our rough estimate is that some customers see as high as 5:1 in favor of Session Virtualization over VDI • Use cases will determine actual numbers That means at minimum Session Virt scales 2:1 over VDI and as high as 5:1
  • 15. VDI Capacity Planning Network Performance Rule of thumb: Rich User Experience requires rich bandwidth• LAN – Generally place VDI (RDVH) servers as “close” as possible to the users – VDI User experience is heavily dependent on network performance – LAN performance generally not a bottleneck (calculate to be sure) – Network redundancy is very important in switching fabric • When its down, the user is totally down – Ensure Blade servers can sustain on the backplane• WAN – WAN issues now equals worse issues later – Latency kills user experience – Persistent protocols take bandwidth per connection – How to tell: Multiply the number of users by approximately 20kbps • Is that beyond the capacity of your internet/WAN network? • 20kbps is the best case scenario based on HDX • 20kbps represents a cut down user experience – Look at WAN optimization technologies or compression solutions
  • 16. MANAGEMENT – WHAT TRULYREDUCES TCO
  • 17. AtSCVMM Dynamic Placement capacit y already
  • 18. System Center Configuration Manager Choices: Local Policy or Separate Primary – Hardware Inventory – Software Inventory – Timing of deployment – Controlling Update targeting – Restriction to purely OS, agent, definitions, required app servicing – Choice for native application deployment over App VirtualizationIn VDI, remember, its important to reduce VM IO andChurn
  • 19. System Center Configuration Manager • Tweaks – Apply Local Policy to limit Site Policy application • Config Mgr v.Next plans will eliminate this requirement • http://msdn.microsoft.com/en-us/library/cc146756.aspx – Hardware Inventory • Eliminate/Minimize – Software Inventory • Eliminate/Minimize – Patch Updates • Be very specific with targeting updates (English Update to English Client) – Timing of deployment • Offline Machine Servicing Tool 3.0 • Wake up, force poll, apply updates, go back to sleep
  • 20. System Center Configuration Manager• App-V and Config Manager – App-V 4.6 supports Shared Cache However… – Config Manager provides single console management – Config Manager allows distributed package management Be aware: – Config Manager “takes over” App-V client • Cant use both App-V and Config Manager to target the same VM
  • 21. Offline Virtual Machine Servicing Tool 3.0 Patching VMs on the Host
  • 22. REMOTE DESKTOP SESSIONSVS. VDI SMACKDOWN
  • 23. The Smackdown Contenders
  • 24. Round #1 – User Density Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs User Density    
  • 25. Round #2 – Resource Isolation Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Resource Isolation    
  • 26. Round #3 – Desktop and Application Performance Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Desktop and App Performance  - - 
  • 27. Round #4 – Application Compatibility Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Application Compatibility  -  
  • 28. Round #5 – Network Bandwidth and Latency Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Network Bandwidth and - - -  Latency
  • 29. Round #6 – Personalization and Localization Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Personalization and Localization   - 
  • 30. Round #7 – Resource and Load Management Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Resource and Load Management    
  • 31. Round #8 – Security (Access Control and Data) Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Security  -  
  • 32. Round #9 – Periphery Support Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Periphery Support  -  
  • 33. Round #10 – Licensing and Costs Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Licensing and Costs    -
  • 34. Round #11 – Web Integration Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Web Integration    
  • 35. Round #12 – Offline Capabilities Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Offline Capabilities    
  • 36. Round #13 – Desktop Templates Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Desktop Templates    
  • 37. Round #14 – Software Vendor Support Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Software Vendor Support  -  
  • 38. Round #15 – Availability of Skilled Staff Remote Desktop Protocol Private Pooled PhysicalChallenge RDSH VMs VMs PCs Availability of Skilled Staff   - 
  • 39. Results
  • 40. More information• Microsoft TechNet Remote Desktop guides• Microsoft Infrastructure Planning and Design (IPM) Guides• Microsoft Answers ™• Citrix: Ask the Architect• www.v-alliance.net• www.citrixandmicrosoft.com

×