Desktop Registration fails even though the VDA is able to ping both the Domain Controller (DC) and Desktop Delivery Controller (DDC). The Virtual Desktop Agents (VDA) are listed as Unregistered in Desktop Studio or in the results, these VDAs are displayed with the Get-BrokerDesktop PowerShell command:
The Windows Application event log on the VDA displays the following errors reported from Citrix Desktop Service:
Source: Citrix Desktop Service Event ID: 1001 Level: Error Description: The Citrix Desktop Service failed to obtain a list of delivery controllers with which to register. Please ensure that the Active Directory configuration for the farm is correct, that this machine is in the appropriate Active Directory domain and that one or more delivery controllers have been fully initialized. Refer to Citrix Knowledge Base article CTX117248 for further information. Source: Citrix Desktop Service Event ID: 1017 Level: Warning Description: The Citrix Desktop Service failed to register with any delivery controller. The service will retry registering with controllers in approximately 8 seconds. Please ensure that at least one delivery controller is available for Virtual Desktop Agents to register with. Refer to Citrix Knowledge Base article CTX117248 for further information. Source: Citrix Desktop Service Event ID: 1022 Level: Warning Description: The Citrix Desktop Service failed to register with any controllers in the last 5 minutes. The service will now try to register with controllers at a reduced rate of every 2 minutes.
This error occurs when the VDA is not able to access a DC on port 3268 (Microsoft Global Catalog). The VDA must communicate with the DC during the registration process in order to validate its list of configured Controllers (DDCs).
This issue can also be verified by running “netstat –na” from a command line on the VDA. In the following screenshots, the significant IP addresses are:
10.90.33.97 = VDA
10.90.33.99 = DDC
10.90.32.71 = Domain Controller
The connection between the VDA and DC on port 3268 is highlighted:
Non-Working Scenario (Port blocked):
There is no established connection between the VDA and the DC on port 3268.
Identify the cause of the port restriction, and then test the VDA registration process again. Typically, the VDA retries every two minutes, but sometimes a restart might be required.
The original article can be found here.