How to Create a Package Accelerator Using PowerShell
Updated: November 1, 2012
Applies To: Application Virtualization 5.0
App-V 5.0 package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V 5.0 package accelerator, you are not always required to manually install an application to create the virtualized package.
To create a package accelerator
Install the App-V 5.0 sequencer. For more information about installing the sequencer see How to Install the Sequencer.
To open a PowerShell console click Start and type PowerShell. Right-click Windows PowerShell and select Run as Administrator. Use the New-AppvPackageAccelerator cmdlet.
To create a package accelerator, make sure that you have the .appv package to create an accelerator from, the installation media or installation files, and optionally a read me file for consumers of the accelerator to use. The following parameters are required to use the package accelerator cmdlet:
InstalledFilesPath - specifies the application installation path.
Installer – specifies the path to the application installer media
InputPackagePath – specifies the path to the .appv package
Path – specifies the output directory for the package.
The following example displays how you can create a package accelerator with an .appv package and the installation media:
New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>
Additional optional parameters that can be used with the New-AppvPackageAccelerator cmdlet are displayed in the following list:
AcceleratorDescriptionFile - specifies the path to user created package accelerator instructions. The package accelerator instructions are .txt or .rtf description files that will be packaged with the package created using the package accelerator.
- InstalledFilesPath - specifies the application installation path.
Other ResourcesAdministering App-V using PowerShell
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.