Server upgrade of App Vols Manager

[mathewdsa]

Hi. I need to migrate 2 App vol manager servers from 2012 to 2019 keeping the same version of App Vols 4.4.

Do these steps seem right? 

• Go to managers and remove the first one 
• Shut down the first old server 
• Boot up the new one, install the SQL driver and and create the same 64-bit ODBC (I understand that 32-bit is no longer supported). 
• Run the App Vols installer and select the options to connect to existing DB
• After reboot I'll get the option to join existing manager

Thanks very much. 

Mathew

[mrkasius]

Hi @mathewdsa

Are the App Volumes Agents pointing to a load balancer or directly to both App Volumes Managers?

[mathewdsa]

Thanks. So I have checked the registry entry that is described in the 'Scaling App Volumes' article and the Manager1 key on the VMs using App Vols is set to the FQDN of one server, not a common DNS like you would have with a load balancer.

This is an old setup that I inherited so not sure if my Horizon Gold images were never setup correctly to begin with. There is no Manager2 entry in the registry for scaling settings.

[mrkasius · Accepted solution]

Well now there is no load balancer in place, the shortest way to migrate is

• Install App Volumes 4.4 on the 2019 hosts and point to the current App Volumes database
• Register the App Volumes Managers
• Edit the golden images, change Manager1 and add Manager2
• Test and validate results in a separate desktop pool
• When ok, bring the image to production
• Remove the previous (2012) App Volumes Managers according to the procedure described in https://docs.vmware.com/en/VMware-App-Volumes/2103/app-volumes-admin-guide/GUID-6DAA7BFF-D068-4E0B-A...