This message was deleted.
# citrix-vad
s
This message was deleted.
a
also our plan for the controller swap (correct me if i'm wrong on this) is to add the 2 new controllers into the environment so we'd temporarily have 4, then remove the old 2 after
s
thats exactly how i just did it. Don't forget to adjust any scripts that reference the old ones, or add the AHV plugin if Nutanix, or Firewall rules for hosting connections, etc...
👍 1
a
so if we do nothing else and JUST add those 2 new controllers in, will that autoupdate feature add them to that ListOfDDCs reg key (and at the same time remove the old once we clear out the old i assume?)
s
we have Group Policies where we define the ListOfDDC through GPP registry entries....however, in theory what you said should in theory work. Based on the autoupdate explanation from https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/vda-registration.html
a
cool yup thats what i was using as a reference. i guess it should be easy enough to test once i add one of the new controllers, reboot a VDA and see if the reg entry changes
s
100%, need to address any of your non persistent images too
a
of course......we're actually all persistent MCS so i'd just need to make sure to update those images too
when you did this, did you add the new controllers (expanding the cluster) during production hours? i'd assume that type of thing is safe and maybe do the removal of the old ones off hours
s
as a consultant i'd recommend off hours, however, shouldn't be an issue should you do it during the day. Removal shouldn't be an issue either, given that nothing is really using it (storefront, STA, director, VDA, etc...)
i usually disable broker services for a day or two before removal
a
good call there....and yup thats what i was thinking about what it affects/doesnt affect. since we can reboot one controller during the day and it just migrates users to the other seemed safe enough
so i noticed there is a "RegistryOverridesAutoUpdate" key w/ a value of 1. Thats not one that we've ever manually set so must be a default.....would we need to change that key to a 0 when we add / remove controllers so that auto update works?
s
interesting, think you're right it is default, but so is autoupdate.
a
i guess we'll see what happens when i add one of the new ones!
s
so looks like that registry key is populated depending on what method you choose during VDA install
a
That makes sense .. question I guess I have to figure out now is if/how the auto update will work with that
t
what we had: server 2016 with older CTX version. and wanted to upgrade CTX version and also Server to 2022. the older CTX version does not supported Server 2022. so we had to install old CTX version to Server 2022, add them to existing environment, sync all.. then remove the 2016 Server from site, upgrade CTX on the new 2022 Servers. regards
a
awesome thanks thats pretty damn close to what we're looking to do.
alright well adding the 2 new controllers went pretty smoothly tonight. now i'm just waiting to see if the auto update works. i think its just a waiting game for whenever that 90 min interval update kicks in?