VDA attempting to register to an old or decomissioned DDC after upgrade

book

Article ID: CTX216883

calendar_today

Updated On:

Description

After performing an upgrade and renaming or rejoining the Delivery Controller, the VDA attempts to register to an old or decommissioned DDC.

When viewing the event viewer on the VDA after restarting the Citrix desktop service, the VDA can be seen attempting to register to an old DDC's FQDN.
Following CTX136668 or CTX126992 no incorrect configurations are found.
Checking the List of DDCs key correctly shows only the new controller(s).
Personality.ini file on the VDA's root of C:\ shows no DDCs or has the proper ones listed.

Resolution

There is a file located in C:\Program Data that contains historical data for the Broker Agent.

This files is located in:

C:\ProgramData\Citrix\PvsAgent\Locallypersisteddata\BrokerAgentInfo\SavedListOfDDCsSids.xml

This location , by default is only accessible by the SYSTEM account in windows. In order to make any changes the file, the admin must change the NTFS permission on the objects.
First, the admin must take ownership of the C:\ProgramData\Citrix\PvsAgent\Locallypersisteddata folder and all sub-containers then allow read and write permission for the admin user.

Once access is granted to edit the file, view the file in a text editor in order to see if the old DDC name is in the file.
If the old DDC is found rename the file to SavedListOfDDCsSids.xml.old and restart the Citrix Desktop Service.
The VDA should now successfully register.

Problem Cause

The file is not updated during the upgrade and would normally not affect the upgrade process had the computer name and/or SID of the DDC not been changed.