This message was deleted.

Just reading this about Autoupdate... Should autoupdate apply changes to the personality.ini ? https://www.citrix.com/blogs/2016/07/12/vda-configuration-options-part-1/

Autoupdate is weird and creates its own cache outside of all the lists. My understanding is that nothing writes to the personality.ini file after it’s deployed, only reads from it.

Hi Mike - i really just need to use ListofDDCs in the registry, but i can't get it to take effect. Personality.ini always seems to take precedence.

Different approach, but FWIW, I always GPP-purge HKLM\SOFTWARE\Citrix\VirtualDesktopAgent\ListOfDDCs, and use GPO to enable both list of DDCs and Auto-Update.

You basically need to strip them out of personality ini if moving to a new zone/site. Auto update can be a pain even though it has highest priority

In cloud deployments I always disable auto update via policy, and then hardcode the CC via GPP

Interesting, thanks for the feedback guys. @James Kindon Did you see something specific with Citrix Cloud around Auto Update causing problems with Cloud / MCS ?

Yeah zoning challenges and auto configs that introduced bad behaviours, as a rule of thumb I disable it and never looked back - across many many deployments

agreed with James. We took that exact approach. Since we are globally dispersed with many resource locations, our policy is configured as a GPP to write the cloud connectors to the listofddc's based on AD site. Works very well for us.