VDAs are still trying to register with old DDCs post changing the list of DDCs
book
Article ID: CTX230703
calendar_today
Updated On:
Description
Post changing the Delivery Controllers list, VDAs are still trying to register with the old Controllers.
Deletes the old Delivery Controllers FQDN on "ListOfDDCs" key in "HKLM\Software\Citrix\VirtualDesktopAgent\Policy" registry and restarts the Citrix desktop service, however the VDAs are still trying to register with the old Delivery Controllers.
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
There are various locations where the old Delivery Controller names are cached.
- C:\ProgramData\Citrix\PvsAgent\LocallyPersistedData\BrokerAgentInfo\ and Check SaveListOfDdcsSids.xml
- C:\Program Files\Citrix\Virtual Desktop Agent\Policy and Check SaveListOfDdcsSids.xml
- "ListOfDDCs" key in registry path HKLM\Software\Citrix\VirtualDesktopAgent
- "ListOfDDCs" key in registry path HKLM\Software\Policy\Citrix\VirtualDesktopAgent
- "ListOfDDCs" key in registry path HKLM\Software\Citrix\VirtualDesktopAgent\Policy
- C:\Personality.ini
- Delete old Delivery Controllers FQDN and SIDs in the above mentioned files and registry.
- Update the new Delivery Controllers FQDNs from control panel\VDA configuration.
- Restart the Citrix Desktop Service on VDA(If Manual VDA).
- If MCS provisioned VDAs, perform the same steps in master image, restart the Citrix Desktop service and update the catalog for the changes to be carried over to the VDAs.
Problem Cause
Old Delivery Controllers information cached on the VDAs
Was this article helpful?
thumb_up
Yes
thumb_down
No