VMware

VMware App Volumes v2.5.2 Release Note

Released 3 February 2015

Last Updated: 30 January 2015

This release note include the following topics:

Key Features

VMware App Volumes is a real-time application delivery system that enables 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.5

This release of VMwareApp Volumes v2.5.x contained the following new features:

  • Horizon View integration for better performance.
  • Multiple templates for writable volumes for additional control over user installed data, applications and user profiles.

Top of Page

Internationalization

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

Top of Page

Compatibility Notes

Supported Platforms:

  • VMware ESX 5.0.x, 5.1.x, 5.5.x and vCenter (ESX/vCenter must be the same version).
  • Horizon View Integration Broker Service 6.0.1
  • Citrix XenDesktop 5.5 and 5.6
  • Citrix XenApp 6.5

Manager Specific Platforms:

  • Microsoft SQL Server/Express 2008
  • Windows 2008 R2

Angent Specific Platforms:

  • Windows 7 32/64-bit for VDI
  • Windows 2008 R2 for Published Applications

Top of Page

Binaries

The following shows the relative file version to product version for each binary file.

  • Release-Agent-Build-32\SvCapture32.exe
    • File version: 2.5.0.0
    • Product version: 2.5.0.0
  • Release-Agent-Build-32\svdriver.sys
    • File version: 2.5.2.0
    • Product version: 2.5.2.0
  • Release-Agent-Build-32\svservice.exe
    • File version: 2.5.0.0
    • Product version: 2.5.0.0
  • Release-Agent-Build-64\SvCapture64.exe
    • File version: 2.5.0.0
    • Product version: 2.5.0.0
  • Release-Agent-Build-64\svdriver.sys
    • File version: 2.5.2.0
    • Product version: 2.5.2.0
  • Release-Agent-Build-64\svservice.exe
    • File version: 2.5.0.0
    • Product version: 2.5.0.0
  • Release-Manager-Build-32\BrokerService.exe
    • File version: 2.5.2.4
    • Product version: 2.5.2.4
  • Release-Manager-Build-32\CVManager.exe
    • File version: 2.5.2.5
    • Product version: 2.5.2.5
  • Release-Manager-Build-32\CVPowerShell.exe
    • File version: 2.5.2.20
    • Product version: 2.5.2.20

Top of Page

Resolved Issues

The following issues were resolved in this v2.5.2 release:

  • Fixed an issue with the "override existing database (if any)" option during installation. Now a new database is created only if the option is selected in the gui during the installation process.
  • BullZip no longer fails installation during provisioning.
  • Windows Side-By-Side (WinSXS) errors during provisiong related to Visual C++ Redistributable have been fixed.
  • Users are now nable to published applications through Horizon RDS located in an AppStack.
  • Citrix receiver can be provisioned in an AppStack.
  • Environment variable PATH is correctly merged during a user session.

Top of Page

These issues were resolved in the v2.5.1 release:

  • Broker Integration Service no longer fails during installation.
  • 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.

Top of Page

Known Issues

  • Windows Home Editions are not supported in this release.
  • There is a mistake in the App Volumes v2.5 User's Guide. The user guide wrongly states in section 5 that the agent must be installed on a virtual machine running Windows 7 64 or 32 bit, Windows 8, or Windows Server 2008 R2. Windows 8 is not is not a supported OS for App Volumes 2.5.x.
  • 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.
  • 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).
  • 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.