2.2 KiB
title, description, ms.assetid, author, ms.assetid, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod
| title | description | ms.assetid | author | ms.assetid | ms.pagetype | ms.mktglfcycl | ms.sitesec | ms.prod |
|---|---|---|---|---|---|---|---|---|
| How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User | How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User | f1d2ab1f-0831-4976-b49f-169511d3382a | jamiejdt | f1d2ab1f-0831-4976-b49f-169511d3382a | mdop, appcompat, virtualization | deploy | library | w10 |
How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
Note:* App-V 4.6 has exited Mainstream support.
Use the following procedure to revert an App-V 5.0 package to the App-V file format using the user configuration file.
To revert a package
-
Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User.
In the userConfiguration section of the deployment configuration file for the converted package, to set the policy, make the following update to the userConfiguration section: ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>
-
From an elevated command prompt, type:
PS>Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath <path to user configuration file>
-
Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
Note If you do not need the App-V 5.0 package anymore, you can unpublish the App-V 5.0 package and the extension points will automatically revert to App-V 4.6.
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