VMware

VMware App Volumes 2.9 Release Notes

VMware App Volumes 2.9 | 15 June 2015

 

This release notes includes 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.

  • 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.9

  • Support for application deployment to physical machines: You can now deploy App Stacks to physical endpoints under the following constraints:
    • Constant network connection is required
    • Automatic Windows Updates must be disabled
    • Operating System on the physical endpoint must be non-persistent, streamed, or both
    • Any updates to the operating system should not be performed with App Stacks detached
  • Support for physical endpoints and writables volumes: This is provided only under the following constraints:
    • Constant network connection is required
    • Automatic Windows Updates must be disabled
    • Operating System on the physical endpoint must be non-persistent, streamed, or both
    • Any updates to the operating system should not be performed with writable volumes detached
  • Support for profiles on writable volumes:
    • Leveraging writable volumes for user profile delivery and storage will continue to be supported.
  • Multi vCenter Configurations: Additional vCenter Machine Managers may be added at any time if vCenter server is selected as the first configured Machine Manager. Configured storage references will include storage from all vCenter Machine Managers.

Internationalization

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

Top of Page

Compatibility Notes

Supported Infrastructure for App Volumes 2.9:

  • VMware ESX 5.0.x, 5.1.x, 5.5.x, 6.0 and vCenter (ESX/vCenter must be the same version)
  • Horizon View 5.x, 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 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

VMware App Volumes Horizon View Broker Integration Service:

  • Horizon View 6.0.1, 6.0.2, and 6.1

Top of Page

Resolved Issues

The following issues were resolved in this release:

  • Active Directory Domain Controller unable to accept connection from App Volumes Manager due to multiple connections that are open while searching Active Directory objects.
  • Writable Volumes for users are not detached when users log off and log on quickly.
  • AppStacks that are part of a configured Storage Group are not detached during user logoff.
  • Deploying Visio 2010 through AppStack with Microsoft Office 2010 in the base image causes Visio activation.
  • Multiple instances of deleted files exist in the Recycle Bin when AppStacks are attached.
  • F1 key fails to load the Help page when Microsoft Visio is deployed through AppStack.
  • Citrix Receiver fails to launch when deployed through an AppStack.
  • After capturing an application which contains a printer as part of the installation (Adobe Acrobat), the printer redirection does not work when this AppStack is attached.
  • Replication of AppStack metadata files fails between data stores when using Storage Groups.

Top of Page

Known Issues

  • Windows Home Editions are not supported in this release.
  • An Outlook search might generate a configuration popup when search indexing is enabled. 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.
  • When using MS Office on the base image, some of the application coming from an AppStack might re-configure.
  • Use of Novell products with App Volumes can cause unexpected behaviour. Novell products are not supported by VMware App Volumes.
  • Icons created by an application might remain after the AppStack is unassigned.
  • Virtual desktops should be rebooted/refreshed on logout. If a user logs in with a writable volume and a user later logs in without a writable volume, a popup will occur. Refresh or reboot after each logout when multiple users can 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. As a workaround, provision Microsoft QuickBooks and Microsoft Office 2010, or 2013, in different AppStacks.
  • Shared datastores might appear more than once depending on the number of vCenters configured.
  • Recommended scale limit of 1000 concurrent VM connections to a single AppVolumes Manager when using multi vCenter mode.
  • When establishing concurrent connections from 2000 Horizon View VDI to a single AppVolumes 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.
  • When the Manager is uninstalled, existing AppStacks and user writable volumes might still be attached to computers. Since these attachments cannot be managed after uninstall, all existing attachments will be detached prior to the actual uninstall. This includes all Writable Volumes and AppStacks that are attached to computers managed by the Manager.
  • An Outlook search might generate a configuration popup when search indexing is enabled. Disable the Windows Search service and searching will work without search indexing.
  • 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.
  • On VMware App Volumes Manager side, under AppStacks application list, all names and versions will be shown correctly, where some of application icons might not be displayed correctly.
  • 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.
  • Writeable volumes that are using template_profile_only or template_uia_plus_profile might not handle profiles as expected. Run the reg.exe add HKLM\SYSTEM\CurrentControlSet\services\svservice\parameters /t REG_DWORD /v VolDelayLoadTime /d 0 / command on the target OS to fully support virtualizing the user profile.