deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 03:43:39 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
Files
ceff60e9cdfad6cca77974d57accb51ca9e7a714
windows-itpro-docs/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md
VSC-Service-Account 858476cf2f CI Update
2019-06-04 22:13:57 +00:00

2.5 KiB
Raw Blame History

title, description, author, ms.assetid, ms.reviewer, manager, ms.author, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod, ms.date
title description author ms.assetid ms.reviewer manager ms.author ms.pagetype ms.mktglfcycl ms.sitesec ms.prod ms.date
How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User dansimp 19da3776-5ebe-41e1-9890-12b84ef3c1c7 dansimp dansimp mdop, appcompat, virtualization deploy library w10 06/21/2016

How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User

Use the following procedure to migrate packages created with App-V using the user configuration file.

Note   This procedure assumes that you are running the latest version of App-V 4.6.

To convert a package

  1. Locate the user configuration file for the package you want to convert. To set the policy, perform the following updates in the userConfiguration section: ManagingAuthority TakeoverExtensionPointsFrom46="true" PackageName=<Package ID>.

    The following is an example of a user configuration file:

    <?xml version="1.0" ?>

    <UserConfiguration PackageId=<Package ID> DisplayName=<Name of the Package>

    xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration"&gt; <ManagingAuthority TakeoverExtensionPointsFrom46="true"

    PackageName=<Package ID>

    </UserConfiguration>

  2. To add the App-V 5.1 package, type the following in an elevated PowerShell command prompt window:

    PS>$pkg= Add-AppvClientPackage –Path <Path to package location>

    PS>Publish-AppVClientPackage $pkg -DynamicUserConfiguration <Path to the user configuration file>

  3. Open the application using FTAs or shortcuts now. The application should open using App-V 5.1.

    The App-V 4.6 package and the converted App-V 5.1 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.1 package.

    Got a suggestion for App-V? Add or vote on suggestions here. Got an App-V issue? Use the App-V TechNet Forum.

Related topics

Operations for App-V 5.1

How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User