Making sure PowerShell has Windows in front of it

This commit is contained in:
JanKeller1
2016-08-17 15:21:33 -07:00
parent 2e636b86d0
commit 02f1e34ce1
28 changed files with 208 additions and 408 deletions

View File

@ -1,6 +1,6 @@
---
title: How to Create a Package Accelerator by Using PowerShell (Windows 10)
description: How to Create a Package Accelerator by Using PowerShell
title: How to Create a Package Accelerator by Using Windows PowerShell (Windows 10)
description: How to Create a Package Accelerator by Using Windows PowerShell
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
@ -9,7 +9,7 @@ ms.prod: w10
---
# How to Create a Package Accelerator by Using PowerShell
# How to Create a Package Accelerator by Using Windows PowerShell
Applies to: Windows 10, version 1607
@ -19,7 +19,7 @@ App-V package accelerators automatically sequence large, complex applications. A
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**. Use the **New-AppvPackageAccelerator** cmdlet.
2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. Use the **New-AppvPackageAccelerator** cmdlet.
3. 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:
@ -35,22 +35,14 @@ App-V package accelerators automatically sequence large, complex applications. A
**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:
An additional optional parameter that can be used with the **New-AppvPackageAccelerator** cmdlet is as follows:
- **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.
**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).
## Have a suggestion for App-V?
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related topics
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)