VMware App Volumes 2.10 Release Notes
VMware App Volumes 2.10 Release Notes | 24 NOV 2015
Updated on: 19 February 2016
Check frequently for additions and updates to these release notes.
What's in the Release Notes?
The release notes include the following topics:
VMware App Volumes is a real-time application delivery system that enables Enterprise IT to instantly deliver applications with complete application lifecycle management. VMware App Volumes provides seamless end-user experience while reducing infrastructure and management costs.
- Real-Time Application Delivery
- Deliver or upgrade applications at scale and in seconds
- Dynamically deliver applications without interrupting users even if they are logged in
- Complete application lifecycle management (provisioning, delivery, maintenance, retirement)
- Seamless End-User Experience
- Support fully customizable desktops, with the freedom for end-users to install applications
- Persistent user experience with non-persistent economics
Top of Page
What's New in Release 2.10?
Windows 10 Support: Classic Windows 10 applications can be delivered through AppStacks to Windows 10 virtual desktops. End-users can install classic Windows applications on Writable Volumes when they are logged in to Windows 10 virtual desktops. Installation of universal applications is not supported on AppStacks and Writable Volumes. App Store applications are not supported.
Enabling vMotion: The AVM_PROTECT_VOLUMES="1" environment variable can be set on the App Volumes Manager to enable vMotion and to provide protection against accidental deletion of volumes when all ESX hosts are of version 6.0 Update 1a and 5.5 Update 3b. vMotion of Storage is not supported.
vSphere 6 Update 1 support: This release of App Volumes includes support for vSphere 6 Update 1.
Horizon 6.2 support: This release of App Volumes supports Horizon 6.2.
Storage Group management: An option to mark a storage as Not Attachable is now available. App Volumes Manager will ignore this storage while mounting volumes.
Expand existing writable volumes: Size of an existing writable volume can be expanded through the App Volumes Manager. This change will take effect after the next user login.
App Volumes templates: All App Volumes templates are now created with the volume attribute set to NODEFAULTDRIVELETTER to ensure they are not automatically assigned a letter by the Windows MountVol utility.
Top of Page
VMware App Volumes product documentation is available in English for release 2.10.
Top of Page
Supported Infrastructure for App Volumes 2.10:
- VMware ESX 5.5.x, 6.0 and vCenter (ESX/vCenter must be the same version)
- Horizon View 6.0.1, 6.0.2, 6.1, and 6.2
- Citrix XenDesktop 5.5, 5.6, and 7.X
- Citrix XenApp 6.5 and 7.x
VMware App Volumes Manager:
- Microsoft Server 2008 R2 and 2012 R2
- Microsoft SQL Server/Express 2008
- Microsoft SQL Server 2012 when App Volumes Manager is installed on Server 2012 R2
VMware App Volumes Agent:
- Windows 10 (Professional and Enterprise)
- Windows 7 32/64 bit
- Windows 8.1 32/64 bit
- Windows Server 2008 R2 and 2012 R2 for RDSH
- Windows Server 2008 R2 and 2012 R2 for VDI
Top of Page
The following issues were resolved in this release:
- When using MS Office on the base image, some of the applications coming from an AppStack might re-configure.
- Icons created by an application might remain after the AppStack is unassigned.
- Shared datastores might appear more than once depending on the number of vCenters configured.
- When establishing concurrent connections from 2000 Horizon View VDI to a single App Volumes Manager for multiple virtual centers, the AppStack attachment state between vCenter and AppVolumes Manager can be different.
- When establishing concurrent connections from more than 1700 VDI desktops in multiple virtual centers to the AppVolumes Manager, Writable Volumes and AppStacks fail to attach randomly from some VDI sessions.
- Writable Volumes that are using template_profile_only or template_uia_plus_profile might not handle profiles as expected.
- When a specific domain controller host is specified during Active Directory configuration, the connection is established to that domain controller instead of the domain trust.
- Welcome UI appears every time you log into App Volumes Manager on a Windows 8.1 machine.
- Tortoise SVN application captured on an AppStack fails to connect to the server.
- App Volumes does not support Active Directory groups with more than 1500 users.
- Writable volumes fail to get detached after a user logs off a virtual machine.
- Drive letters are assigned to AppStacks when users log in to their desktops which interrupts the network drive mappings through GPO.
Top of Page
- Windows Home Editions are not supported in this release.
An Outlook search might generate a configuration popup when search indexing is enabled.
Workaround: Disable the Windows Search service and searching will work without search indexing.
Apple iTunes contained in an AppStack must be assigned prior to user login. Dynamic "real-time" assignment for this application is not supported.
Use of Novell products with App Volumes can cause unexpected behavior. Novell products are not supported by VMware App Volumes.
- If a user logs in to a virtual desktop with a Writable Volume and a user later logs in without a Writable Volume, a pop-up appears.
Workaround: Refresh or reboot after each logout when multiple users log into the same virtual desktop.
Microsoft QuickBooks can fail to correctly install if provisioned in the same AppStack with Microsoft Office 2010 or 2013.
Workaround: Provision Microsoft QuickBooks and Microsoft Office 2010, or 2013 in different AppStacks.
- Recommended scale limit is of 1000 concurrent VM connections to a single App Volumes Manager when using multi vCenter mode.
- If Adobe Reader AppStack is provisioned in virtual machine with Windows OS installed on a drive other than C, and the AppStack is attached to the a virtual machine with Windows OS installed on C drive, then all PDF files viewed in Windows Explorer will not show the Adobe Reader icon and cannot be opened by simply clicking on the icon. You can still open Adobe Reader.
- After completing provisioning on Horizon RDS virtual machine, a manual reboot is required. After provisioning is complete, the virtual machine reboots automatically. If nothing happens after clicking OK in the provisioning dialogue after several minutes, then reboot manually. Once you login again, the provisioning process will be completed as normal.
- Removing volumes in real-time can result in unexpected Windows behavior.
- If an AppStack is created in the background and it fails because an AppStack already exists with the same name on that datastore, the background job will be retried 5 times before being removed.
- Renaming a datastore will result in disabled volumes which cannot be deleted using the VMware App Volumes Manager.
- Renaming a virtual machine will not be reflected in the VMware App Volumes database.
- When a new font is installed on a virtual machine with an attached writable volume, it does not display in the control panel, but can be used until logoff.
Workaround: After you install a new font, copy it to the C:\Windows\fontsCV folder for the font to be visible and usable in the applications.
- When a user with assigned Writables logs off a virtual machine and a new user with assigned Writables subsequently logs on to the same virtual machine, a message asking the user to restart the machine appears. Restarting the virtual machine displays a black screen and makes the virtual machine unusable.
Workaround: Ensure that a virtual machine is rebooted after every user logoff.
High CPU consumption is observed during provisioning of applications on 64-bit Windows 10 machines.
Once you provision a Horizon View client on a 64-bit agent machine, the subsequent provisioning of Horizon View client on the same machine fails.
Workaround: Use a clean 64-bit agent machine for provisioning the client.
Storage Group replication fails if the names of the datastores are identical between different vCenter servers.
Workaround: Rename the datastores to ensure that the names are unique.
Renaming a datastore from a vCenter server that is configured for use in AppVolumes Manager, lists both the old and new names of the datastore in the Manager UI.
Creation of AppStacks might fail if you use special characters such as "@:" while naming the AppStacks.
When VHD In-Guest connection mode is selected during the first instance of App Volumes Manager configuration, the Summary tab displays the default storage path appended with a redundant “|” character.
When you use special characters such as “%” or “\” for a storage name, the storage list incorrectly displays “%25” and “%5c” for the names in places such as the Default Storage Location list on the Storage tab.
Unable to install Chrome browser extensions from an AppStack.
RunDll error appears when you install Adobe Reader 11 on Windows 2012 R2 and 64-bit Windows 8.1 devices.
vCenter configuration on App Volumes Manager using IPv6 address fails.
If multi-vCenter is used and there is a shared datastore between two or more vCenters, that datastore might be displayed more than once.