Planning for Migrating From a Previous Version

Fortunately, the App-V 5.0 client is allowed to run on the same computer with the App-V 4.6 SP2 version of the client. This coexistence helps to make the migration easier. With both client versions running, you can convert an App-V 4.6 SP2 package to the App-V 5.0 format and both packages can be published. You can define the migration policy for the converted package, which will allow the converted App-V 5.0 package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.

Important
App-V 5.0 can co-exist only on computers that run App-V 4.6 SP2. The migration is not supported if App-V 4.6 SP2 is not installed. You must apply App-V 4.6 SP2 before you install App-V 5.0.

App-V 5.0 client coexistence is supported for the following scenario:

• The computer is running App-V 4.6 SP2, and App-V 5.0 is also installed on the same computer.
  
  

For more information about how to configure App-V 5.0 client coexistence, see How to Install the App-V 4.6 SP2 Client and the App-V 5.0 Client on the Same Computer.

Before you migrate a package that was created using App- 4.6 SP2 or earlier to App-V 5.0, you must convert the package to the .appv file format.

Note
The Package Converter only supports direct conversion of packages created using App-V 4.5 and later. To use the package converter on a package created using a previous version, you must use an App-V 4.5 or later version of the sequencer to upgrade the package, and then you can perform the package conversion.

For more information about converting a package using the package converter, see How to Convert a Package Created in a Previous Version of App-V. After the file has been converted, you can deploy to target computers that run the App-V 5.0 client.

Other Resources