How to Convert a Package Created in a Previous Version of App-V
Updated: November 1, 2012
Applies To: Application Virtualization 5.0
You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V.
|If you are running a computer with a 64-bit architecture, you must use the x86 version of PowerShell.|
The package converter can only directly convert packages that were created by using the App-V 4.5 sequencer or a subsequent version. Packages that were created using a version prior to App-V 4.5 must be upgraded to the App-V 4.5 or App-V 4.6 format before conversion.
The following information provides direction for converting existing virtual application packages.
|You must configure the package converter to always save the package ingredients file to a secure location and directory. A secure location is accessible only by an administrator. Additionally, when you deploy the package, you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion process.|
Install the App-V Sequencer on a computer in your environment. For information about how to install the Sequencer, see How to Install the Sequencer.
The following cmdlets are available:
Test-AppvLegacyPackage – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing .sft files, an invalid source, .osd file errors, or invalid package version. This cmdlet will not parse the .sft file or do any in depth validation. For information about options and basic functionality for this cmdlet, using the PowerShell cmdline, type
ConvertFrom-AppvLegacyPackage – To convert an existing package, type
ConvertFrom-AppvLegacyPackage c:\contentStore c:\convertedPackages. In this command,
c:\contentStorerepresents the location of the existing package and
c:\convertedPackagesis the output directory to which the resulting App-V 5.0 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used for the App-V 5.0 filename.
Note Before you specify the output directory, you must create the output directory.
Advanced Conversion Tips
Piping - PowerShell supports piping. Piping allows you to call
dir c:\contentStore\myPackage | Test-AppvLegacyPackage. In this example, the directory object that represents
myPackagewill be given as input to the
Test-AppvLegacyPackagecommand and bound to the
-Sourceparameter. Piping like this is especially useful when you want to batch commands together; for example,
dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages. This piped command would test the packages and then pass those objects on to actually be converted. You can also apply a filter on packages without errors or only specify a directory which contains an .sprj file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V 5.0 client.
Batching - The PowerShell command enables batching. More specifically, the cmdlets support taking a string object for the
-Sourceparameter which represents a list of directory paths. This allows you to enter
$packages = dir c:\contentStoreand then call
ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target c:\ConvertedPackagesor to use piping and call
dir c:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages.
Other functionality - PowerShell has other built-in functionality for features such as aliases, piping, lazy-binding, .NET object, and many others. All of these are usable in PowerShell and can help you create advanced scenarios for the Package Converter.
- Test-AppvLegacyPackage – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing .sft files, an invalid source, .osd file errors, or invalid package version. This cmdlet will not parse the .sft file or do any in depth validation. For information about options and basic functionality for this cmdlet, using the PowerShell cmdline, type
Other ResourcesOperations for App-V 5.0
How to Convert a Package Created in a Previous Version Using PowerShell [Beta]
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.