Citrix: VDA Configuration Options – Part 1
While working on the CXD-302 Advanced Troubleshooting course (if you haven’t yet, you should really go and take it right away), I started looking at data from Citrix Support. Before starting to teach how to troubleshoot problems, it helps to know which are the most common.
I found that VDA registration has been in the top 5 issues reported to Citrix Support, and in CXD-302 we’ve dedicated one whole module just to troubleshooting of VDA registration.
Why is it such a big issue? The reason is that registration is a very sensitive operation from a security perspective – you’re effectively establishing a connection between master (controller) and slave (VDA). And with such a sensitive operation, expected behavior is to reject the connection if everything is not in perfect shape. You are effectively establishing two separate communication channels – VDA to XenApp/XenDesktop Delivery Controller (XDC) and separate channel for XDC to VDA communication. Kerberos is used, so time synchronization or domain membership issues are unforgiving. Service Principal Names (SPN) are used by Kerberos, so you cannot use load balanced IPhostname.
We have published various articles (including, Troubleshooting XenDesktop registration process) and have provided tools (including Citrix Health Assistant that was updated just a few days ago).
Read the entire article here, VDA Configuration Options – Part 1
via the fine folks at Citrix Systems, Inc.