Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Migrating from a Previous Version

Updated: December 16, 2014

Applies To: Application Virtualization 5.0, Application Virtualization 5.0 SP1, Application Virtualization 5.0 SP2, Application Virtualization 5.0 SP3

With App-V 5.0 you can migrate your existing App-V 4.6 infrastructure to the more flexible, integrated, and easier to manage App-V 5.0 infrastructure.

Consider the following sections when you plan your migration strategy:

For more information about the differences between App-V 4.6 and App-V 5.0, see the Differences between App-4.6 and App-V 5.0 section of About App-V 5.0.

Converting packages created using a prior version of App-V

Use the package converter utility to upgrade virtual application packages created using previous versions of App-V. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.

After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful.

What to know before you convert existing packages


Issue Workaround

Package scripts are not converted.

Test the converted package. If necessary convert the script.

Package registry setting overrides are not converted.

Test the converted package. If necessary, re-add registry overrides.

Virtual packages using DSC are not linked after conversion.

Link the packages using connection groups. See Managing Connection Groups.

Environment variable conflicts are detected during conversion.

Resolve any conflicts in the associated .osd file.

Hard-coded paths are detected during conversion.

Hard-coded paths are difficult to convert correctly. The package converter will detect and return packages with files that contain hard-coded paths. View the file with the hard-coded path, and determine whether the package requires the file. If so, it is recommended to re-sequence the package.

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.

It is recommended that you use the App-V 5.0 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.0.

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 5.0 sequencer.

How to Convert a Package Created in a Previous Version of App-V

Migrating Clients

The following table displays the recommended method for upgrading clients.


Task More Information

Upgrade your environment to App-V 4.6 SP2

Application Virtualization Deployment and Upgrade Considerations.

Install the App-V 5.0 client with co-existence enabled.

How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer.

Sequence and roll out App-V 5.0 packages. As needed, unpublish App-V 4.6 packages.

How to Sequence a New Application with App-V 5.0.

You must be running App-V 4.6 SP2 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the User Configuration is located in the User Configuration section.

Migrating the App-V 5.0 Server Full Infrastructure

There is no direct method to upgrade to a full App-V 5.0 infrastructure. Use the information in the following section for information about upgrading the App-V server.


Task More Information

Upgrade your environment to App-V 4.6 SP2.

Application Virtualization Deployment and Upgrade Considerations.

Deploy App-V 5.0 version of the client.

How to Deploy the App-V Client.

Install App-V 5.0 server.

How to Deploy the App-V 5.0 Server.

Migrate existing packages.

See the Converting packages created using a prior version of App-V section of this article.

Additional Migration tasks

Got a suggestion for App-V?

Add or vote on suggestions here. For App-V issues, use the App-V TechNet Forum.

Other resources for performing App-V migration tasks

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
© 2015 Microsoft