diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index 249d1366e3..ee780fe37e 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -207,45 +207,8 @@ It is recommended that you use the App-V sequencer for converting critical appli If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer. - - [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md) -## Migrating Clients - - -The following table displays the recommended method for upgrading clients. - -
Task | -More Information | -
---|---|
Upgrade your environment to the latest version of App-V 4.6 |
-[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy). |
-
Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages. |
-[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md). |
-