While troubleshooting a Citrix VDI agent failing to register with DDC(Desktop Delivery Controller), I came across a few interesting finds. I thought sharing this information on my blog will help many others.
The agent I was troubleshooting failing with below errors. After a few seconds, the agent is getting registered with DDC1 without any issues. But the moment user is trying to connect the VM6.local.com through VDI, the user is getting a standard error message similar to when no VMs available for establishing the connection.
Log Name: Application
Source: Citrix Desktop Service
Date: 3/1/2013 7:46:52 AM
Event ID: 1015
Task Category: None
The Citrix Desktop Service’s connection to the Citrix Desktop Delivery Controller Service was terminated. The Citrix Desktop Delivery Controller Service is running on server ‘DDC1’.
Check that there is no active firewall blocking the controller communicating with this machine.
Please refer to Citrix Knowledge Base article CTX117248 for further information.
Keep-alive request was rejected.
After some troubleshooting I concluded that if there is a discrepancy in list of DDCs provided in web interfaces Vs the list of DDCs given to VDI agent at the time of installation, this error can occur. The reason is simple, VDI agent trusts the list of DDCs that are provided to it at the time of installation and registers to one of them. When it receives a broker connection request from a DDC which is not there is the ListofDDCs reg value( in side HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\VirtualDesktopAgent), the VDI agent denies the request and un registers from the already registered DDCs. It will try again after a minute or so to re-register again with DDC..
So, the lesson here is that, the list of DDCs given in Web Service for a given farm and the list available at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\VirtualDesktopAgent\ListofDDCs keys should match. Otherwise, there is a possibility that you will run into issues.
Hope this helps…