KB: Changes to an App-V application are not included when deployed using System Center 2012 Configuration Manager

Artikel
08/07/2012

Here’s a new Knowledge Base article we published. This one talks about an issue where changes to an App-V package may not get delivered when the app is deployed using ConfigMgr 2012.

=====

Symptoms

Consider the following scenario:

You create a Microsoft Application Virtualization (App-V) application.
You deploy the source for the application to a System Center 2012 Configuration Manager distribution point.
You change the application by using the App-V Sequencer.
You deploy the content for the updated application to the distribution point.

In this scenario, when users run the application, your changes are not included in the application.

Cause

This problem occurs because the App-V Sequencer saves the virtual application's SFT file (.sft) using a different name when changes are saved for the application. For example, if your virtual application is named MyApp.sft, the App-V Sequencer will save the changed application as MyApp_2.sft. Without manual adjustment, the Deployment Type for the App-V application will still refer to the original .sft file name.

Workaround

To work around this problem, change the Deployment Type to refer to the current .sft file manually.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

Because the file name changes when you update an App-V application, Binary Delta Replication is not used to download the updated content to the clients. Binary Delta Replication is possible only when you work with two versions of a file that have the same name.

=====

For the most current version of this article please see the following:

2683934 - Changes to an App-V application are not included when deployed using System Center 2012 Configuration Manager

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter :

The Forefront Server Protection blog: https://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/

Freigeben über