Export (0) Print
Expand All

Planning for Migrating From a Previous Version

Updated: November 1, 2012

Applies To: Application Virtualization 5.0

The following sections provide information about how to migrate from a previous version of Microsoft Application Virtualization (App-V) 5.0.

Before you attempt to upgrade to App-V 5.0 or later versions, any version prior to 4.6 SP2 must be upgraded to version 4.6 SP2. You should plan to upgrade your clients first, and then upgrade the server components.

App-V 5.0 supports only packages that are created using App-V 5.0 or packages that have been converted to the App-V 5.0 (.appv) format.

App-V 5.0 client coexistence with 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.

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.

Convert previous-version packages using the package converter

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.

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.

See Also

Other Resources

Planning to Deploy App-V

You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft