Here is a great support article from the brilliant guys over at Citrix Support!

First of all you need to download and install Wireshark on the virtual desktop. (accept all defaults). Then, Copy instsrv.exe and srvany.exe from the Windows Server 2003 Resource Kit Tools to the virtual desktop.

Caution! This procedure requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Back up the registry before you edit it.

1. To find the NIC ID, at a command prompt, type:
<path>tshark -D > NICs.txt
(TShark is the text based version of Wireshark and has less overhead)

2. Edit NICs.txt and locate the NIC ID of the network card.

3. At the command prompt type:
<path>instsrv.exe wireshark <path>srvany.exe
Where path is the folder where the 2003 resource kit is held
This creates service called wireshark.

4. Edit the registry to configure the service:

a. Run regedit:

b. Locate the key called HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wireshark

c. Create key called "parameters"

d. Create a value of type reg_SZ, called "application" with value of "c:\Program Files\Wireshark\tshark.exe" -i <NIC ID> -t ad -p -n -w c:\citrixlog.pcap

5. Run services.msc, find the wireshark service, check that the security is correct (local service will work - uncheck Allow service to interact with desktop)

6. Restart the virtual desktop (if this is not possible: log off from the virtual desktop and start computer management from a separate computer in the same domain, connect to the virtual desktop and start the wireshark service - although Wireshark runs as a service, the tracingon is paused when a user logs out. So the service needs to be started at startup or when there is no user logged in.)

7. Attempt to connect as assigned user from Web Interface

8. Attempt to telnet to Virtual machine on ports 1494 and 2598 from UK.

9. Log out as assigned user.

10. Log in as an administrative user.

11. Collect the log files.

12. Stop the service.

13. When you have finished and wish to remove the service, run the command:
instsrv wireshark remove

14. Uninstall Wireshark and Winpcap from the virtual desktop.

Click here to read the full article

The HDX Monitor for XenDesktop is provided “as is” without warranty of any kind. Citrix makes no commitment to provide support for this tool.

Click here to learn more and download

If you do not configure your antivirus software properly, the performance of the Target Device and Provisioning Services Server can be greatly impacted. Below is a list of symptoms consistent with an Antivirus client that needs to be tuned:

• The Target Device seems sluggish or generally slower than normal after installing or upgrading your antivirus client.

• You notice prolonged high CPU use.

• You see a significant change in the write cache Disk I/O Performance. For example, if the percentage of disk write time or disk write queue length increase significantly.

• The Target Device software indicates excessive retries in its console.

Regardless of whether you are currently experiencing any of these symptoms, you should follow the steps outlined in the Resolution section below.

In general, most antivirus products defaults are configured to scan all files and processes on a disk, and just like an operating system that runs locally to its hardware, usually all I/O operations are subject to real time scanning, as well. If an antivirus program scans the continuously active data stream that delivers the operating system, this impedes the normal operation of Provisioning Services by causing performance delays. When a vDisk is running in standard mode and needs to be restarted, it downloads all of its previously loaded virus definitions. This is a common scenario and can cause serious degradation when rebooted several at a time, often causing a congested network pipe while the operation persists. In extreme cases, the Provisioning Services Target Device and Server can become sluggish and consume more resources than necessary. This can potentially lead to a negative impact on the overall performance of the device(s) being streamed.

Click here to check out the resolution

Citrix XenDesktop is a desktop virtualization solution that delivers a complete Windows desktop experience as an on-demand service to any user, anywhere. Most large implementations of XenDesktop thus far have been based on Microsoft Windows XP, although that is expected to change quickly as Microsoft Windows 7 goes mainstream in the enterprise. Many early adopters of XenDesktop have faced the challenging task of tuning Windows XP for a hosted VM-based VDI desktop model. Typically, Windows operating systems are tuned based on whether they are a client or server operating system. In the case of a hosted VM-based VDI desktop though, Windows XP is a client operating system operating in more of a traditional server role in the datacenter. Understanding this duality is just the beginning of optimizing Windows XP for XenDesktop.
While most server-based computing administrators have experience tuning server-based operating systems like Windows Server 2003 to support hundreds of users, not as much knowledge is available for tuning a client operating system like Windows XP for running in the datacenter.

Click here to download the whitepaper made by the Citrix Architects