VMware App Volumes 2.11 Release Notes

VMware App Volumes 2.11 Release Notes | 7 SEP 2016

Updated on: 7 SEP 2016

Check frequently for additions and updates to these release notes.

What's in the Release Notes?

The release notes include the following topics:

Key Features

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.

Top of Page

What's New in Release 2.11?

  • Support for VMware Horizon View versions 7 and 7.0.1:
    You can now deliver AppStacks and Writable Volumes to Instant Clones and Linked Clones hosted on VMware Horizon View 7.0 and VMware Horizon View 7.0.1 machines.

  • TLS 1.0 protocol communications disabled from App Volumes agent:
    All communications from the App Volumes agent are now done through TLS 1.1 and TLS 1.2 protocols. There are no configuration changes needed as the agent communicates only through the newer protocols. However, the App Volumes Manager accepts communications through the TLS 1.0 protocol to support connections from earlier agents.
  • Top of Page

    Internationalization

    VMware App Volumes product documentation is available in English for release 2.11.

    Top of Page

    Compatibility Notes

    Supported Infrastructure for App Volumes 2.11:

    • VMware ESX 5.5.x, 6.0 and vCenter (ESX/vCenter must be the same version)
    • VMware Virtual SAN 6.2
    • Horizon View 6.0.1, 6.0.2, 6.1, 6.2, 7.0, and 7.0.1
    • 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 SP1, SP2, and SP3 when App Volumes Manager is installed on Microsoft Server 2012 R2

    VMware App Volumes Agent:

    • Windows 10 (Professional and Enterprise, with Windows 10 November 2015 KB 3163018 OS Build 10586.420 applied)
    • Windows 7 SP1 32/64 bit (Professional and Enterprise, with Microsoft Hot fix 3033929 applied)
    • Windows 8.1 32/64 bit
    • Windows Server 2008 R2 and 2012 R2 for RDSH
    • Windows Server 2008 R2 and 2012 R2 for Server VDI

    Top of Page

    Resolved Issues

    The following issues were resolved in this release:

    • The Perform Search error appears when you provide unicode characters for the Organizational Unit (OU) name, while configuring Active Directory.

    • An event log error appears every 30 seconds each time you attach an AppStack on a Windows 8 or a Windows 10 machine.

    • Certain applications might lose network connectivity when delivered in an AppStack if filter drivers are installed on the machine.
      For more information, see KB 2145681

    • The App Volumes Manager does not delete entries such as datastores and virtual machines from the database after they are removed from the vCenter Server.
      As the App Volumes Manager cleans-up machines and storage locations which do not exist on the vCenter Server every 4 and 22 hours respectively, the GUI might not reflect the changes immediately.

    • The launch of applications is slow when an AppStack is attached due to slow performance of RegEnumKey operations of large registry keys.
      For more information, see KB 2145683

    • BSOD occurs when you rename a folder within a special folder in App Volumes.

    • BSOD occurs due to stack overflow when additional products with filter drivers are present in App Volumes.

    • Microsoft Office might reconfigure when delivered through an AppStack to non-English versions of Windows.

    • The allvolattached.bat script fails to run at the time of user log in.

    • The refresh operation of an AppStack fails on the App Volumes Manager.

    • Writable Volumes fail to attach on a machine when they are located on different vCenter Servers.

    • AppStacks cannot be updated when they are located in several storage locations across different vCenter Servers.

    • Expanding Writable Volumes fails on the client machine and the size does not update correctly in the App Volumes Manager UI.

    • The Windows Start menu fails to launch with AppStacks on Windows 10 machines.

    • An antivirus software cannot detect infected files on a Writable Volume.


    Top of Page

    Known Issues

    • AppStacks and Writable Volumes fail to attach on instant clone agents if the Data center name and virtual machine folder locations have non-English characters.
      Workaround: Change the Data center name and the virtual machine folder name to English.

    • The Windows Search menu fails to launch with AppStacks on Windows 10 machines.

    • BSOD occurs on 1 desktop during logon in a pool of 2000 desktops when AppStacks and a Writable Volume are attached.
      Workaround: Restart the machine or perform a delete operation to reprovision the virtual machine.

    • Some machines appear offline in the App Volumes Manager after performing the Push Image operation on a large pool of instant clone desktops.
      Workaround: Restart the machines that appear offline, or restart the App Volumes service on these machines.

    • Windows Home Editions are not supported in this release.
      Workaround: None.

    • 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.
      Workaround: None.

    • Use of Novell products with App Volumes can cause unexpected behavior. Novell products are not supported by VMware App Volumes.
      Workaround: None.

    • 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.
      Workaround: None.

    • 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.
      Workaround: None.

    • 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.
      Workaround: None.

    • Removing volumes in real-time can result in unexpected Windows behavior.
      Workaround: None.

    • 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.
      Workaround: None.

    • Renaming a datastore will result in disabled volumes which cannot be deleted using the VMware App Volumes Manager.
      Workaround: None.

    • Renaming a virtual machine will not be reflected in the VMware App Volumes database.
      Workaround: None.

    • 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.
      Workaround: None.

    • 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 App Volumes Manager, lists both the old and new names of the datastore in the Manager UI.
      Workaround: None.

    • Creation of AppStacks might fail if you use special characters such as "@:" while naming the AppStacks.
      Workaround: None.

    • 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.
      Workaround: None.

    • 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.
      Workaround: None.

    • Unable to install Chrome browser extensions from an AppStack.
      Workaround: None.

    • The RunDll error appears when you install Adobe Reader 11 on Windows 2012 R2 and 64-bit Windows 8.1 devices.
      Workaround: None.

    • vCenter configuration on App Volumes Manager using IPv6 address fails.
      Workaround: None.

    • If multi-vCenter is used and there is a shared datastore between two or more vCenters, that datastore might be displayed more than once.
      Workaround: None.