Citrix XenDesktop Virtual Desktop Agent (VDA) 7 stays Unregistered

In Citrix XenDesktop 7 there has been a change that DNS alias isn’t allowed anymore. See article http://support.citrix.com/article/CTX137960 for more information.

When you start a Device that has a alias in the registry it stays Unregistered and the following is logged in the Event Log.

The Citrix Desktop Service failed to register with any delivery controller”

image

This can be fixed by starting the Device in Maintenance mode and replace the registry key:

HKLM\SOFTWARE\Citrix\VirtualDesktopAgent\ListofDDC’s

to the hostname.

In my case changing

image

to

 

image

After this change the Device registers with the Desktop Delivery Controller.

image
 

Can’t get the solution to work? Contact me and let me do the trick.

 

 

 

Advertisements
This entry was posted in Citrix XenDesktop and tagged . Bookmark the permalink.

5 Responses to Citrix XenDesktop Virtual Desktop Agent (VDA) 7 stays Unregistered

  1. Ilya says:

    Tried to use DC IP address. Short name solved my problem. THANK YOU!!!

  2. Boris Groenhout says:

    additionally ….

    In Citrix XenDesktop 7.x there has been a change that DNS alias isn’t allowed anymore. See article http://support.citrix.com/article/CTX137960 for more information.
    The CNAME lookups have been disabled to enforce a tighter security model in XenDesktop 7.

    CNAME can be re-enabled by the following registry setting:

    32-bit and 64-bit:

    Registry Key: HKEY_LOCAL_MACHINESOFTWARECitrixVirtualDesktopAgent
    Name: UseCnameLookup
    Type: REG_DWORD
    Value: 1
    (1 = enabled)

    For a proper registration of the workplace the following registry setting has to be added to the client also:

    32-bit:
    Registry Key: HKEY_LOCAL_MACHINESoftwareCitrixVirtualDesktopAgent
    Name: ListOfDDCs
    Type: REG_SZ
    Value: deliverycontrollerA deliverycontrollerB

    64-bit:
    Registry Key: HKEY_LOCAL_MACHINESoftwareWow6432NodeCitrixVirtualDesktopAgent
    Name: ListOfDDCs
    Type: REG_SZ
    Value: deliverycontrollerA deliverycontrollerB

    After adjustment the registration in XenDesktop works fine 😉

    In total my reg-file looks like:

    Windows Registry Editor Version 5.00
    ; Fix to register VDA on XenDesktop 7.5
    ; http://support.citrix.com/article/CTX137960

    [HKEY_LOCAL_MACHINESOFTWARECitrixVirtualDesktopAgent]
    “UseCnameLookup”=dword:00000001
    “ListOfDDCs”=”deliverycontrollerA.domain.org deliverycontrollerA.domain.org”

    [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixVirtualDesktopAgent]
    “UseCnameLookup”=dword:00000001
    “ListOfDDCs”=”deliverycontrollerA.domain.org deliverycontrollerA.domain.org”

    Remark:
    On 64-bit environments in XenDesktop 5.6, the setting ListOfDDCs was needed in HKEY_LOCAL_MACHINESOFTWAREWow6432Node…

    On 64-bit environments in XenDesktop 7.5, the setting ListOfDDCs and UseCnameLookup is only needed in HKEY_LOCAL_MACHINESOFTWARE…
    The Wow6432Node supplement seems no longer to be necessary in a XenDesktop 7.5 environment. To be sure I add them under both.

    Bonus:

    Sometimes the logon to a XenDesktop 7.x published desktop may take long and a black screen may be visualized.
    The causes are not very clear but article http://support.citrix.com/article/CTX135782 describes the steps required to modify a registry setting on a XenApp server that will help you reduce logon times. This setting is also useful in a XenDesktop environment.

    HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixLogon
    Name: DisableStatus
    Type: REG_DWORD
    Value: 00000001

    In total my reg-file looks like:

    Windows Registry Editor Version 5.00
    ; Fix Slow logon and black screen on XenDesktop 7.x
    ; http://support.citrix.com/article/CTX135782

    [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixLogon]
    “DisableStatus”=dword:00000001

  3. L4 says:

    I have been looking for a solution to this ‘unregistred’ problem, but your solution is the ONLY one that worked for me. Added the regkeys and all machines registered. Thank you very much, this info should get more exposed!

  4. Steve says:

    Worked for me as well. DDC list is the key. If you use MCS the personality.ini file in C: should contain ListOfDDCs if it does not that is why your machines don’t register and you are forced to add to registry. The order of operation I believe is VDA attemps to determine DDC from Registry>AD>Personality.ini…. Hope this helps./

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s