If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](#bkmk-check-reg-key-svr).
If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](check-reg-key-svr.md).
Follow the steps in [How to Deploy the App-V 5.1 Server](how-to-deploy-the-app-v-51-server.md)
diff --git a/mdop/appv-v5/how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md b/mdop/appv-v5/how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md index 7420ac9bef..49c8452df2 100644 --- a/mdop/appv-v5/how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md +++ b/mdop/appv-v5/how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md @@ -32,9 +32,9 @@ Use the following information to install the Microsoft Application Virtualizatio 5. Convert extension points, as needed. For more information, see the following resources: - - [How to Migrate Extension Points From an App-V 4.6 SP2 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-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) + - [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-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) - - [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md) + - [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-46-sp2-package-to-app-v-51-for-a-specific-user.md) - [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md) diff --git a/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md b/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md index 35d77c5117..d11e7fad16 100644 --- a/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md +++ b/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md @@ -1,21 +1,22 @@ --- -title: How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer -description: How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer +title: 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 +description: 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 ms.assetid: 4ef823a5-3106-44c5-aecc-29edf69c2fbb author: jamiejdt --- -# How to Migrate Extension Points From an App-V 4.6 SP2 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 -Use the following procedure to migrate extension points from an App-V 4.6 SP2 package to a App-V 5.1 package using the deployment configuration file. +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 SP2 package to a converted App-V 5.1 package using the deployment configuration file** +**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** 1. 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: @@ -47,14 +48,14 @@ The following procedure does not require an App-V 5.1 management server. PS>**Publish-AppVClientPackage $pkg** -3. To test the migration, open the virtual application using asscoaited FTAs or shortcuts. The application opens with App-V 5.1. Both, the App-V 4.6 SP2 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. +3. 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](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 -[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md) +[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md) [Operations for App-V 5.1](operations-for-app-v-51.md) diff --git a/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md b/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md index 0b9e3cd221..3e1888a1e1 100644 --- a/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md +++ b/mdop/appv-v5/how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md @@ -1,15 +1,18 @@ --- -title: How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.1 for a Specific User -description: How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.1 for a Specific User +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 ms.assetid: 19da3776-5ebe-41e1-9890-12b84ef3c1c7 author: jamiejdt --- -# How to Migrate Extension Points From an App-V 4.6 SP2 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 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>**. @@ -34,7 +37,7 @@ Use the following procedure to migrate packages created with App-V using the use 3. Open the application using FTAs or shortcuts now. The application should open using App-V 5.1. - The App-V SP2 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. + 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). @@ -43,7 +46,7 @@ Use the following procedure to migrate packages created with App-V using the use [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 SP2 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.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-sp2-package-for-a-specific-user.md) diff --git a/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md b/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md index 98339d52ca..c69c21b2b6 100644 --- a/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md +++ b/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md @@ -1,18 +1,18 @@ --- -title: How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 SP2 Package for a Specific User -description: How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 SP2 Package for a Specific User +title: How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User +description: How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User ms.assetid: bd53c5d6-7fd2-4816-b03b-d59da0a35819 author: jamiejdt --- -# How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 SP2 Package for a Specific User +# How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User Use the following procedure to revert an App-V 5.1 package to the App-V file format using the user configuration file. **To revert a package** -1. Ensure that App-V 4.6 SP2 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md). +1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [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-46-sp2-package-to-app-v-51-for-a-specific-user.md). 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>** @@ -20,7 +20,7 @@ Use the following procedure to revert an App-V 5.1 package to the App-V file for PS>**Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath** <path to user configuration file> -3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 SP2. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2. +3. 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. **Note** If you do not need the App-V 5.1 package anymore, you can unpublish the App-V 5.1 package and the extension points will automatically revert to App-V 4.6. diff --git a/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md b/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md index 2cfc4d1722..265afe0293 100644 --- a/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md +++ b/mdop/appv-v5/how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md @@ -1,18 +1,18 @@ --- -title: How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer -description: How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer +title: How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer +description: How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer ms.assetid: 64640b8e-de6b-4006-a33e-353d285af15e author: jamiejdt --- -# How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer +# How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer -Use the following procedure to revert extension points from an App-V 5.1 package to the App-V 4.6 SP2 file format using the deployment configuration file. +Use the following procedure to revert extension points from an App-V 5.1 package to the App-V 4.6 file format using the deployment configuration file. **To revert a package** -1. Ensure that App-V 4.6 SP2 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 SP2 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-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md). +1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [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-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md). 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>** @@ -22,9 +22,9 @@ Use the following procedure to revert extension points from an App-V 5.1 package PS>**Publish-AppVClientPackage $pkg –DynamicUserConfigurationType useDeploymentConfiguration** -3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 SP2 package. +3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 package. - Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2. + Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6. **Note** If you do not need the App-V 5.1 package anymore, you can unpublish the App-V 5.1 package and the extension points will automatically revert to App-V 4.6. diff --git a/mdop/appv-v5/how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md b/mdop/appv-v5/how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md index 5f95a39eb1..a12c13f680 100644 --- a/mdop/appv-v5/how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md +++ b/mdop/appv-v5/how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md @@ -1,24 +1,27 @@ --- -title: How to Use an App-V 4.6 SP1 Application From an App-V 5.1 Application -description: How to Use an App-V 4.6 SP1 Application From an App-V 5.1 Application +title: How to Use an App-V 4.6 Application From an App-V 5.1 Application +description: How to Use an App-V 4.6 Application From an App-V 5.1 Application ms.assetid: 909b4391-762b-4988-b0cf-32b67f1fcf0e author: jamiejdt --- -# How to Use an App-V 4.6 SP1 Application From an App-V 5.1 Application +# How to Use an App-V 4.6 Application From an App-V 5.1 Application -Use the following procedure to run an App-V 4.6 SP2 application with App-V 5.1 applications on a standalone client. +Use the following procedure to run an App-V 4.6 application with App-V 5.1 applications on a standalone client. + +**Note** +This procedure assumes that you are running the latest version of App-V 4.6. **To run applications on a standalone client** 1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat. -2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 SP2 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-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md). +2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [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-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) or [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-46-sp2-package-to-app-v-51-for-a-specific-user.md). 3. Add and provision the package using the App-V 5.1 management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-51-gb18030.md) and [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-51.md). -4. The converted application now runs using App-V 5.1 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.1 package and Adobe Acrobat is still running as an App-V 4.6 SP2 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook. +4. The converted application now runs using App-V 5.1 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.1 package and Adobe Acrobat is still running as an App-V 4.6 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook. **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). diff --git a/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version.md b/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version.md index 0eb3ce6d09..dc0aeb1008 100644 --- a/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version.md +++ b/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version.md @@ -202,7 +202,7 @@ After you convert an existing package you should test the package prior to deplo -When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be hard-coded path. Convert the path. +When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path. **Note** It is recommended that you use the App-V 5.1 sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V 5.1](how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md). @@ -231,7 +231,7 @@ The following table displays the recommended method for upgrading clients.
Upgrade your environment to App-V 4.6 SP2
Upgrade your environment to the latest version of App-V 4.6
[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md).
Upgrade your environment to App-V 4.6 SP2.
Upgrade your environment to the latest version of App-V 4.6.
[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md).