Export (0) Print
Expand All

Migrating from a Previous Version

Updated: July 9, 2014

Applies To: Application Virtualization 5.0

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:

noteNote
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.

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

When converting existing packages using you should consider the information in the following table:

 

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. For more information about 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.

Managing Authority section is erroneously removed from the deployment configuration file when you use the command line to convert a package.

Before you convert the package, copy the Managing Authority section from the deployment configuration file, and then paste that section into the new configuration file after you complete the conversion process.

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.

noteNote
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. For more information about using the sequencer 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

For more information about upgrading see, Application Virtualization Deployment and Upgrade Considerations.

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

For more information see, How to Install the App-V 4.6 SP2 Client 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.

For more information see, How to Sequence a New Application with App-V 5.0.

ImportantImportant
You must be running App-V 4.6 SP2 to use co-existence mode. Additionally, when you sequence a package you must configure the, managing authority setting in deployment configuration file which 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.

For more information about upgrading see, Application Virtualization Deployment and Upgrade Considerations.

Deploy App-V 5.0 version of the client.

For more information see How to Deploy the Client.

Install App-V 5.0 server.

For more information about installing the App-V 5.0 see How to Deploy the App-V 5.0 Server.

Migrate existing packages.

For more information about migrating App-V 5.0 packages see the Converting packages created using a prior version of App-V section of this document.

Additional Migration tasks

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
Show:
© 2014 Microsoft