XenApp and XenDesktop – Optimization Guide: User Logon

Here is a “never to be missed” guide on how to optimize the user logons in a XenApp and XenDesktop environment published by Citrix. I have found this very handy when deploying XenApp deployments.

Logon Optimization for XenDesktop and XenApp

Key Infrastructure XenApp Server Tuning

Hello All,

This article has been taken from the Citrix Knowledge Base article CTX116492


This article describes techniques for tuning key infrastructure servers in a Citrix Presentation Server (XenApp) farm.


To communicate with server farms, the server running the Web Interface contacts the Citrix XML Service through broker servers running on one or more specified servers. This service functions as the contact point to provide least-loaded, and other published application information, to clients and servers running between the server farm, and the server running the Web Interface. The Citrix XML Service is automatically installed with Presentation Server for Windows and Presentation Server for UNIX.

The Key Infrastructure Servers in a Citrix Presentation Server farm are the Zone Data Collector and XML Broker Servers. Having more Zones increases the load on the Zone Data Collectors in all other Zones in the farm because information must be replicated between the Zone Data Collectors in all Zones. Production Zones should not include servers from different physical locations and should not be grouped into a single zone.

Key Infrastructure Server Best Practices

Ensure that the Zone Data Collector has ample (75%) available space on the system drive (for example, a 400GB hard drive should have 400 X 0.75 = 300 or 300 GB available).

To reduce non-essential load on the Key Infrastructure Servers, do not run or point the Access Management (or Presentation Server) Console (running on another computer) to a Zone Data Collector or XML Broker Server.
Failover: Dedicate a Most Preferred Zone Data Collector in each zone.

• These servers should not run published applications.

• A lightly loaded Preferred (Backup) Zone Data Collector server should also be designated for each zone.

• This server should not be a Resource Manager Database Connection Server or Farm Metric Server.

Dedicate at least two XML Broker servers for each Web Interface Site.

• These servers should not run published applications.

• These servers should not be a Resource Manager Database Connection Server or Farm Metric Server.

Zone Data Collector Tuning

Enable the setting, Share Information across zones in the properties of the farm in the Access Management Console.

This decreases application resolution time because the local Zone Data Collector does not have to request the load information for the target zone (where the published application resides) at the time of application resolution.

Decreasing resolution time frees up the IMA service to perform other activities faster.

Fine Tuning Parameters for XML

Configure the tuning parameters on the XML brokers serving each Web Interface site and the Most Preferred and Preferred Zone Data Collector in each zone to increase scalability. These settings can also be made to all servers in the farm.

Registry Changes

Caution! Using the 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 the Registry Editor can be solved. Use the Registry Editor at your own risk. Back up the registry before editing it.

SQL Option: The values below enable timeouts for IMA threads when waiting on a SQL server for information. These values are not present by default.



The value below causes IMA to timeout a connection to SQL if it doesn’t receive a response to a query after 45 seconds.

The value below causes IMA to wait 300 seconds to make another connection to SQL after a timeout occurs.

NOTE: The changes made by the registry settings below are automatically made by IMA on Presentation Server 4.5 with Hotfix Rollup Pack 3 and above. For more information refer to CTX118659 – Best Practices for Installing and Maintaining a Large Farm with Hotfix Rollup Pack 3 for XenApp 5.0 and Presentation Server 4.5


The value below increases the amount of worker threads for the IMA Service from the default value of 8 to 128.

“IsolationWorkQueueThreadCount” =dword:00000080


This document applies to: