VMware

VMware App Volumes 2.7 Release Notes

VMware App Volumes 2.7 | 28 April 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

What's New in Release 2.7

This release of VMwareApp Volumes 2.7 includes the following new features:

  • Storage Group Distribution Strategy : The Spillover strategy has been removed as this strategy fills up a storage using actual storage size and not the provisioned size.
  • Editing a Storage Group - A new Edit button has been added which now allows you to edit the Storage Group.
  • Rescanning a Storage Group - You can now rescan a Storage Group. The operation contacts the hypervisor and updates storage information metadata such as free space and overall capacity. It also adds any new storage that make the prefix.
  • Trusted Domain Credentials - An additional set of credentials can be provided to be used when connecting to any trusted Active Directory domain. This enables the use of additional domains that have one-way trusted relationships.
  • Active Directory Synchronization - New Sync buttons have been added which allow you to manually synchronize all users and computers with Active Directory.
  • App Stacks and Writable Volumes in Unreachable and Creating states - You can now delete App Stacks and Writable Volumes that are in Unreachable or Creating states.
  • Direct-To-Host Mounting - When configuring Direct-To-Host mounting using the vCenter, you will no longer be prevented from saving the ESX credentials if they are not valid, or not been validated on all hosts visible to vCenter.
  • Agent access to VHD - A new featue in the In-Guest mode is added where the Agents are only granted access to a VHD volume directly before the Agent can mount the file.
  • System Messages - An error is displayed in System Messages when an Agent fails to attach a VHD. This occurs when the App Volumes Manager is configured in the In-Guest mode. An error is also recorded in the Windows Event Viewer.
  • Upload Pre-packaged VHD templates - You can upload pre-packaged VHD templates using the Upload Prepackaged Volumes button during storage configuration.
  • API Login - New POST /cv_api/sessions route has been added for API login. The parameters are username and password. Once this method is used for login, the CSRF tokens are not needed for subsequent requests.
  • API Logout - New DELETE /cv_api/sessions route has been added for API logout.
  • Deleting Assignments API - The API used to delete assignments has changed from POST /cv_api/assignements to DELETE /cv_api/assignments.
  • Security Session Token - The Security Session token is re-created during UI and API login requests.
  • Security HTTP Server - The Security HTTP Server no longer accepts RC4 or EXPORT ssl ciphers.

Internationalization

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

Top of Page

Compatibility Notes

Supported Infrastructure for App Volumes 2.7:

  • VMware ESX 5.0.x, 5.1.x, 5.5.x and vCenter (ESX/vCenter must be the same version)
  • Horizon View 5.x, 6.0.1, 6.0.2, and 6.1
  • Citrix XenDesktop 5.5, 5.6, and 7.x
  • Citrix XenApp 6.5

VMware App Volumes Manager:

  • Microsoft Server 2008 R2 and 2012 R2
  • Microsoft SQL Server/Express 2008
  • Microsoft SQL Server 2012 when App Volumes 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

Resolved Issues

The following issues were resolved in this release:

  • Firewall policies and printer service are reloaded once after all volumes are attached and again when all volumes are removed during logout.
  • Added a new registry value VolDelayLoadTime under can be used to delay loading of AppStacks until after user login to avoid impacting login time.

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.
  • After an AppStack is attached and functions, the Event Viewer might show BitLocker error.
  • Use of Novell products with App Volumes can cause unexpected behavior. Novell products are not supported by VMware App Volumes.
  • 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:, 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.
  • When using MS Office on the base image, some of the application coming from an AppStack might re-configure.
  • 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.
  • 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 click "OK" in the provisioning dialogue after several minutes, then reboot manually. Once you login again, the provisioning process will be completed as normal.
  • The use of Internet Explorer in an Appstack is not supported due to the tight OS integration and dependancies it is recommended to use an application isolation technology such as VMware ThinApp. VMware App Volumes can be then utilized for delivery of the isolated application package.
  • Removing volumes in real-time can result in unexpected Windows behavior.
  • 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.
  • 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.
  • On user based assignments with non-persistent desktops some applications might re-configure themselves (for example, Skype or iTunes).
  • 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.
  • 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 detached prior to the actual uninstall. This includes all writable volumes and AppStacks that are attached to computers managed by the Manager.