mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Finished old file and started updating new file.
This commit is contained in:
@ -18,23 +18,25 @@ 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 Windows PowerShell console, select **Start** and enter **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
3. Enter the **New-AppvPackageAccelerator** cmdlet.
|
||||
4. 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 readme file for the accelerator's consumers to use. The following parameters are required to use the package accelerator cmdlet:
|
||||
3. Make sure that you have the .appv package to create an accelerator from the installation media or installation files. You can also optionally use a readme file for the accelerator's users to reference.
|
||||
4. Enter the **New-AppvPackageAccelerator** 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 parameters are required to use the package accelerator cmdlet:
|
||||
|
||||
The following example displays how you can create a package accelerator with an .appv package and the installation media:
|
||||
- *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 cmdlet shows how you can create a package accelerator with an .appv package and the installation media:
|
||||
|
||||
```PowerShell
|
||||
New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>
|
||||
```
|
||||
|
||||
An additional optional parameter that can be used with the **New-AppvPackageAccelerator** cmdlet is as follows:
|
||||
You can also use the following optional parameter with the **New-AppvPackageAccelerator** cmdlet:
|
||||
|
||||
- **AcceleratorDescriptionFile** specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created using the package accelerator.
|
||||
- *AcceleratorDescriptionFile* specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Create a Package Accelerator (Windows 10)
|
||||
description: How to Create a Package Accelerator
|
||||
title: How to create a package accelerator (Windows 10)
|
||||
description: How to create a package accelerator.
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -8,72 +8,70 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
# How to create a package accelerator
|
||||
|
||||
|
||||
# How to Create a Package Accelerator
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
App-V package accelerators automatically generate new virtual application packages.
|
||||
|
||||
>**Note** You can use Windows PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md).
|
||||
>[!NOTE]
|
||||
>You can use Windows PowerShell to create a package accelerator. For more information, see [How to create a package accelerator by using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md).
|
||||
|
||||
Use the following procedure to create a package accelerator.
|
||||
|
||||
>**Important**
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
> - Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
|
||||
> - Before you begin the following procedure, perform the following:
|
||||
- Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer.
|
||||
- Copy all required installation files associated with the virtual application package to the computer running the sequencer.
|
||||
> - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V Sequencer.
|
||||
>- Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer.
|
||||
>- Copy all required installation files associated with the virtual application package to the computer running the sequencer.
|
||||
> - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a package accelerator with the App-V sequencer.
|
||||
|
||||
## To create a package accelerator
|
||||
## Create a package accelerator
|
||||
|
||||
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
1. To start the App-V sequencer on the computer running the sequencer, select **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, click **Tools** / **Create Accelerator**.
|
||||
2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, select **Tools** > **Create Accelerator**.
|
||||
|
||||
3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, click **Browse**, and locate the existing virtual application package (.appv file).
|
||||
3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, select **Browse**, then locate the existing virtual application package (it will appear as an .appv file).
|
||||
|
||||
**Tip**<br>
|
||||
Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer.
|
||||
|
||||
Click **Next**.
|
||||
>[!TIP]
|
||||
>Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer.
|
||||
|
||||
4. On the **Installation Files** page, to specify the folder that contains the installation files that you used to create the original virtual application package, click **Browse**, and then select the directory that contains the installation files.
|
||||
Select **Next**.
|
||||
|
||||
**Tip**<br>
|
||||
Copy the folder that contains the required installation files to the computer running the Sequencer.
|
||||
4. To specify the folder containing original virtual package's installation files, go to the **Installation Files** page and select **Browse**, then select the directory that contains the installation files.
|
||||
|
||||
5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location.
|
||||
>[!TIP]
|
||||
>Copy the folder that contains the required installation files to the computer running the Sequencer.
|
||||
|
||||
6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, and then click **Next**. If the files are required, click **Previous** and copy the required files to the directory specified on the **Installation Files** page.
|
||||
5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location.
|
||||
|
||||
**Note**<br>
|
||||
You must either remove the unrequired files, or click **Previous** and locate the required files to advance to the next page of this wizard.
|
||||
6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page.
|
||||
|
||||
7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**.
|
||||
>[!NOTE]
|
||||
>You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard.
|
||||
|
||||
8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package.
|
||||
7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**.
|
||||
|
||||
8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package.
|
||||
|
||||
If necessary, to add additional Installer files, click **Add**. To remove unnecessary installation files, select the Installer file, and then click **Delete**. To edit the properties associated with an installer, click **Edit**. The installation files specified in this step will be required when the Package Accelerator is used to create a new virtual application package. After you have confirmed the information displayed, click **Next**.
|
||||
|
||||
9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**.
|
||||
9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**.
|
||||
|
||||
10. On the **Create Package Accelerator** page, to specify where to save the Package Accelerator, click **Browse** and select the directory.
|
||||
|
||||
11. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**.
|
||||
|
||||
**Important**<br>
|
||||
To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator.
|
||||
>[!IMPORTANT]
|
||||
>To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
- [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
|
Reference in New Issue
Block a user