XD 7.6 VDA Registering With Incorrect XenDesktop Controller and Site

book

Article ID: CTX205057

calendar_today

Updated On:

Description

XenDesktop 7.6, PVS 7.6 - VDA registering with the incorrect XenDesktop site Existing PVS Vdisk copied and used for new image. After roughly 10 days of the VDA registering to the correct XenDesktop site, it suddenly stops and tries to register with original XenDesktop site. DDC List is being pushed via Reg preferences Hive HKEY_LOCAL_MACHINE Key path SOFTWARE\Policies\Citrix\VirtualDesktopAgent

The following directory is empty of any presisted data: C:/ProgramData/Citrix/PvsAgent/LocallyPersistedData\BrokerAgentInfo

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Set the policies to prohibited in the Group Policy Management Console as well as in Studio
Rebooting VDA or restarting desktop service - key was then set to 0
VDA registers only against the hardcoded ListOfDDCs.

Problem Cause

-Auto Controller Discover Policy not being applied
-Even after setting the policy in Studio the reg key defaulted back to 1(enabled) after restarting desktop service or reboot of VDA.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\VirtualDesktopAgent\EnableAutoUpdateOfControllers
-When Disabled the value should be 0

Issue/Introduction

Customer found that after introducing the a site, vdas from the new site(site2) were registering against controllers in site1

Was this article helpful?

thumb_up Yes

thumb_down No

Welcome to "KB Articles"