How to in place upgrade App Volumes 2.12 to 2.12.1

Yes! App Volumes 2.12.1 was just released and it allows Upgrades!

What’s New in This Release

The latest release of App Volumes includes an improved upgrade process, Writable Volumes exclusions, and important security fixes.

  • Improved Upgrade Process
    You can now upgrade from App Volumes 2.12 to App Volumes 2.12.1 without uninstalling your existing 2.12 installation. Upgrading from versions earlier than 2.12 still requires App Volumes Manager and agent binaries to be uninstalled before proceeding with 2.12.1 installation.
    Note – As a best practice with any system change, ensure that you have a backup of your systems including security cerificates and configuration files before performing an upgrade. Customizations to App Volumes outside the normal configuration interface may not be retained.
  • Writable Volumes Exclusions
    An App Volumes administrator can exclude specific file paths or registry keys from being overwritten, thus excluding them from being persisted across sessions.

Miscellaneous Updates

  • Nginx configuration file has been upgraded.
  • You can now use non-ASCII characters when naming the datastore in App Volumes Manager.
  • The App Volumes Manager remembers and displays the last selected domain.
  • The Pending Activities tab in App Volumes Manager displays the background jobs that are in progress in App Volumes.

Resolved Issues

  • You can grant permissions to members of groups from trusted domains (that are configured in the Active Directory) to log in to App Volumes Manager.
  • In some cases, deleting items from the Windows Desktop would result in the item being deleted without moving it to the Recycle Bin.
  • Storage locations in Storage Groups for In-guest services would earlier show disk usage as (null of null) even when information was unavailable.
  • App Volumes Manager displays Unable to save user message if the Allow non-domain entities was checked during manager installation, and the agent was installed in a non-domain joined VM.
  • Fixed memory utilization issue in agent driver.
  • Errors seen when deleting an empty folder after provisioning and deploying AppStacks have been resolved.
  • When using In-Guest VHD, expand writable volume is not supported. This button is no longer visible when App Volumes is configured to use In-Guest VHD.
  • Duplicate operating system entries were displayed after upgrading App Volumes Manager.
  • User was unable to preview Word document in Outlook when Office 2016 was installed in an AppStack, and the AppStack was attached as a machine-based assignment. Something went wrong error message would be displayed after a user logged in to an RDSH server and tried to preview a Word document from Outlook.

So below in comic version on how to upgrade:

1. Before you start always have a proper backup!

Mount or unpack iso to start the upgrade.

Agree with the terms.

Choose, install App Volumes Manager

A new setup window will pop up and see that it will perform an upgrade from 2.12.0.69 to 12.12.1.103. If you try to upgrade from 2.11 or lower you will get a warning to remove the installation first.



During the upgrade it will backup and import settings like the certificate and odbc



Presto upgrado.

 

1 thought on “How to in place upgrade App Volumes 2.12 to 2.12.1

  1. Pingback: App Volumes 2.12.1 vCenter certificate verify failed - vDrone

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.