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.
Consider the following scenario:
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.
To work around this problem, change the Deployment Type to refer to the current .sft file manually.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Can you not do the following :
open up the sequencer and select Tools and Options. In the general tab untick Append package Version to Filename. S
Now open the package for an upgrade. Make your changes and save the package. The SFT file name will now be the same. and upload to SCCM.
nice app how secure is the virtualization in the cloud when running on server 2012 as your server platform ? i have worked on server 2008 and I have read the data sheet and the white paper for server 2012 I am currently studying busy with my n+ and well have worked on the server platform but from what I have seen on the datasheet
server 2012 looks quite solid.