{"id":5314,"date":"2013-07-24T18:30:53","date_gmt":"2013-07-24T16:30:53","guid":{"rendered":"https:\/\/ingmarverheij.com\/?p=5314"},"modified":"2014-06-18T08:12:17","modified_gmt":"2014-06-18T06:12:17","slug":"citrix-pvs-optimize-endpoint-with-powershell","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/citrix-pvs-optimize-endpoint-with-powershell\/","title":{"rendered":"Citrix PVS: Optimize endpoint with PowerShell"},"content":{"rendered":"

With Citrix PVS<\/strong> the content of a disk is streamed<\/strong> over the network<\/strong> to an endpoint. This requires sufficient bandwidth and an optimized<\/strong> configuration. If both criteria are not met the endpoint suffers from delays, retries or failures.<\/p>\n

\"Ain't<\/a>A number of best practices<\/strong> apply when using Citrix PVS, most of them probably apply for your situation. In the past I had to optimize my VM\u2019s manually<\/strong> each and every time I had to create a new vDisk! Ain\u2019t nobody got time for that (link<\/a>)!<\/em><\/p>\n

I wrote a PowerShell<\/strong> script that optimizes the endpoint for Citrix PVS and would like to share it with you.<\/p>\n

Updated on June\u00a018th, 2014 with version 1.7<\/em><\/p>\n

<\/p>\n

Applied best practices<\/span><\/h1>\n

The script applies a number of best practices to optimize the performance of the PVS endpoint. Some are enabled by default, some are not.<\/p>\n

\"OptimizePVSendpoint\"<\/a><\/p>\n

Disable Task Offload<\/h4>\n

The most generic best practice that applies for (almost) every PVS environment, disabling all of the task offloads from the TCP\/IP transport. See also CTX117491<\/a><\/p>\n

 <\/p>\n

Disable IPv6<\/h4>\n

\"vmxnet3<\/a>Although Citrix is working hard to get IPv6 working for all Citrix products, PVS does not support IPv6. Disabling IPv6 on your PVS endpoints prevent intermittent failures. For each network adapter the IPv6 binding is removed using the nvspbind<\/a> utility. This utility is included in the download. Also, slow boots could occur due to IPv6. See also this TechNet article<\/a>.<\/p>\n

 <\/p>\n

Disable TSO and DMA on XenTools<\/h4>\n

When you\u2019re running your PVS endpoints on Citrix XenServer 5.0 or 5.5 poor target device performance, sluggish mouse responsiveness, application latency and slow moving screen changes might occur. This is a known bug that\u2019s solved in (a hotfix of XenServer 5.6). See also CTX125157<\/a>.


<\/em><\/p>\n

Increase UDP FastSend threshold<\/h4>\n

For every UDP packet larger than 1024 bytes, the Windows network stack waits for a transmit completion interrupt before sending the next packet. Unlike for earlier releases, vSphere 5.1 does not provide a transparent workaround of the situation. See also KB2040065<\/a><\/p>\n

 <\/p>\n

Set multiplication factor to the default UDP scavenge value<\/h4>\n

High CPU usage occurs when a Windows Server 2008 R2-based server is under a very heavy UDP load. This issue occurs because a table is too aggressively scavenged. See also KB2685007<\/a><\/p>\n

 <\/p>\n

Icons are hidden<\/h4>\n

To prevent users from accessing system tools like the PVS target device software or VMware tools the icons are removed.<\/p>\n

 <\/p>\n

Disable VMware debug driver<\/h4>\n

The virtual machine debug driver was disabled for this virtual machine message displays in event log. The virtual machine debug driver is not required in an ESX host. The driver is used for record\/play functions in Fusion and Workstation products. See also KB1007652<\/a>.<\/p>\n

<\/h4>\n

Receive Side Scaling is disabled<\/h4>\n

VMXNET3 resets frequently when RSS is enabled in a multi vCPU Windows virtual machine. When Receive Side Scaling (RSS) is enabled on a multi vCPU Windows virtual machine, you see NetPort messages for repeating MAC addresses indicating that ports are being disabled and then re-enabled. See also KB2055853<\/a>.<\/p>\n

 <\/p>\n

<\/h4>\n

Remove non-present NICs<\/h4>\n

\"Device<\/a>After removing a network adapter – for instance to replace an E1000 adapter with a vmxnet3 (because your deployment tool does not support vmxnet3) \u2013 the network adapter still exists on your Windows machine. The network adapter is not visible in device manager (see KB241257<\/a>) but it\u2019s active in the IP stack and, most likely, has a higher priority. As a result the PVS target device software is unable to communicate with the streaming server.<\/p>\n

All Ethernet adapters that are not present on the machine are removed using the DevCon<\/a> utility. The utility is included in the download, in case you lost it make sure you use version 6.1.7600.16385 from the Windows 7 WDK<\/a> for x64 machines.<\/p>\n

Default setting: Enabled
<\/em><\/p>\n



Network Adapter specific optimization<\/h4>\n

\"vmxnet3<\/a>For each network adapter (E1000, vmxnet3, vmbus, etc.) best practices exists, the most generic is disabling TCP offloading. Depending on the network adapter this has different names and some have more than one feature to disable.<\/p>\n

Default setting: Enabled<\/em><\/p>\n

 <\/p>\n

The script changes the following sets the following properties:<\/p>\n\n\n\n\n\n\n\n\n\n\n
Network Adapter<\/strong><\/td>\nProperty<\/strong><\/td>\nValue<\/strong><\/td>\n<\/tr>\n
E1000 (VMware)<\/td>\nLarge Send Offload (IPv4)<\/td>\nDisabled<\/td>\n<\/tr>\n
vmxnet3 (VMware)<\/td>\nIPv4 Giant TSO Offload<\/td>\nDisabled<\/td>\n<\/tr>\n
<\/td>\nIPv4 TSO Offload<\/td>\nDisabled<\/td>\n<\/tr>\n
xennet6 (XenServer)<\/td>\nLarge Send Offload Version 2 (IPv4)<\/td>\nDisabled<\/td>\n<\/tr>\n
vmbus (Hyper-V)<\/td>\nLarge Send Offload Version 2 (IPv4)<\/td>\nDisabled<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Missing an adapter?<\/em><\/td>\nDrop me an e-mail at<\/em><\/td>\ninfo@ingmarverheij.com<\/em><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

All other properties listed in the Ethernet Adapter Properties dialog can be changed as well. All known properties and values are provided in the script, all you have to do is uncomment (removing the #-character) and set the value you want.\u00a0 Do NOT enable options before you\u2019ve tested this first and understand what the implications are.<\/em><\/p>\n

 <\/p>\n

Example
<\/strong>You want disable IPv4 Checksum Offload <\/em>for the vmxnet3 adapter. The default value is 3 (Tx and Rx Enabled), to disable the feature you need to set the value to 0.\u00a0 In the script go to lines 256, remove the # in front of\u00a0 \u2018Set-ItemProperty\u2019 and set the value \u201c0\u201d and the end of the statement.<\/p>\n

# --- IPv4 Checksum Offload ---\r\n$strRegistryKeyName = \"*IPChecksumOffloadIPv4\"\r\n# 0 - Disabled\r\n# 1 - Tx Enabled\r\n# 2 - Rx Enabled\r\n# 3 - Tx and Rx Enabled (default)\r\nSet-ItemProperty -Path (\"HKLM:\\SYSTEM\\CurrentControlSet\\Control\\Class\\{0}\\{1}\" -f \"{4D36E972-E325-11CE-BFC1-08002BE10318}\", ( \"{0:D4}\" -f $intNICid)) -Name $strRegistryKeyName -Value \"0\"<\/pre>\n
 <\/p>\n
Tested platforms<\/span><\/h1>\n
The script is tested on multiple hypervisor platforms to ensure it covers the majority of the environments. In case your missing a hypervisor (or a version) feel free to contact me at info@ingmarverheij.com<\/a>.<\/p>\n