Configuration Manager Support for App-V 5.0 SP2

  • Makale

It has recently been announced that Configuration Manager now supports App-V 5.0 SP2 with either of the following:

Cumulative Update 4 for System Center 2012 Configuration Manager SP1
https://support.microsoft.com/kb/2922875/en-us

Or

Cumulative Update 1 for System Center 2012 Configuration Manager R2
https://support.microsoft.com/kb/2938441

Not only do the new releases bring in full support for the great new features of SP2 such as pending tasks, it also brings about fixes for the following App-V related issues:

  • With App-V 5.0 SP2, when a new version of an App-V package supersedes an earlier version, and that earlier version is being used, the package will be listed as not published. Errors that resemble the following are seen in the AppEnforce.log and AppDiscovery.log files

AppEnforce.log:

Publish-AppvClientPackage : A publish operation has been scheduled, pending the shutdown of all applications in the package or the connection group.

Publishing Package is successful but one one of the Virtual Package is currently in use. Close this Virtual Package to get the changes into effect

Performing detection of app deployment type TestApp – Microsoft Application Virtualization 5(ScopeId_0C7279F0-1490-4A0E-A7A3-32A000CEF76D/DeploymentType_d1adf427-ac14-4ee1-9e51-415af7675383, revision 2) for system.

AppDiscovery.log:

Required component [{AppVPackageRoot}]\TestApp.exe is not published

  • With App-V 5.0 SP2, App-V packages that are being used cannot be uninstalled. Errors that resemble to the following will appear in the AppEnforce.log file:

CVEWorker::UninstallConnectionGroup() failed