XenApp 6_5 for Windows Server 2008 R2
This article provides a resolution for the issue of Desktop Director unable to Monitor a Larger XenApp 6.5 Farm.

Symptoms or Error

Desktop Director is unable to monitor a larger XenApp 6.5 farm that has more than 100 servers. And, any attempt to monitor a Citrix session is timed out.

The following is an extract from the Desktop Director log:

 The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.


To resolve the issue, complete the following steps:
  1. On all XenApp servers in the farm:
    1. Open the command prompt with server administrator privileges.
    2. Run the command winrm set winrm/config/Service @{MaxConcurrentOperationsPerUser="400"}.
    3. Run the command winrm set winrm/config @{MaxTimeoutms = "1800000"}.
    4. Restart WinRM services or reboot the server by issuing the following commands:
      net stop winrm
      net start winrm
  2. On the server where Desktop Director (IIS) is installed:
    1. Set Connector.WinRM.Timeout to 1800000.
    2. Restart IIS.

Problem Cause

WinRM in the corresponding farm is responding late. In the meantime, the default timeout is reached and no data is returned.


Join the conversation

Citrix Discussions

Open a case

Citrix Support