deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

adding app-v for windows files

Browse Source
This commit is contained in:
Brian Lich
2016-06-20 14:37:42 -07:00
parent e7e30456b2
commit e38d599270
107 changed files with 19184 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
windows/manage/appv-sequence-a-package-with-powershell.md Normal file
View File

@ -0,0 +1,73 @@
---
title: How to Sequence a Package by Using PowerShell
description: How to Sequence a Package by Using PowerShell
author: jamiejdt
ms.assetid: 6134c6be-937d-4609-a516-92d49154b290
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Sequence a Package by Using PowerShell
Use the following procedure to create a new App-V 5.1 package using PowerShell.
**Note**  
Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
 
**To create a new virtual application using PowerShell**
1. Install the App-V 5.1 sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
3. Using the PowerShell console, type the following: **import-module appvsequencer**.
4. To create a package, use the **New-AppvSequencerPackage** cmdlet. The following parameters are required to create a package:
- **Name** - specifies the name of the package.
- **PrimaryVirtualApplicationDirectory** - specifies the path to the directory that will be used to install the application. This path must exist.
- **Installer** - specifies the path to the associated application installer.
- **Path** - specifies the output directory for the package.
For example:
**New-AppvSequencerPackage –Name <name of Package> -PrimaryVirtualApplicationDirectory <path to the package root> -Installer <path to the installer executable> -OutputPath <directory of the output path>**
Wait for the sequencer to create the package. Creating a package using PowerShell can take time. If the package was not created successfully an error will be returned.
The following list displays additional optional parameters that can be used with **New-AppvSequencerPackage** cmdlet:
- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
- InstallMediaPath - specifies the path to where the installation media is
- TemplateFilePath - specifies the path to a template fileif you want to customize the sequencing process.
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V 5.1 before it can be opened.
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
## Related topics
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)