- 1 Resolved Issues
- 1.1 Download:
- 1.2 Related Posts:
- 1.2.1 What is VMware App volumes?
- 1.2.2 VMware App Volumes Components
- 1.2.3 System Requirements for App Volumes?
- 1.2.4 VMware App Volumes documentation
- 1.2.5 VMware App Volumes, Installation & Configuration
- 1.2.6 VMware App Volumes – How to Create a New App Stack?
- 1.2.7 VMware App Volumes – How to Assign and unassign an appstack?
- 1.2.8 VMware App Volumes – About Writable Volumes?
- 1.2.9 VMware App Volumes snapvol.cfg – Explained
- 1.2.10 VMware App Volumes – Troubleshooting?
- 1.2.11 Introducing VMware AppVolume 3.0 and whats new ?
- 1.2.12 Install and Configure VMware Appvolumes 3.0
- 1.2.13 App Volumes Toolbox – VMware Flings
- 1.3 Related
The most awaited moment is finally arrived; VMware today announced the general availability of App Volumes 2.11. This new release enables Horizon 7 customers to take advantage of Instant Clones in conjunction with App Volumes. While the release of App Volumes 2.11 is designed to support Instant Clone technology in conjunction with VMware Horizon 7, VMware is also working to help customers optimize app delivery and user management in other VDI platforms like Citrix XenDesktop.
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.
Below is the Compatibility matrix for App Volumes v2.11.
|Infrastructure||AppVol manager||AppVol Agent|
|VMware ESX 5.5.x, 6.0 and vCenter (ESX/vCenter must be the same version)||Microsoft Server 2008 R2 and 2012 R2||Windows 10 (Professional and Enterprise, with Windows 10 November 2015 KB 3163018 OS Build 10586.420 applied)|
|VMware Virtual SAN 6.2||Microsoft SQL Server/Express 2008||Windows 7 SP1 32/64 bit (Professional and Enterprise, with Microsoft Hot fix 3033929 applied)|
|Horizon View 6.0.1, 6.0.2, 6.1, 6.2, 7.0, and 7.0.1||Microsoft SQL Server 2012 SP1, SP2, and SP3 when App Volumes Manager is installed on Microsoft Server 2012 R2||Windows 8.1 32/64 bit|
|Citrix XenDesktop 5.5, 5.6, and 7.X||Windows Server 2008 R2 and 2012 R2 for RDSH|
|Citrix XenApp 6.5 and 7.x||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.
Product Documentation: Click Here
Download AppVol 2.11: Click Here
In my next blog , I will guide you through the installation and configuration of App Volumes 2.11. Please stand by.
I hope this is informative for you. Thanks for Reading!!!. Be Social and share it in social media, if you feel worth sharing it.
VMware App Volumes – How to Create a New App Stack?