Server Application Virtualization Release Notes


Updated: May 13, 2016

Applies To: System Center 2012 R2 Virtual Machine Manager, System Center 2012 - Virtual Machine Manager

To search these Release Notes, press CTRL+F.

System_CAPS_ICON_important.jpg Important

Read these Release Notes thoroughly before you install the Microsoft Server Application Virtualization (Server App-V). These Release Notes contain information that you must have to successfully install Server App-V. This document contains information that is not available in the product documentation. If there is a difference between these Release Notes and other Server App-V documentation, the latest change should be considered authoritative. These Release Notes supersede the content included with this product.

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 website at

You can provide feedback, make a suggestion, or report an issue with the Microsoft Application Virtualization (App-V) Management System in a community forum on the Microsoft Application Virtualization TechCenter (

You can also provide your feedback about the documentation directly to the App-V documentation team. Send your documentation feedback to

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

When sequencing Team Foundation Server 2010, you receive the following error: - db backup error - file not found

When you sequence Team Foundation Server 2010 and you specify Microsoft SharePoint integration by providing a location of the Windows SharePoint Services installer, a db backup error occurs when you stop monitoring. This occurs because Team Foundation Server 2010 creates the Windows SharePoint Services databases on the remote SQL server. This is an unsupported scenario.

WORKAROUND During the monitoring phase of sequencing, follow these steps:

  1. Install the Windows SharePoint Services and configure for your environment.

  2. Install Team Foundation Server 2010 and configure it to reference the Windows SharePoint Services installation during the Team Foundation Server 2010 configuration phase.

When you remove a package that contains COM+ components the associated native registration overrides are also removed

After you remove a virtual application package that contains COM+ components, any overrides that were applied by using the native registration after you deployed the virtual application are also removed.

WORKAROUND After you remove the virtual application package, you must reapply the overrides that were applied by using the native registration.

Changing credentials of an interactive service renders the credentials noninteractive

Interactive windows services (services that can interact with the desktop) can only run as Local System. If your package has an interactive Windows Service, and if you change its credentials from Local System to another user during deployment, the service can no longer interact with the desktop. Therefore, the package might lose some of its functionality.

WORKAROUND To preserve this functionality, you should not change the credentials of interactive services.

Deleting a deployment configuration item causes the sequencer to quit unexpectedly

Server App-V automatically captures configuration items associated with a virtual application package that can be used during deployment to configure an instance of the deployed application package. After sequencing an application, these configuration items are displayed in the deployment configuration section of the sequencer console. If any of the configuration items are deleted using the sequencer console, the sequencer can crash, causing a loss of the virtual application package that was created.

WORKAROUND To delete a configuration item, you should first save your package and then manually edit the deploymentconfig.xml document. To remove an item from the file, you should delete the applicable .xml node for the required deployment configuration item.

Information in this document, including URL and other Internet website 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 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.

© 2011 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 USA. and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.