Partager via


New KB articles for App-V version 5

imageWe just published a few new KB articles in anticipation of the Microsoft Application Virtualization (App-V) v5 release so if you’re among the many who are planning to make the move then you’ll probably want to take a quick look at these. It’s mostly some support tips and a couple informational types articles but it’s all good stuff.

2772509 - Supported scenarios for deploying Microsoft Office as a sequenced App-V Package (https://support.microsoft.com/kb/2772509)

2777003 - An App-V v5 virtualized application fails to start with error 0xc0000142 (https://support.microsoft.com/kb/2777003)

2778019 - Adding a large application package via the Management Server console on App-V v5 fails with "Timeout expired" (https://support.microsoft.com/kb/2778019)

2778168 - How to troubleshoot publishing server refresh failures in App-V v5 (https://support.microsoft.com/kb/2778168)

2778283 - PowerShell cmdlets are not available after installing an App-V v5 component (https://support.microsoft.com/kb/2778283)

2774436 - Known issues when using App-V v5 Package Converter (https://support.microsoft.com/kb/2774436)

2777777 - Important changes in the App-V v5 Sequencer (https://support.microsoft.com/kb/2777777)

2778945 - Importing a deployment configuration file on App-V v5 fails with "The configuration file does not contain well formed AppV configuration XML" (https://support.microsoft.com/kb/2778945)

2778957 - Virtual applications deployed by .MSI on App-V v5 are not uninstalled correctly when using PowerShell (https://support.microsoft.com/kb/2778957)

2768954 - A Microsoft Application Virtualization MSI run from a mapped drive fails to install the virtual package (https://support.microsoft.com/kb/2768954)

2768945 - How to remove a cached copy of an unpublished package in Microsoft App-V v5 (https://support.microsoft.com/kb/2768945)

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

Get the latest System Center news on Facebook and Twitter :

clip_image001 clip_image002

App-V Team blog: https://blogs.technet.com/appv/
ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/
DPM Team blog: https://blogs.technet.com/dpm/
MED-V Team blog: https://blogs.technet.com/medv/
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: https://blogs.technet.com/momteam/
SCVMM Team blog: https://blogs.technet.com/scvmm
Server App-V Team blog: https://blogs.technet.com/b/serverappv
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: https://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: https://blogs.technet.com/sus/

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/

Comments

  • Anonymous
    November 04, 2012
    Looking at KB2772509 (Supported scenario's). It looks like deployment of Office 2013 on a Terminal Server (RDSH) using App-V is not allowed. Is this correct? (If so, is the only allowed deployment of Office2013 on a Terminal server a local install?)