What's in the Release Notes?
The release notes for App Volumes 2.12.1 includes the following topics:
About VMware App Volumes
VMware App Volumes provides a system to deliver applications to desktops through virtual disks. Applications are bundled in AppStacks and delivered by attaching a standard VMDK file to a virtual machine. You can centrally manage the applications with the App Volumes Manager and there is no need to modify the desktops or individual applications. Applications delivered by using App Volumes look and feel natively installed and you can update or replace the applications in real time.
All applications are provisioned during login time and App Volumes enables users to have a persistent user experience wherein users can install their own applications and have them persist across sessions.
App Volumes is intended for use on non-persistent desktops.
For more information, see the VMware App Volumes documentation.
See the App Volumes 2.12 release notes for information about the 2.12 release of App Volumes.
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.
You can upgrade the App Volumes agent by using the App Volumes installer or by performing a silent install. You cannot upgrade by clicking the .msi file.
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.
- 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.
- 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.
- Pressing Alt+F11 when using MSOffice applications, such as Word and Excel, that is installed in an AppStack, is broken when used with a 32-bit version of Office 365 on a 64-bit Windows OS. Alt+F11 normally brings up a Visual Basic for Applications screen when used with Office applications. In App Volumes 2.12.1 however, a message Could not open macro storage is displayed instead. Note that this issue does not arise when Office 365 is deployed natively.
- You may face printer issues when using App Volumes with Windows 10.
Workaround: See https://kb.vmware.com/kb/2150382 for details.
- After a user provisions a large instant clone pool, a few machines are seen to be offline in App Volumes Manager. When the user tries to connect to one of these "offline" machines, a virtualization is disabled message is displayed.
Workaround: Log out of the desktop and log back in; the AppStacks and Writable Volumes are available again.
- An Outlook search might generate a configuration pop-up when search indexing is enabled. Sometimes no error or pop-up is displayed, and search functionality fails.
Workaround:Log in to your App Volumes instance as an administrator and disable the Windows Search service to enable search to work without indexing. See https://kb.vmware.com/kb/2149799 for detailed information.
- If you are using a persistent VDI, all modifications made during the user sessions are lost when you log off the App Volumes agent. You might also encounter application compatibility issues over time.
- Chrome drive letter settings must have a non-persistent environment to work correctly.
Workaround: Refresh or delete your VM after you log off from App Volumes. See https://kb.vmware.com/kb/2128266 for detailed information.
- Recycle bin may show multiple copies of deleted items.
VMware App Volumes 2.12.1 product documentation is available in English.