VDA Fails to Register: Cannot Communicate With Delivery Controllers

VDA Fails to Register: Cannot Communicate With Delivery Controllers

book

Article ID: CTX227388

calendar_today

Updated On:

Description

The VDA must be able to communicate with the Delivery Controllers so the VDA can register with the Site. If the VDA can't register with the Site, users can't access the applications and desktops that the VDA hosts.

If the VDA can't communicate with the Delivery Controllers in the Site, it could be caused by:

  1. Incorrect Delivery Controller configuration on the VDA: 
An administrator chooses the VDA Registration configuration method to use when installing a VDA for the first time.
There are several methods for configuring Controller addresses on a VDA.
  • Policy-based (LGPO or GPO) 
  • Registry-based (manual, GPP, specified during VDA installation)
  • Active Directory OU-based (legacy OU discovery)
  • MCS-based (personality.ini)
2. The VDA or Delivery Controllers have incorrect DNS settings.
3. Network issues prevents communication
4. The Delivery Controllers are not reachable on configured ports.
5. Invalid hostname entries in the Windows Hosts file

 
For more information, please see https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/vda-registration.html

Resolution

To resolve this issue:

1. If the communication between VDA and Delivery Controllers were set using

a) Policy or Manually/Registry-based:

  • Verify the ListOfDDCs is not empty, and that the hostnames are correctly entered and can be resolved. To do this, you can ping each host name or use nslookup from the command prompt.
  • Value will be stored in:
HKLM\Software\Policies\Citrix\VirtualDesktopAgent (ListOfDDCs)
or
HKLM\Software\Wow6432Node\Citrix\VirtualDesktopAgent (ListOfDDCs)
 *For more information, see CTX133384 - Best Practices for XenDesktop Registry-based DDC Registration 
 
b)  Active Directory OU-based discovery:
  • Value will be stored in:
32 Bit: HKEY_LOCAL_MACHINE\Software\Citrix\VirtualDesktopAgent\FarmGUID
64 Bit HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\VirtualDesktopAgent\FarmGUID

*For more information, see Active Directory OU-based Controller Discovery
 
c) Provisioned by MCS
  • The MCS process creates C:\Personality.ini, containing a list of contactable DDCs in following format:

[VdaData] ListOfDDCs=<FQDN of the Controller>

2.  Verify the VDA's DNS settings are correctly configured so the Delivery Controller's FQDN can be resolved from the VDA.

3. Verify the network communication by pinging VDA from the Controller and vice versa. 

4. Verify the VDA and the Delivery Controller can communicate on the same port.

5. Verify that any Delivery Controller host names in the Windows Hosts file are correctly entered and can be resolved. To do this, you can ping each host name or use nslookup from the command prompt.

 

Powered by Wolken Software