User guide

© 2011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Cisco Validated Design Page 68
5.3.1 Citrix XenDesktop Desktop Delivery Controller (DDC)
The DDCs were virtualized on XenServer server and some of the roles of the DDC were assigned to specific
DDCs, an approach commonly taken in Citrix XenApp deployments.
The DDCs were configured such that:
●
DDC 1: Farm Master and Pool Management
●
DDC 2 and 3: VDA Registrations and XML Brokering
In this environment, 3 DDCs (4vCPU, 4GB RAM) easily sustained the farm size of 1920 desktops and proved
stable at all various stages of testing.
5.3.2 Farm Configuration
In addition to the standard XenDesktop farm installation, the following additional items were configured or
installed:
●
Installed Citrix Pool Management Hotfix XDE400PM004
●
Installed Citrix Desktop Delivery Controller Hotfix DDCE400W2K3X64005
●
Installed Citrix Delivery Services Console Hotfix XDE400AMC002
●
Created XenDesktop policy to disable client printer mappings
●
Configured DDC1 as Farm Master and Pool Management as per CTX117477
●
Configured DDC2 & 3 for Registrations and XML Brokering as per CTX117477
●
Created one Desktop Group and aggregated two XenServer Resource Pools as per CTX120077
It was necessary to have multiple Resource Pool instances to support the 16 blade validation; each instance
required a new XenDesktop desktop group. In the testing 3 Resource Pools were used with the following
distribution:
●
2 RPs x 880 - Virtual Desktops for the scaled out test of 1760
●
1 RP - XenDesktop and associated infrastructure
By default, Pool Management will attempt to start 10 percent of the total pool size. In a large environment this
may be more than the hosting infrastructure can handle.
●
The number of concurrent requests can be throttled by editing the Pool Management Service configuration
file:
◦ C:\Program Files\Citrix \VMManagement\CdsPoolMgr.exe.config
●
Modify the <appSetting> section by adding the line:
●
<add key=‖MaximumTransitionRate‖ value=‖40‖/>
●
The Pool Management service needs to be restarted to read the new configuration
●
Note that this is a fixed value and is a setting that is specific to this environment
5.3.3 Provisioning Services Configuration
For the scaled out test, a total of 6 Provisioning Servers supported 1760 Windows 7 desktops. The Provisioning
Server streamed to ~293 desktops per virtual machine-based server using a single virtual NIC.
Note: it was determined that the PVS farm could have supported the desktops with at least one less server.
The Provisioning Services farm was created. The following items represent additional changes to the environment
after the initial default installation: