Dell EMC Ready Architectures for VDI - Citrix.com...l GPU resources—vSphere Client monitoring collects data about the GPU resource use from a script that is run on ESXi 6.5 and later

Dell EMC Ready Architectures for VDIDesigns for Citrix Virtual Apps and Desktops on VxRailand vSAN Ready NodesOctober 2018

H17344.1

Validation Guide

Abstract

This validation guide describes the architecture and performance of the integration ofCitrix Virtual Apps and Desktops components for virtual desktop infrastructure (VDI)and hosted shared desktops on Dell EMC VxRail hyper-converged appliances or vSANReady Nodes in a VMware vSphere environment.

Dell EMC Solutions

Copyright © 2018 Dell Inc. or its subsidiaries. All rights reserved.

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.” DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH

RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN

APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their

respective owners. Published in the USA.

Dell EMCHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.DellEMC.com

2 Dell EMC Ready Architectures for VDI

Executive Summary 5Document purpose..............................................................................................6Audience.............................................................................................................6We value your feedback......................................................................................6

Test Environment Configuration and Best Practices 7Validated hardware resources.............................................................................8Validated software resources..............................................................................8Validated system version matrix..........................................................................8Virtual networking configuration.........................................................................9Management server infrastructure.................................................................... 10

SQL Server databases.......................................................................... 10DNS......................................................................................................10

High availability................................................................................................. 10Citrix Virtual Apps and Desktops architecture.................................................... 11

Solution Performance and Testing 13Testing process................................................................................................. 14

Resource monitoring.............................................................................14Load generation....................................................................................15Profiles and workloads..........................................................................15Citrix Virtual Apps and Desktops Machine Creation Services................16Desktop VM test configurations........................................................... 16

Test results and analysis.................................................................................... 17B5 configuration................................................................................... 17

Conclusion 25User density recommendations.........................................................................26Conclusions.......................................................................................................26

References 27Dell EMC documentation.................................................................................. 28VMware documentation....................................................................................28Citrix resources.................................................................................................28

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

Dell EMC Ready Architectures for VDI 3

Contents


CHAPTER 1

Executive Summary

This chapter presents the following topics:

l Document purpose.................................................................................................................. 6l Audience................................................................................................................................. 6l We value your feedback.......................................................................................................... 6


Document purpose

This validation guide details the architecture, components, testing methods, and test results forDell EMC VxRail appliances and vSAN Ready Nodes with Citrix Virtual Apps and Desktops. Itincludes the test environment configuration and best practices for systems that have undergonetesting.

Audience

This guide is intended for architects, developers, and technical administrators of IT environments.It provides an in-depth explanation of the testing methodology and basis for VDI densities. It alsovalidates the value of the Dell EMC Ready Architectures for VDI that deliver Microsoft Windowsvirtual desktops to users of Citrix Virtual Apps and Desktops VDI components on VxRail appliancesor vSAN Ready Nodes.

We value your feedback

Dell EMC and the authors of this document welcome your feedback on the solution and thesolution documentation. Contact the Dell EMC Solutions team by email or provide your commentsby completing our documentation survey.

Authors: Dell EMC Ready Architectures for VDI Engineering Team, Donna Renfro

Executive Summary


mailto:[email protected]?subject=Feedback:%20Dell%20EMC%20Ready%20Architecture%20for%20VDI:%20Designs%20for%20Citrix%20Virtual%20Apps%20and%20Desktops%20for%20VxRail%20and%20vSAN%20Ready%20Nodes%20VG%20(H17344.1)https://www.surveymonkey.com/r/SolutionsSurveyExt

CHAPTER 2

Test Environment Configuration and BestPractices


l Validated hardware resources................................................................................................. 8l Validated software resources.................................................................................................. 8l Validated system version matrix.............................................................................................. 8l Virtual networking configuration............................................................................................. 9l Management server infrastructure........................................................................................ 10l High availability...................................................................................................................... 10l Citrix Virtual Apps and Desktops architecture........................................................................ 11


Validated hardware resourcesDell EMC validated the solutions with the specific hardware resources listed in this section.

Enterprise platforms

We used the VxRail and vSAN Ready Nodes hardware components listed in the following table. Wehave designated the configuration as B5, which is referenced throughout the document.

Table 1 Validated hardware configurations

Config Enterpriseplatform

CPU Memory RAID ctlr BOSS HD config Network

B5 V570FR740XD

5120 Gold(14-core 2.2GHz)

384 GB@2,400MT/s

HBA 330 2 x 240GB M.2

2 x 400 GB SSD(Cache)4 x 1.92 TB HDD(Capacity)

4 x IntelX710rNDC

Network hardware

The following network hardware was used in our test environment:

l Dell Networking S3048 (1 GbE ToR switch)—A low-latency top-of-rack (ToR) switch thatfeatures 48 x 1 GbE and 4 x 10 GbE ports, a dense 1U design and up to 260 Gbps performance

l Dell Networking S4048 (10 GbE ToR switch)—A high-density, ultra-low-latency ToR switchthat features 48 x 10 GbE SFP+ and 6 x 40 GbE ports and up to 720 Gbps performance.

Validated software resources

Dell EMC validated this solution with the software components listed in the following table.

Component Description/Version

Hypervisor ESXi 6.5 (VxRail), ESXi 6.7 (VSRN)

Broker technology Citrix Virtual Apps and Desktops version 7.15 LTSR

Broker database Microsoft SQL Server 2016

Management VM OS Microsoft Windows Server 2016 (DCC, StoreFront, anddatabase)

Virtual desktop OS Microsoft Windows 10 Enterprise

Office application suite Microsoft Office Professional 2016

Login VSI test suite Version 4.1

Platform VxRail v 4.5 or VSRN with vSAN v 6.5

Validated system version matrix

Dell EMC validated this solution using the system versions listed in the following table.

Test Environment Configuration and Best Practices


Table 2 Version matrix for tested system

ServerConfig

Hyper-visor

Hyper-visorVersion

Hyper-visorBuild

Bios VxRailversion

Win10Version

Nvidia vGPUVersion

B5 ESXi 6.5 U2b 6.5.0-8935087 1.4.8 4.5.215 1803 n/a

Virtual networking configurationThe network configuration for the uses a 10 GbE converged infrastructure model.

All required VLANs traverse two 10 GbE NICs configured in an active/active team.

We used the following VLAN configurations for the compute and management hosts in ourvalidation testing.

l VLAN configuration:

n Management VLAN: Configured for hypervisor infrastructure traffic—L3 routed via coreswitch

n VDI VLAN: Configured for VDI session traffic—L3 routed via core switch

n VMware vSAN VLAN: Configured for VMware vSAN traffic—L2 switched only via ToRswitch

n vMotion VLAN: Configured for Live Migration traffic—L2 switched only, trunked from Core(HA only)

n VDI Management VLAN: Configured for VDI infrastructure traffic—L3 routed via coreswitch

l A VLAN iDRAC is configured for all hardware management traffic—L3 routed via core switch



Management server infrastructure

The management server component sizing requirements are listed in the following table.

Table 3 Sizing for VxRail Appliances or vSAN Ready Nodes

Component vCPU RAM (GB) NIC OS + Data vDisk(GB)

Tier 2 Volume(GB)

VMware vCenter Appliance 2 16 1 290

Platform Services Controller 2 2 1 30

Desktop Delivery Controller andLicense Server

4 8 1 40

SQL Server 5 8 1 40 210 (VMDK)

File Server 1 4 1 40 2048 (VMDK)

VxRail Appliance Manager 2 8 1 32

Log Insight 4 8 1 530

SQL Server databases

During validation, a single dedicated SQL Server 2016 VM hosted the VMware databases in themanagement layer. We separated SQL data, logs, and tempdb into their respective volumes, andcreated a single database for Desktop Delivery Controller and License Server.

We adhered to VMware best practices for this testing, including alignment of disks to be used bySQL Server with a 1,024 KB offset and formatted with a 64 KB file allocation unit size (data, logs,and tempdb).

DNSDNS is the basis for Microsoft Active Directory and also controls access to various softwarecomponents for VMware services . All hosts, VMs, and consumable software components musthave a presence in DNS. We used a dynamic namespace integrated with Active Directory andadhered to Microsoft best practices.

High availability

Although we did not enable high availability (HA) during the validation that is documented in thisguide, we strongly recommend that HA be factored into any VDI design and deployment. Thisprocess involves following the N+1 model with redundancy at both the hardware and softwarelayers. The design guide for this architecture provides additional recommendations for HA.



Citrix Virtual Apps and Desktops architecture

The following figure shows the Citrix Virtual Apps and Desktops communication flow.

Figure 1 Citrix Virtual Apps and Desktops architecture



CHAPTER 3

Solution Performance and Testing


l Testing process......................................................................................................................14l Test results and analysis........................................................................................................ 17


Testing processTo ensure the optimal combination of end-user experience (EUE) and cost-per-user, weconducted performance analysis and characterization testing on this solution using the Login VSIload-generation tool. Login VSI is a carefully designed, holistic methodology that monitors bothhardware resource utilization parameters and EUE during load-testing.

We tested each user load against four runs: a pilot run to validate that the infrastructure wasfunctioning and valid data could be captured, and three subsequent runs to enable data correlation.

During testing, while the environment was under load, we logged in to a session and completedtasks that correspond to the user workload. While this test is subjective, it helps to provide abetter understanding of the EUE in the desktop sessions, particularly under high load. It also helpsto ensure reliable data gathering.

Resource monitoring

To ensure that the user experience was not compromised, we monitored the following importantresources:

l Compute host servers—VMware vCenter (for VMware vSphere-based solutions) orMicrosoft Performance Monitor (for Hyper-V-based solutions) gathers key data (CPU,memory, disk, and network usage) from each of the compute hosts during each test run. Thisdata is exported to .csv files for single hosts, and then consolidated to show data from allhosts. While the report does not include specific performance metrics for the managementhost servers, these servers are monitored during testing to ensure that they are performing atan expected level with no bottlenecks.

l Hardware resources—Resource contention, which occurs when hardware resources havebeen exhausted, can cause poor EUE. We monitored the relevant resource utilizationparameters and applied relatively conservative thresholds, as shown in the following table.Thresholds are carefully selected to deliver an optimal combination of good EUE and cost-per-user while also providing burst capacity for seasonal or intermittent spikes in usage.

Table 4 Parameter pass/fail thresholds

Parameter Pass/fail threshold

Physical host CPU utilization 85% a

Physical host memory utilization 85%

Network throughput 85%

Storage I/O latency 20 ms

a. The Ready Solutions for VDI team recommends that average CPU utilization not exceed85% in a production environment. A 5% margin of error was allocated for this validationeffort. Therefore, CPU utilization sometimes exceeds our recommended percentage.Because of the nature of LoginVSI testing, these exceptions are reasonable for determiningour sizing guidance.

l GPU resources—vSphere Client monitoring collects data about the GPU resource use from ascript that is run on ESXi 6.5 and later hosts. The script runs for the duration of the test andcontains NVIDIA System Management Interface commands. The commands query each GPUand log the GPU processor, temperature, and memory use to a .csv file.



Load generationLogin VSI from Login VSI, Inc. is the industry-standard tool for testing VDI environments andRemote Desktop Session Host (RDSH) environments.

Login VSI installs a standard collection of desktop application software (for example, MicrosoftOffice, Adobe Acrobat Reader) on each VDI desktop. It then uses launcher systems to connect aspecified number of users to available desktops within the environment. When the user isconnected, a logon script starts the workload, configures the user environment, and starts the testscript. Each launcher system can launch connections to a number of VDI desktops (targetmachines). A centralized management console configures and manages the launchers and theLogin VSI environment.

In addition, we used the following login and boot paradigm:

l Users were logged in within a login timeframe of 1 hour, except when testing low-densitysolutions such as GPU/graphic-based configurations, in which users were logged in every 10 to15 seconds.

l All desktops were started before users logged in.

l All desktops ran an industry-standard anti-virus solution. Windows 10 machines used WindowsDefender.

Profiles and workloadsMachine profiles and user workloads determine the density numbers that the solution can support.Each profile and workload is bound by specific metrics and capabilities, with two targeted atgraphics-intensive use cases.

Profiles and workloads are defined as follows:

l Profile—The configuration of the virtual desktop; the number of vCPUs and the amount ofRAM that is configured on the desktop and available to the user

l Workload—The set of applications that is used

We load-tested each profile by using a workload that is representative of the profile. The followingtable describes each use case.

Table 5 Virtual desktop profiles and workloads

Profile name/workload

Workload description

Task worker The least intensive of the standard workloads. This workload primarily runs Microsoft Exceland Microsoft Internet Explorer, with some minimal Microsoft Word activity, as well asMicrosoft Outlook, Adobe, and copy and zip actions. The applications are started and stoppedinfrequently, which results in lower CPU, memory, and disk I/O usage.

Knowledge worker Designed for virtual machines with 2 vCPUs. This workload includes the following activities:

l Outlook: Browse messages.

l Internet Explorer: Browse websites and open a YouTube style video (480p movie trailer)three times in every loop.

l Word: Start one instance to measure response time and another to review and edit adocument.

l Doro PDF Printer and Acrobat Reader: Print a Word document and export it to PDF.

l Excel: Open a large randomized sheet.



Table 5 Virtual desktop profiles and workloads (continued)

Profile name/workload

Workload description

l PowerPoint: Review and edit a presentation.

l FreeMind: Run a Java-based Mind Mapping application.

l Other: Perform various copy and zip actions.

Power worker The most intensive of the standard workloads. The following activities are performed withthis workload:

l Begin by opening four instances of Internet Explorer and two instances of Adobe Reader,which remain open throughout the workload.

l Perform more PDF printer actions than in the other workloads.

l Watch a 720p and a 1080p video.

l Reduce the idle time to two minutes.

l Perform various copy and zip actions.

Citrix Virtual Apps and Desktops Machine Creation Services

For this validation, we used the Virtual Apps and Desktops Machine Creation Services (MCS)linked clones provisioning method. MCS is a collection of services that work together to createvirtual desktops from a master image on demand, optimizing storage utilization and providing apristine virtual machine to users each time they log on.

Desktop VM test configurations

The following table summarizes the compute VM configurations for the profiles and workloads thatwe tested.

Table 6 Desktop VM specifications

User profile vCPUs ESXi configuredmemory

ESXi reservedmemory

Screenresolution

Operating system

Task worker 2 a 2 GB 1 GB 1280 x 720 Windows 10 Enterprise 64-bit

Knowledge worker 2 3 GB 1.5 GB 1920 x 1080 Windows 10 Enterprise 64-bit

Power worker 2 4 GB 2 GB 1920 x 1080 Windows 10 Enterprise 64-bit

Multimedia 4 8 GB 8 GB 1920 x 1080 Windows 10 Enterprise 64-bit

a. Dell EMC has validated the LoginVSI Task worker workload with two vCPUs assigned per VM, although LoginVSIlists the typical VM vCPU profile for this workload as being a single vCPU. Dell EMC diverges from this definition todeliver virtual desktops with great user experience. Increasing the vCPU count to 2 in the vCPU profile associatedwith the Task worker workload does have a minor impact on densities but generates improved user experience inreturn.



Test results and analysis

We used the Login VSI test suite to simulate the user experience for several profile types underthe typical workload for that type. The following table summarizes the test results for the computehosts using the various workloads and configurations.

Note:Dell EMC is aware of the vulnerabilities known as Meltdown, Spectre, and Foreshadow/L1TF,which affect many modern microprocessors. Ensure that you read the information in thefollowing links:

l http://www.dell.com/support/article/SLN308588

l http://www.dell.com/support/article/SLN308587

l http://dell.com/support/L1-terminal-fault

Consider this information in combination with the version information in Table 2 on page 9 tounderstand the vulnerability mitigation status of the environment we used to derive the testresults shown in the following table.

Table 7 Test results summary

Workload Density per host AverageCPU

Averageconsumedmemory

Average activememory

Average IOPSper user

B5 Knowledge worker 105 84% 105 GB 3.8

B5 Power worker 80 85% 115 GB 6.0

The table headings are defined as follows:

l User density—The number of users per compute host that successfully completed theworkload test within the acceptable resource limits for the host. For clusters, this numberreflects the average of the density achieved for all compute hosts in the cluster.

l Avg CPU—The average CPU usage over the steady-state period. For clusters, this numberrepresents the combined average CPU usage of all compute hosts. On the latest Intelprocessors, the ESXi host CPU metrics exceed the rated 100 percent for the host if TurboBoost is enabled, which is the default setting. An additional 35 percent of CPU is available fromthe Turbo Boost feature, but this additional CPU headroom is not reflected in the VMwarevSphere metrics where the performance data is gathered. Therefore, CPU usage for ESXihosts is adjusted and each CPU graph includes a line indicating the potential performanceheadroom that is provided by Turbo boost.

l Avg active memory—For ESXi hosts, the amount of memory that is actively used, asestimated by the VMkernel based on recently touched memory pages. For clusters, this is theaverage amount of guest physical memory that is actively used across all compute hosts overthe steady-state period.

l Avg IOPS per user—IOPS calculated from the average disk IOPS over the steady state perioddivided by the number of users.

B5 configuration

The following task worker, knowledge worker, and power worker performance testing wasperformed on the vSAN Ready Nodes-R740XD in the B5 configuration described in Validated



http://www.dell.com/support/article/SLN308588http://www.dell.com/support/article/SLN308587http://dell.com/support/L1-terminal-fault

hardware resources on page 8. These results also apply to the VxRail B5 configuration, as theconfigurations are the same.

Knowledge Worker, 305 users, ESXi 6.x, XenDesktop 7 v7.15 LTSR

CPU usage

We populated the compute hosts with 105 virtual machines per host and the combined compute/management host with 90 user VMs in addition to the management VMs. With all user virtualmachines powered on and before starting the test, the CPU usage was approximately 11 percenton the compute hosts.

The following figure shows the performance data for 105 user sessions per compute host. TheCPU reached a steady state average of 84 percent across the two compute hosts during the testcycle when 105 users were logged on to each host. The combined compute/management hostaverage CPU usage was 81 percent during steady state.

Memory

With regard to active memory usage for the cluster, with a total of 384 GB available memory pernode, no memory issues occurred. The compute hosts reached a maximum active memory usageof 285 GB. No ballooning or memory swapping occurred at any point during testing.



Network usage

Network bandwidth was not an issue on this test run, with a steady state peak of approximately1,077 MBps on the combined compute/management host and a peak of 625 Mbps on one of thecompute hosts. The busiest period for network traffic was during logoff phase after testing wascomplete. One of the hosts reached a peak of 1,999 MBps during logoff.

IOPS

The IOPS graphs clearly display the initial logon of the desktops, the steady state, and finally thelogoff phase. The graph displays the disk IOPS figure for the VSAN cluster.

The cluster reached a maximum (read + write IOPS) of 36,4329 disk IOPS during the boot stormand the average during steady state was 1,579.58 disk IOPS.



Disk I/O latency

Disk I/O latency was not an issue during the Login VSI testing period of this test run. Total latency(read + write latency) reached its maximum at approximately 4414 microseconds (µs) during theboot storm. The average total latency during steady state was 1,172.25 µs.

User experience

The following figure shows that the user experience score for this test did not reach the Login VSImaximum.



Power Worker, 230 users, ESXi 6.x, XenDesktop 7 v7.15 LTSR

CPU usage

We populated the compute hosts with 80 virtual machines per host and the combined compute/management host iwht 70 user VMs in addition to the management VMs. With all user virtualmachines powered on and before starting the test, the CPU usage was approximately 11 percenton the compute hosts before reboot.

The following figure shows the performance data for 80 user sessions per compute host. The CPUreached a steady state average of 85 percent across the two compute hosts during the test cyclewhen 80 users were logged on to each host. The combined compute/management host averageCPU usage was 81 percent during steady state.

Memory

With regard to memory consumption for the cluster, with a total of 384 GB available memory pernode, no memory usage issues occurred. The compute hosts reached a maximum active memoryusage of 138 GB. No ballooning or memory swapping occurred at any point during the testing.



Network usage

Network bandwidth was not an issue on this test run with a steady state peak of approximately2,206 MBps on the combined compute/management host and a peak of 2,123 Mbps on one of thecompute hosts. The busiest period for network traffic was during the logoff phase after testinghad completed. The combined hosts total usage reached a peak of 6,729 MBps during logoff.

IOPS

The IOPS graphs clearly display the initial logon of the desktops, the steady state, the logoffphase, and finally the recreation of the desktops after testing was complete. The graph displaysthe disk IOPS figure for the VSAN cluster.

The cluster reached a maximum (read + write IOPS) of 44,285 disk IOPS during the instant clonerecreation period after testing, and the steady state total average was 528 disk IOPS.



Disk I/O latency

Disk I/O latency was not an issue during the Login VSI testing period of this test run. Total latency(read + write) reached its maximum of approximately 5,596 µs during the steady state phase.

User experience

The following figure shows that the user experience score for this test did not reach the Login VSImaximum.



CHAPTER 4

Conclusion

l User density recommendations............................................................................................. 26l Conclusions........................................................................................................................... 26


User density recommendationsTest results provided recommended user densities.

The user densities in the following table were achieved by following the VMware best practices ofFTT = 1 and a reserved slack space of 30 percent. All configurations were tested with MicrosoftWindows 10 and Microsoft Office 2016.

Table 8 User density recommendations for VMware vSphere ESXi 6.5 or 6.7 with Citrix VirtualApps and Desktops

Server configuration Workload User density

B5 Knowledge worker 105

B5 Power worker 80

Conclusions

Both vSAN Ready Nodes and VxRail appliances reach similar user densities when configuredsimilarly, as shown during this validation. Remember to use VxRail sizing tools to reserve resourcesfor management tools when designing your VDI infrastructure.

The configurations for the VxRail appliances and vSAN Ready Nodes have been optimized for VDI.We selected the memory and CPU configurations that provide optimal performance. You canchange these configurations to meet your own requirements, but keep in mind that changing thememory and CPU configurations from those that have been validated in this document affects theuser density per host.

With the introduction of the six-channels-per-CPU requirement for Skylake, the C7 memoryconfiguration recommendation has increased from the previous guidance of 512 GB to 768 GB.This change was necessary to ensure a balanced memory configuration and optimizedperformance for your VDI solution. The additional memory is advantageous, considering theresulting increase in operating system resource utilization and the enhanced experience for userswhen they have access to additional memory allocations.

Conclusion


CHAPTER 5

References


l Dell EMC documentation.......................................................................................................28l VMware documentation........................................................................................................ 28l Citrix resources..................................................................................................................... 28


Dell EMC documentationThe following Dell EMC documentation provides additional and relevant information. Access tothese documents depends on your login credentials. If you do not have access to a document,contact your Dell EMC representative. Also see the VDI Info Hub for Ready Solutions for acomplete list of VDI resources.

l Dell EMC VxRail Appliance documentation

l Dell EMC Virtual Desktop Infrastructure

This document is part of the documentation set for this architecture, which includes the following:

l Dell EMC Ready Architectures for VDI: Designs for Citrix Virtual Apps and Desktops on VxRailand vSAN Ready Nodes Design Guide

l Dell EMC Ready Architectures for VDI: Designs for Citrix Virtual Apps and Desktops on VxRailand vSAN Ready Nodes Validation Guide

l Dell EMC Ready Architectures for VDI: Designs for Citrix XenDesktop and XenApp on VxRailand vSAN Ready Nodes Deployment Guide

VMware documentationThe following VMware documentation provides additional and relevant information:

l VMware vSphere documentation

l vSAN Ready Node Configurator

l VMware Compatibility Guide

l vSAN Hardware Quick Reference Guide

Citrix resourcesThe following Citrix resources provide additional and relevant information:

l XenDesktop and XenApp 7.15 LTSR: System Requirements

l Citrix VDI Handbook and Best Practices

l Citrix deployment guides

l Citrix StoreFront Proof of Concept Implementation Guide

l Install and Configure

References


https://infohub.delltechnologies.com/t/solutions/vdi/https://support.emc.com/products/39970_VxRail-Appliance-Series/Documentation/https://www.dellemc.com/en-us/solutions/vdi/index.htmhttp://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/converged-infrastructure/h17343-vxrail-vsrn-citrix-design-guide.pdfhttp://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/converged-infrastructure/h17343-vxrail-vsrn-citrix-design-guide.pdfhttp://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/converged-infrastructure/h17344-vsan-vxrail-citrix-validation-guide.pdfhttp://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/converged-infrastructure/h17344-vsan-vxrail-citrix-validation-guide.pdfhttps://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/converged-infrastructure/h17345-vxrail-vsrn-citrix-deployment-guide.pdfhttps://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/converged-infrastructure/h17345-vxrail-vsrn-citrix-deployment-guide.pdfhttps://docs.vmware.com/en/VMware-vSphere/index.htmlhttp://vsanreadynode.vmware.com/RN/RNhttps://www.vmware.com/resources/compatibility/search.php?deviceCategory=vsan&details=1&vsan_type=vsanreadynode&vsan_partner=23&vsan_releases=278&page=1&display_interval=10&sortColumn=Partner&sortOrder=Aschttps://www.vmware.com/resources/compatibility/vsan_profile.html?locale=enhttps://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/system-requirements.htmlhttps://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/downloads/handbook-715-ltsr.pdfhttps://www.citrix.com/products/xenapp-xendesktop/resources/#doc-type=iso-deployment-guideshttps://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/citrix-storefront-2.0.pdfhttps://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/install-configure.html

Dell EMC Ready Architectures for VDI Designs for Citrix Virtual Apps and Desktops on VxRailand vSAN Ready Nodes Validation GuideContentsExecutive SummaryDocument purposeAudienceWe value your feedback

Test Environment Configuration and Best PracticesValidated hardware resourcesValidated software resourcesValidated system version matrixVirtual networking configurationManagement server infrastructureSQL Server databasesDNS

High availabilityCitrix Virtual Apps and Desktops architecture

Solution Performance and TestingTesting processResource monitoringLoad generationProfiles and workloadsCitrix Virtual Apps and Desktops Machine Creation ServicesDesktop VM test configurations

Test results and analysisB5 configuration

ConclusionUser density recommendationsConclusions

ReferencesDell EMC documentationVMware documentationCitrix resources

Documents

Dell EMC Ready Architectures for VDI - Citrix.com...l GPU resources—vSphere Client monitoring collects data about the GPU resource use from a script that is run on ESXi 6.5 and later