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
2016-06-21 10:17:14 -07:00

64 lines
2.4 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User
description: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User
author: jamiejdt
ms.assetid: 19da3776-5ebe-41e1-9890-12b84ef3c1c7
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# 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"> <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](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](operations-for-app-v-51.md)
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)