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

updating for Windows 10, version 1607

Browse Source
This commit is contained in:
Brian Lich
2016-08-01 11:06:15 -07:00
parent a4202ede0c
commit 5bfc4eaed0
14 changed files with 178 additions and 586 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
windows/manage/appv-sequence-a-package-with-powershell.md
View File

@ -1,6 +1,6 @@
---
title: How to Sequence a Package by Using PowerShell (Windows 10)
description: How to Sequence a Package by Using PowerShell
title: How to sequence a package by using Windows PowerShell (Windows 10)
description: How to sequence a package by using Windows PowerShell
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
@ -9,23 +9,21 @@ ms.prod: w10
---
# How to Sequence a Package by Using PowerShell
# How to Sequence a Package by using Windows PowerShell
Use the following procedure to create a new App-V package using Windows PowerShell.
Use the following procedure to create a new App-V 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 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
> [!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 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
 
**To create a new virtual application using PowerShell**
**To create a new virtual application by using Windows PowerShell**
1. Install the App-V 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**.
2. Click **Start** and type **Windows PowerShell**. Right-click **Windows PowerShell**, and select **Run as Administrator**.
3. Using the PowerShell console, type the following: **import-module appvsequencer**.
3. Using the Windows 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:
@ -39,34 +37,28 @@ Before you use this procedure you must copy the associated installer files to th
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>**
```
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:
Wait for the sequencer to create the package. Creating a package by using Windows PowerShell can take time. If the package was not created successfully, an error will be returned.
- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
The following list displays additional optional parameters that can be used with **New-AppvSequencerPackage** cmdlet:
- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
- InstallMediaPath - specifies the path to where the installation media is
- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
- TemplateFilePath - specifies the path to a template fileif you want to customize the sequencing process.
- InstallMediaPath - specifies the path of the installation media
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
- TemplateFilePath - specifies the path to a template file if you want to customize the sequencing process.
**Have 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/en-US/home?forum=mdopappv).
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
## Have 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/en-US/home?forum=mdopappv).
## Related topics
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 
 
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)