2.2 KiB
title, description, ms.assetid, author, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod
| title | description | ms.assetid | author | ms.pagetype | ms.mktglfcycl | ms.sitesec | ms.prod |
|---|---|---|---|---|---|---|---|
| How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User | How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User | dad25992-3c75-4b7d-b4c6-c2edf43baaea | jamiejdt | mdop, appcompat, virtualization | deploy | library | w10 |
How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
Note:* App-V 4.6 has exited Mainstream support.
Use the following procedure to migrate packages created with App-V using the user configuration file.
To convert a package
-
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"> <ManagingAuthority TakeoverExtensionPointsFrom46="true"
PackageName=<Package ID>
</UserConfiguration>
-
To add the App-V 5.0 package type the following in an elavted PowerShell command prompt:
PS>$pkg= Add-AppvClientPackage –Path <Path to package location>
PS>Publish-AppVClientPackage $pkg -DynamicUserConfiguration <Path to the user configuration file>
-
Open the application using FTAs or shortcuts now. The application should open using App-V 5.0.
The App-V SP2 package and the converted App-V 5.0 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.0 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