| 
Common Troubleshooting Workflow - You can use the following sequence of tasks to perform common troubleshooting of your XenDesktop environment.
Troubleshooting - You can use the information in this section to prevent or identify potential troubleshooting issues related to the following topics:
Virtual Desktop Agent Registration - The Virtual Desktop Agent provides tie ICA service that manages communication between an end user's desktop and end user device. If the Virtual Desktop Agent fails to register with the Desktop Delivery Controller, it will not be made available for connections by and users during some XenDesktop upgrades. For example, after the upgrade to XenDesktop 5.5, Virtual Desktop
Agents that were already installed did not properly register with the Desktop Delivery Controller. To resolve this issue, the virtual desktop
object will need to be removed and re-entered from the desktop group in the Desktop Delivery Controller. For other registration issues, you can troubleshoot the issue by performing the following tasks:
• Reinstall the Virtual Desktop Agent
• Recreate the desktop pools
• Remove and re-add the virtual desktop from the Active Directory domain
DHCP and DNS Services - Provisioning Services makes it possible to provision thousands of
virtual desktops in a short amount of time. Because of this, the monitoring of other infrastructure services, such as DHCP and DNS
services, becomes critically important. These services should be considered mission-critical applications because if they are not
available, virtual desktops cannot obtain the IP addresses that are assigned to them. DNS issues will also prevent a connection broker,
such as the Desktop Delivery Controller, from redirecting end user requests to available virtual desktops. As a last step after updating or building a virtual machine image configuration, run the following command to clear out the DNS cache. Clearing the DNS cache ensures there are no outdated records at the time of next update
Command: ipconfig /flushdns
User Experience Requirements - While planning the requirements for a XenDesktop implementation, decisions must be made about the following end user requirements and features:
End User Requirements:
• End user types
• Desktop customization level
• Desktop availability
• Desktop access location
• Operating system version
Features:
• USB direction
• Multimedia
• Bidirectional audio
• High-resolution graphics
• Full-motion video
• VoIP
• Non-standard hardware devices connected to the end user endpoint
These end user requirements and features increase the utilization of resources in a virtual desktop environment and should be assessed and incorporated in the design at the beginning of a project.
NOTE: When replacing an existing physical desktop environment with a virtual desktop implementation, it is important to properly communicate the differences in performance between a physical desktop and a virtual desktop to end users so the implementation does not cause a significant impact to end user satisfaction.
- Verify that the Virtual Desktop Agent is registered to the Desktop Delivery Controller and if not:
a. Ping the fully qualified domain name (FQDN) of the Virtual Desktop Agent from a Desktop Delivery Controller.
b. Telnet to the IP address of the Virtual Desktop Agent on port 8080.
c. Use the following command to check if another process is using the port:
netstat-0
d. Disable the firewalls.
e. Verify that the Virtual Desktop Agent or Desktop Delivery Controller services are running. - Ping the FQDN of the Desktop Delivery Controller from the Virtual Desktop Agent.
- Telnet to the IP address of the Desktop Delivery Controller on port 8080.
- Check to see if the domain membership has failed for the workstation.
- Check the time on the Desktop Delivery Controller and the Virtual Desktop Agent to ensure that the time difference is no more than five minutes.
- Verify that the farm globally unique identifier (GUID) stored in the registry on the Virtual Desktop Agent matches the information found in the Desktop Delivery Controller farm Service Connection Point (SCP) object. Registry locations include:
a .HKLM\Software\Policies\Citrix\VirtualDesktopAgent\FarmGUID
b. HKLM\software\citrix\VirtualDesktopAgent\FarmGUID - Enable further logging and review logged errors, such as Virtual Desktop Agent logging and Desktop Delivery Controller logging. Note: For more information about enabling Virtual Desktop Agent and Desktop Delivery Controller logging, see Citrix article CTX117452
- Check the other components, such as the XenServer host and the Virtual Center Software Development Kit.
Note: For more information about additional troubleshooting tips, see Citrix article CTX118038
Troubleshooting - You can use the information in this section to prevent or identify potential troubleshooting issues related to the following topics:
Virtual Desktop Agent Registration - The Virtual Desktop Agent provides tie ICA service that manages communication between an end user's desktop and end user device. If the Virtual Desktop Agent fails to register with the Desktop Delivery Controller, it will not be made available for connections by and users during some XenDesktop upgrades. For example, after the upgrade to XenDesktop 5.5, Virtual Desktop
Agents that were already installed did not properly register with the Desktop Delivery Controller. To resolve this issue, the virtual desktop
object will need to be removed and re-entered from the desktop group in the Desktop Delivery Controller. For other registration issues, you can troubleshoot the issue by performing the following tasks:
• Reinstall the Virtual Desktop Agent
• Recreate the desktop pools
• Remove and re-add the virtual desktop from the Active Directory domain
DHCP and DNS Services - Provisioning Services makes it possible to provision thousands of
virtual desktops in a short amount of time. Because of this, the monitoring of other infrastructure services, such as DHCP and DNS
services, becomes critically important. These services should be considered mission-critical applications because if they are not
available, virtual desktops cannot obtain the IP addresses that are assigned to them. DNS issues will also prevent a connection broker,
such as the Desktop Delivery Controller, from redirecting end user requests to available virtual desktops. As a last step after updating or building a virtual machine image configuration, run the following command to clear out the DNS cache. Clearing the DNS cache ensures there are no outdated records at the time of next update
Command: ipconfig /flushdns
User Experience Requirements - While planning the requirements for a XenDesktop implementation, decisions must be made about the following end user requirements and features:
End User Requirements:
• End user types
• Desktop customization level
• Desktop availability
• Desktop access location
• Operating system version
Features:
• USB direction
• Multimedia
• Bidirectional audio
• High-resolution graphics
• Full-motion video
• VoIP
• Non-standard hardware devices connected to the end user endpoint
These end user requirements and features increase the utilization of resources in a virtual desktop environment and should be assessed and incorporated in the design at the beginning of a project.
NOTE: When replacing an existing physical desktop environment with a virtual desktop implementation, it is important to properly communicate the differences in performance between a physical desktop and a virtual desktop to end users so the implementation does not cause a significant impact to end user satisfaction.