3.0 KiB
title, description, author, ms.assetid, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod
| title | description | author | ms.assetid | ms.pagetype | ms.mktglfcycl | ms.sitesec | ms.prod |
|---|---|---|---|---|---|---|---|
| How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer | How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer | jamiejdt | 4ef823a5-3106-44c5-aecc-29edf69c2fbb | mdop, appcompat, virtualization | deploy | library | w10 |
How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer
Use the following procedure to migrate extension points from an App-V 4.6 package to a App-V 5.1 package using the deployment configuration file.
Note
This procedure assumes that you are running the latest version of App-V 4.6.
The following procedure does not require an App-V 5.1 management server.
To migrate extension points from a package from an App-V 4.6 package to a converted App-V 5.1 package using the deployment configuration file
-
Locate the directory that contains the deployment configuration file for the package you want to migrate. To set the policy, make the following update to the userConfiguration section:
ManagingAuthority TakeoverExtensionPointsFrom46="true" PackageName=<Package ID>
The following is an example of content from a deployment configuration file:
<?xml version="1.0" ?>
<DeploymentConfiguration
xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration" PackageId=<Package ID> DisplayName=<Display Name>
<MachineConfiguration/>
<UserConfiguration>
<ManagingAuthority TakeoverExtensionPointsFrom46="true"
PackageName=<Package ID>
</UserConfiguration>
</DeploymentConfiguration>
-
To add the App-V 5.1 package, in an elevated PowerShell command prompt type:
PS>$pkg= Add-AppvClientPackage –Path <Path to package location> -DynamicDeploymentConfiguration <Path to the deployment configuration file>
PS>Publish-AppVClientPackage $pkg
-
To test the migration, open the virtual application using associated FTAs or shortcuts. The application opens with App-V 5.1. Both, 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