主な変更点は Horizon View 7, 7.0.1 のサポートです。
What's New in Release 2.11?
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.
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.
VMware App Volumes product documentation is available in English for release 2.11.
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
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.