VMware App Volumes 2.12 Release Notes | 08 DEC 2016
Check frequently for additions and updates to these release notes.
What's in the Release Notes?
The release notes for App Volumes 2.12 include the following topics:
- Key Features
- What's New
- System Requirements
- Resolved Issues
- Known Issues
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.
For more information, see VMware App Volumes documentation.
The latest release of App Volumes includes many enhancements that improve end user login times, security, Microsoft Office support, and Windows 10 support.
Performance improvements for faster user login and application launch
- Optimized handling of application registry hives by not blocking end-user login.
- Addressed a bug that caused the App Volumes agent to scan Appstacks and Writable Volumes before the Windows explorer shell is available.
Integration with Active Directory
- You can manage application and writable volumes assignments across multiple Active Directory domains and forests.
- You can add multiple domain controllers that App Volumes Manager leverages to query Active Directory users, computers, groups, and OUs.
- You can move and retain application and writable volumes assignments even when Active Directory objects are moved out of an OU or Group.
- By default, communication between App Volumes Manager and agent occurs over HTTPS. The App Volumes Manager is installed with a port number of 443. See KB 2148178 for more information.
- By default, certificate validation is required for all communication between the App Volumes Manager and vSphere. See the SSL section in the App Volumes User Guide for detailed information.
- Ruby version in App Volumes Manager is upgraded to 2.2.4.
Support for Delivering Office 365 (Office 2016) Applications Through AppStacks
You can deliver Office 365 (Office 2016) applications through AppStacks. See KB 2146035 for detailed information.
Support for Windows 10 Anniversary Update (AU) build 1607
You can now deliver applications, user-installed applications, and profiles through AppStacks and Writable Volumes to Windows 10 version 1607 (Windows 10 Anniversary Update) on Current Branch, Current Branch for Business and Long-term Service Branch. Windows 10 version 1511 is not supported with App Volumes 2.12. See KB 2148177 for more information.
Tech Preview Features
See the following VMware Knowledge Base articles to learn about the Tech Preview features that are included with App Volumes 2.12.
- Centralized Log Collection - You can redirect logs from all App Volumes Managers and agents to a central location. This helps in uploading the logs more easily to VMWare Support and also makes troubleshooting easier. See KB 2148180 for more information.
- Read-only Administrator - A read-only administrator can only log in to App Volumes Manager and view the App Volumes configuration details but cannot make any modifications. See KB 2147984 for more information.
- Asynchronous Mounting - You can configure asynchronous mounting of AppStacks on App Volumes Manager to improve scalability. See KB 2147985 for more information.
Note - The Tech Preview features and capabilities are not supported for production deployment, rather they are available as a preview of potential upcoming innovations to test in a lab or UAT environment. You can provide feedback to improve these features through VMWare Communities.
AppVolumes Manager Nginx supports TLSv1.0
The App Volumes Manager 2.12 continues to allow communication using TLSv1.0. However, future releases of App Volumes Manager will not support TLSv1.0 which will affect older agents (App Volumes 2.11 and earlier).
System requirements for App Volumes 2.12
Ensure that your system meets the following software and hardware requirements before you install App Volumes 2.12.
App Volumes Manager supports different versions of the Microsoft SQL database.
- SQL Server 2012 SP1, SP2, and SP3 (whenApp Volumes Manager is installed on Microsoft Server 2012 R2), Express, Standard, and Enterprise editions
- SQL Server 2008 R2 SP2, Express, Standard, Enterprise, and Datacenter editions
- SQL Server 2014 SP1 (supported on App Volumes 2.12 and later)
- For High Availability, App Volumes supports the following database features :
- SQL Server Clustered Instances
- SQL Server Mirroring
Use App Volumes Manager on one of the following supported browsers:
- Internet Explorer 9 or later
- Mozilla Firefox 28 or later
- Safari 5.1 or later
- Google Chrome 21 or later
Infrastructure and Networking Requirements
Infrastructure and networking requirements for App Volumes include requirements for App Volumes Manager, agent, and Active Directory.
|App Volumes Manager||
|App Volumes Agent (client OS)||
Note: Disable the GPO Control Read and Write Access to Removable Devices or Media option.
|App Volumes Agent (RDSH)||
|VMware software for VMDK Direct Attached Mode (Preferred)||
|SMB file share if using VHD mode||
|Active Directory||Microsoft Active Directory domain, 2003 functional level or
later. Read-only account access.
|App Volumes Manager||Agent and Manager Communications||
|App Volumes SQL database||Database Communication||TCP 1433 (SQL)|
The following issues were resolved in this release:
- Assignments were not honored when the organizational unit (OU) or group membership of users or computers was changed.
- App Volumes agent would scan Appstacks and Writable Volumes before the Windows explorer shell was available.
- When a user logs in to the virtual machine and AppStacks are attached, the Windows Start menu and search menu fail to launch. This is specific to Windows 10.
- 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.
- Microsoft Office 2016 applications become unresponsive after a few minutes of being launched on Windows 10 with Writable Volume attached.
- AppVolumes now enables users to handle Alternate Data Stream.
- Java fails to render with Microsoft Office AppStack attached.
- Login to App Volumes Manager fails if the user name contains space.
- App Volumes Manager occasionally goes in to a deadlock state after aborting a query which is running slow.
- If a file from the system volume is deleted when a writable volume is attached, App Volumes Manager returns false success instead of "Access_Denied".
- Users who are from the same forest but in an alternate domain as the domain configured in App Volumes Manager are unable to login.
- svservice aborts when connecting to App Volumes Manager after HttpInitializeRequest:WinHttpSendRequest failed (error 12175).
- Windows 10 Start button and Cortana become unresponsive when WritableVolume is attached after recomposing the floating pool.
- If you select "Delayed creation of Writable Volume" when creating Writable Volumes for a nested group, App Volumes Manager creates WritableVolumes immediately for all the users in parent groups. Only Writable Volumes creation for users at the deepest group level is delayed.
- A VM with an Appstack attached fails to report the correct VM state to VMware Horizon View
- When a user is moved to another organizational unit (OU), the AppStacks or WritableVolume assigned to him is no longer available to him when he logs in to the VM.
- FlexEngine.exe is invoked by the allvolattached_shellstarted.bat file. In previous releases of App Volumes, users had to update the batch file separately to ensure that UEM did not throw an error when invoking FlexEngine.exe with App Volumes. With App Volumes 2.12, the batch file has been updated to invoke FlexEngine.exe with –UEMRefreshShortcuts. FlexEngine.exe is invoked after the user logs in and all volumes have been attached.
- A black screen with the error message Connection Error Unable to contact App Volumes Manager is displayed if there is a mismatch in the SSL settings in the App Volumes Manager and agent, and App Volumes may not function correctly. See KB 2148178 for more information.
- Error when expanding writable volume in App Volumes Manager
- Storage locations in Storage Groups for In-guest services shows disk usage as (null of null).
- AppStacks and Writable Volumes fail to attach on instant clone agents if the data center name and virtual machine folder location have non-English characters.
- BSOD occurs on 1 desktop during log on, in a pool of 2000 desktops when AppStacks and Writable Volumes are attached.
- Mass deletion of writable volumes may result in a small subset of the volumes still remaining in the datastore.
- An Outlook search might generate a configuration pop-up when search indexing is enabled.
- Apple iTunes contained in an AppStack must be assigned before a user logs in to a virtual machine. Dynamic real-time assignment for this application is not supported.
- Novell products are not supported by VMware App Voumes. Use of Novell products with App Volumes can cause unexpected behavior.
- If a user logs in to a virtual desktop with a Writable Volume attached, and a different user later logs in without having a Writable Volume attached, a pop-up appears.
- Microsoft QuickBooks can fail to correctly install if provisioned in the same AppStack with Microsoft Office 2010 or 2013.
- Recommended scale limit is of 1000 concurrent VM connections to a single App Volumes Manager when using multi vCenter mode.
- If an Adobe Reader AppStack is provisioned on a virtual machine with Windows OS installed on a drive other than C drive, and the AppStack is attached to a virtual machine with Windows OS installed on C drive, then all PDF files viewed in Windows Explorer will not display the Adobe Reader icon and the PDF files cannot be opened by 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.
- 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 results in disabled volumes which cannot be deleted using the App Volumes Manager.
- Renamed virtual machine is not reflected in the App Volumes database.
- When a user with an 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.
- High CPU consumption is observed during provisioning of applications on 64-bit Windows 10 machines.
- 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 App Volumes Manager.
- 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.
- Unable to install Chrome browser extensions from an AppStack.
- The 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 multiple vCenters are used and there is a shared datastore between two or more vCenters, that datastore might be displayed more than once.
Workaround: If you disable SSL in the App Volumes agent, ensure that you have enabled HTTP connection in App Volumes Manager.
When you configure a machine manager as an In-guest VHD in App Volumes Manager, create a writable volume for a user, and then try to expand the volume, the writable is not expanded. The following error is displayed: Error: "Error expanding writable volume <user>"
When you configure In-Guest services, add file shares, and create storage groups, the storage locations show (null of null) as disk usage, even though the information is unavailable.
Workaround:Change the data center name and the virtual machine folder name to English.
Workaround: Restart the machine or perform a delete operation to reprovision the virtual machine.
Workaround: After you delete the volumes, click Rescan in the App Volumes Manager. The remaining volumes are seen in the App Volumes Manager. Select the volumes again and delete them.
Workaround: Disable the Windows search service to enable search to work without indexing.
Workaround:Refresh or reboot after each logout when multiple users log into the same virtual desktop.
Workaround: Provision Microsoft QuickBooks and Microsoft Office 2010, or 2013 in different AppStacks.
Workaround: Reboot the virtual machine after every user logoff.
VMware App Volumes product documentation is available in English for release 2.12.