Microsoft Application Virtualization 5.

0 Beta Help Release Notes

To search these Release Notes, press CTRL+F. Important Read these Release Notes thoroughly before you install the Application Virtualization Management System. These Release Notes contain information that you need to successfully install the Application Virtualization Management System. This document contains information that is not available in the product documentation. If there is a discrepancy between these Release Notes and other Application Virtualization Management System documentation, the latest change should be considered authoritative. These Release Notes supersede the content included with this product.

About Microsoft Application Virtualization 5.0 Beta About the Product Documentation Protect Against Security Vulnerabilities and Viruses
To help protect against security vulnerabilities and viruses, it is important to install the latest available security updates for any new software being installed. For more information, see the Microsoft Security Web site at http://go.microsoft.com/fwlink/?LinkId=3482.

Providing Feedback
You can provide feedback, make a suggestion, or report an issue with the Microsoft Application Virtualization (App-V) Management System via a community forum on the Microsoft Application Virtualization TechCenter (http://go.microsoft.com/fwlink/?LinkId=122917). You can also provide your feedback on the documentation directly to the App-V documentation team. Send your documentation feedback to appvdocs@microsoft.com.

Known Issues with Application Virtualization 5.0 Beta

This section provides the most up-to-date information about issues with App-V 5.0 Beta. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.

The App-V Management Server has limit of 50 packages

If there are 50 or more packages in the management server, users may begin to see that the server becomes unresponsive. This is a known SQL issue that we will address in future builds. WORKAROUND Do not use more than 50 packages at a time when using the App-V 5.0 Beta management server.

The App-V Management Server console does not respect IE language settings
The current server console does not respect the computers current IE location settings, but rather the operating system language settings of the computer. WORKAROUND Adjust the operating system language settings if needed.

Client uninstall does not remove publishing refresh scheduled tasks

When uninstalling the App-V 5.0 Beta client, the publishing refresh tasks are left behind. When logging into the system after uninstall, the user will see the cmd console display on the desktop in order to execute the App-V 5.0 Beta publishing refresh scheduled task. WORKAROUND Use Windows Task Scheduler to manually remove the scheduled tasks.

No SSL support in App-V 5.0 Beta

The App-V 5.0 Beta server does not support using SSL. WORKAROUND None. For this release users will have to use HTTP or SMB.

App-V 5.0 Beta Package Converter: Packages that fail to convert are still produced
If an error occurs during package conversion, and the conversion fails, the package is still output. WORKAROUND It is important to review failure cases and remove these packages from the converter output directory, as they are likely not functional.

App-V 5.0 Beta Package Converter: Converted packages do not show up in the application list in the Client UX or Management Server UX
Currently, a converted package does not display the application list in the Client UX or Server Management UX. WORKAROUND Open the converted package for upgrade and save it. For Server UX, shortcuts and file type associations are still displayed; the only thing not displayed is the application list.

App-V 5.0 Beta Sequencer: Sequencing Microsoft Lync and Microsoft Windows Live produces error An attempt to stop the monitoring session failed
WORKAROUND During monitoring, delete the following registry key: Microsoft Lync: HKCU\Software\Microsoft\Tracing\WPPMediaPerApp\CommunicatorMicrosoft Windows Live: HKCU\Software\Microsoft\Tracing\WPPMediaPerApp\WindowsLiveMessenger

App-V 5.0 Beta components (Client, Sequencer and Server) require both .Net 3.5 and .Net 4.0
To successfully install and use the App-V 5.0 Beta components, both .Net 3.5 and .Net 4.0 must be installed. . WORKAROUND Install .NET 3.5 and 4.0 on the computer that will be running the App-V 5.0 Beta components. Note: Server install will fail silently if .Net 4.0 is not present.

App-V Management Server will not load after install

Due to the multiple versions of .Net that are required, IIS is sometimes incorrectly registered in ASP.NET. Both 32-bit and 64-bit ASP.net must be registered. WORKAROUND From a command prompt, run "c:\windows\microsoft.net\framework\v4.0.30319\aspnet_regiis.exe ir for the 32-bit registration and "c:\windows\microsoft.net\framework64\v4.0.30319\aspnet_regiis.exe ir for the 64-bit version.

Sequencer GUI: View --> Show Sequencer Variables is only applicable in the Virtual File System tab.
The Show Sequencer Variables Menu item in the View menu bar item toggles on and off the ability to view sequencer variables or the actual file location. Currently it is enabled on every page in the wizard, and should only be enabled in the Virtual File System/Virtual Registry tabs. WORKAROUND Only use the "Show sequencer variables" menu item when editing the Virtual File system or Virtual registry tab.

Sequencer GUI: Advanced Edit Page - No warning to Save package if edit page is closed without saving.
In the advanced editing page of the Sequencing wizard, there is no warning to save if the user attempts to close the package without saving. WORKAROUND Ensure to manually save the package in the advanced edit screen before closing, or you will not have a completed package.

Sequencer GUI: Package Name Page - Primary Virtual Application Directory should match Application Installation Directory for best results
In the Package Name page when specifying where the Primary Application Virtual Directory is to be installed, this should match where the Sequenced application is installed, for best sequencing results. For example, if Notepad installs to C:\Program Files\Notepad; set C:\Program Files\Notepad as your Primary Virtual Directory. Alternatively, you can choose to set C:\Notepad as your Primary Virtual Application Directory, as long as during installation time, you set the installer to install to C:\Notepad. WORKAROUND For more information, see description.

Package Converter returns error: "An unexpected error encountered while converting the package: An item with the same key has already been added."
This has been known to be caused when a 64-bit virtual legacy application is converted on a 32bit OS. WORKAROUND Convert the package on a 64-bit OS.

Some IIS features may prevent the services from working correctly
One known IIS feature that will prevent the service components from working correct is WebDav, but there may be others as well. WORKAROUND We suggest that for testing purposes only the required IIS features are installed (as specified in the documentation for setting up the server).

App-V 5.0 Beta server does not support Server core.

App-V 5.0 Beta currently does not support deployment on the Server Core SKU. WORKAROUND None.

EnablePackageScripts via Group Policy

WORKAROUND If you EnablePackageScripts via Group Policy and then set EnablePackageScripts as "Not Configured", you will still see the setting as Enabled on App-V 5.0 Beta client

PackageId instead of Package Name

WORKAROUND Use PackageID instead of Package Name in user and deployment configuration files.

ADMXTemplates ship with the Sequencer installer

WORKAROUND ADMXTemplates for managing Group Policy ship as part of the Sequencer. Install a sequencer and navigate to <Install Path>\Sequencer directory to get the files.

Sequencing Office 2010

Sequencing Office 2010 is not supported in the Beta release. WORKAROUND None.

App-V Sequencer and Client Customer Experience Improvement Program(CEIP): Opt-Out not enabled
The App-V 5.0 Beta Sequencer and Client enforce the CEIP opt in for the Beta deployment. Optouts for the program are currently not enabled. 5

WORKAROUND None.

App-V 5.0 Beta Client does not install correctly on a machine with 4.6 SP1 (or earlier) or Microsoft Office Click-to-Run for Office 2010
Installing App-V 5.0 Beta Client on a machine with versions earlier than 4.6 SP2 or Microsoft Office Click-to-Run for Office 2010 is not supported. WORKAROUND Ensure 4.6 SP2 Beta client is the installed App-V version prior to installing the App-V 5.0 Beta client.

App-V Sequencer and Client Pre-requisites - latest Windows updates

The App-V Sequencer and Client require the latest windows updates as they contain updates critical to creating correctly formatted virtual application packages. (i.e KB2533623). WORKAROUND None.

App-V 5.0 Beta Supported Locales

The Beta release of App-V 5.0 is available in the following locales: English, German, Japanese, Chinese (Traditional) and Chinese (Simplified). Note: App-V Beta depends on the OS Locale settings to display the appropriate strings. Deploying OS MUI Packs and updating locale settings in Internet Explorer without updating the OS locase setting will cause App-V to not display the correct locale WORKAROUND None.

Help links in App-V 5.0 Beta do not open Help pages

The App-V 5.0 documentation is not available online. WORKAROUND The documentation is available for download on the Connect site.

Release Notes Copyright Information

Information in this document, including URL and other Internet Web site references, is subject to change without notice, and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this 6

document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2009 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, and ActiveSync are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.