AppVol Update from 2.17 to 2.18 - Downtime?

[burgerking68]

Hello, we want to update our app volume environment from version 2.17 to 2.18. So far, this has always been done by an external service provider. Unfortunately, this time it falls flat.

Hence my question: can the version be updated to version 2.18 during operation or are all user sessions separated (running AppStacks and Writeable Vol)? We have 2 AppVol servers and also an AppVol SQL database.

(Of course, we will create a backup beforehand and back up the corresponding servers or take a snapshot ...)

Thanks for answers

Andreas

[Lieven]

I have done all upgrades from 2.12 over 2.13, 2.14, 2.15, 2.16 to 2.18 ( I skipped 2.17)

The only thing to really watch out for in my opinion with regards to the pure upgrade path is the SQL database compatibility.

Once you are sure that all components are compatible with the new release of App Volumes, the upgrade does not take that long.

- I usually block new logons during the upgrade, VDIs with attached AppStacks/writeables should not be impacted.

- If you have more then one App Volumes instance, do one at a time, do not upgrade simultaneously

- I also usually look at differences in the logoff.bat, prestartup.bet, shell start.bat, ... between the old and the new versions of appvolumes and upload the new or adapted once to the writeable volumes. I have adapted these files and have now a set of script files that work better for the several clients I work for (see App Volumes writeable: logoff.bat, prestartup.bat, shellstart.bat, shutdown.bat, snapvol.cfg and sta...

- I am not yet upgarding to version 4.0 as I have seen and heard of too many problems with 4.0. For the moment I am sticking with 2.18

[VirtualSpence]

This operational tutorial on Tech Zone covers upgrade considerations, including the options for a full change window or rolling upgrade:

Upgrading App Volumes Manager Servers and Agents: VMware App Volumes Operational Tutorial | VMware