| 
XenDesktop needs firewall rule to allow port 5985 for WinRM
Enabling WinRM for Desktop Director - http://support.citrix.com/article/CTX125243
Troubleshooting Controller Connections
- Look for Event log errors on the VDA (Virtual Desktop Agent) and the Controller
- Ensure the Controller is specified correctly in the VDA's registry
- Ensure forward and reverse DNS lookups are correct for VDA and the Controller
(Tip: check whether aging and scavenging is turned on)
- Ensure time is in sync between the VDA an the Controller
- Ensure firewall port TCP/80 is open between VDA and the Controller
- Turn on logging by modifying WorkstationAgent.exe.config on the VDA and
CdsController.exe.config on the Controller, and then restart both.
See How to Enable the Logging Process in XenDesktop - http://support.citrix.com/article/CTX117452
- Use the XDPing command to verify many of these potential misconfigurations.
Troubleshooting Provisioning Services
- Slow Virtual desktop logons with large number of retries can sometimes be resolved
by tuning network configurations such as TCP task offload
- Unresponsive desktops that hang at the boot process are sometimes caused by
failures in the Citrix PVS Stream Service
- Pay careful attention to any PVS master target devices showing a red "X"
These may have network connectivity issues such as misconfigured firewalls,
or may have inadvertently booted to a local hard drive instead of a vDisk
Troubleshooting Active Directory and Machine Creation Services
- An inability to create virtual machines via Machine Creation Services is sometimes caused by
failures in the Citrix AD Identity Service, Active Directory configurations that prevent AD account creation, or lack of storage space
Troubleshooting VDA (Virtual Desktop Agent) issues
- For Desktop Director to collect metrics, it requires Windows Remote Management to be installed, enabled,
and correctly configured. WinRM is not available by default on Windows XP, and can sometimes be blocked by firewalls
- Pay careful attention to VDA agents in the unregistered session state. Agents in this state may not allow users to login
Enabling WinRM for Desktop Director - http://support.citrix.com/article/CTX125243
Troubleshooting Controller Connections
- Look for Event log errors on the VDA (Virtual Desktop Agent) and the Controller
- Ensure the Controller is specified correctly in the VDA's registry
- Ensure forward and reverse DNS lookups are correct for VDA and the Controller
(Tip: check whether aging and scavenging is turned on)
- Ensure time is in sync between the VDA an the Controller
- Ensure firewall port TCP/80 is open between VDA and the Controller
- Turn on logging by modifying WorkstationAgent.exe.config on the VDA and
CdsController.exe.config on the Controller, and then restart both.
See How to Enable the Logging Process in XenDesktop - http://support.citrix.com/article/CTX117452
- Use the XDPing command to verify many of these potential misconfigurations.
Troubleshooting Provisioning Services
- Slow Virtual desktop logons with large number of retries can sometimes be resolved
by tuning network configurations such as TCP task offload
- Unresponsive desktops that hang at the boot process are sometimes caused by
failures in the Citrix PVS Stream Service
- Pay careful attention to any PVS master target devices showing a red "X"
These may have network connectivity issues such as misconfigured firewalls,
or may have inadvertently booted to a local hard drive instead of a vDisk
Troubleshooting Active Directory and Machine Creation Services
- An inability to create virtual machines via Machine Creation Services is sometimes caused by
failures in the Citrix AD Identity Service, Active Directory configurations that prevent AD account creation, or lack of storage space
Troubleshooting VDA (Virtual Desktop Agent) issues
- For Desktop Director to collect metrics, it requires Windows Remote Management to be installed, enabled,
and correctly configured. WinRM is not available by default on Windows XP, and can sometimes be blocked by firewalls
- Pay careful attention to VDA agents in the unregistered session state. Agents in this state may not allow users to login