mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Preparing for pull request, updated two more articles
This commit is contained in:
Heidi Lohr
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to Convert a Package Created in a Previous Version of App-V
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to create a connection croup with user-published and globally published packages
|
||||
|
||||
@ -24,31 +24,7 @@ Here are some important things to know before you get started:
|
||||
- If you add user-published packages in globally entitled connection groups, the connection group will fail.
|
||||
- Track the connection groups where you've used a non-optional package before removing it with the **Unpublish-AppvClientPackage <</span>package> -global** cmdlet.
|
||||
|
||||
In situations where you have a gobally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running that cmdlet can unpublish the package from every connection group containing that package.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Unsupported scenarios and potential issues</th>
|
||||
<th align="left">Result</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You cannot include user-published packages in globally entitled connection groups.</p></td>
|
||||
<td align="left"><p>The connection group will fail.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>If you publish a package globally and then create a user-published connection group in which you’ve made that package non-optional, you can still run <strong>Unpublish-AppvClientPackage <package> -global</strong> to unpublish the package, even when that package is being used in another connection group.</p></td>
|
||||
<td align="left"><p>If any other connection groups are using that package, the package will fail in those connection groups.</p>
|
||||
<p>To avoid inadvertently unpublishing a non-optional package that is being used in another connection group, we recommend that you track the connection groups in which you’ve used a non-optional package.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
In situations where you have a gobally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running **Unpublish-AppvClientPackage <</span>package> -global** cmdlet can unpublish the package from every connection group containing that package. Tracking connection groups can help you avoid unintentionally unpublishing non-optional packages.
|
||||
|
||||
## How to use Windows PowerShell cmdlets to create user-entitled connection groups
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to create a connection group
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to create a custom configuration file by using the App-V Management Console
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to create a package accelerator by using Windows PowerShell
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to create a package accelerator
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
# How to create a virtual application package using an App-V Package Accelerator
|
||||
|
||||
@ -19,9 +19,9 @@ Use the following procedure to create a virtual application package with the App
|
||||
|
||||
## Create a virtual application package with an App-V Package Accelerator
|
||||
|
||||
1. Be sure that the required Package Accelerator has been copied locally to the computer that runs the App-V Sequencer. Also copy all required installation files for the package to a local folder on the computer that runs the Sequencer. This is the folder that you have to specify in step 6 of this procedure.
|
||||
1. Make sure you've copied the required Package Accelerator locally to the computer running the App-V Sequencer. Also make sure to copy all required installation files for the package to a local folder on the computer running the Sequencer. This is the folder that you have to specify in step 6 of this procedure.
|
||||
|
||||
2. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, go to **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
2. To start the App-V Sequencer on the computer that runs the Sequencer, go to **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
3. Select **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, then select **Next**.
|
||||
|
||||
@ -34,41 +34,41 @@ Use the following procedure to create a virtual application package with the App
|
||||
|
||||
6. On the **Select Installation Files** page, select **Make New Folder** to create a local folder that contains all required installation files for the package, and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer that runs the Sequencer, select **Browse** to select the folder.
|
||||
|
||||
Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, and then select **Next**.
|
||||
Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, then select **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>You can specify the following types of supported installation files:
|
||||
> - Windows Installer files (**.msi**)
|
||||
> - Cabinet files (.cab)
|
||||
> - Compressed files with a .zip file name extension
|
||||
> - The actual application files
|
||||
> - Windows Installer files (**.msi**)
|
||||
> - Cabinet files (.cab)
|
||||
> - Compressed files with a .zip file name extension
|
||||
> - The actual application files
|
||||
> The following file types are not supported: **.msp** and **.exe** files. If you specify an **.exe** file, you must extract the installation files manually.
|
||||
|
||||
7. If the package accelerator requires an application to be installed before you apply the Package Accelerator, and if you have already installed the required application, select **I have installed all applications**, and then select **Next** on the **Local Installation** page.
|
||||
7. If the package accelerator requires you to install an application before you apply the Package Accelerator and you have already installed the required application, select **I have installed all applications**, then select **Next** on the **Local Installation** page.
|
||||
|
||||
8. On the **Package Name** page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Select **Next**.
|
||||
8. On the **Package Name** page, specify a name that will be associated with the package. The name you choose will identify the package in the App-V Management Console. Select **Next**.
|
||||
|
||||
9. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information that is displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network, or when the package size exceeds 4 GB.
|
||||
9. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network or the package size exceeds 4 GB.
|
||||
|
||||
10. To create the package, select **Create**. After the package is created, select **Next**.
|
||||
|
||||
11. On the **Configure Software** page, to enable the Sequencer to configure the applications that are contained in the package, select **Configure Software**. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements.
|
||||
11. On the **Configure Software** page, to enable the Sequencer to configure the applications contained within the package, select **Configure Software**. **Configure Software** will let you configure any associated tasks required to run the application on the target computers. For example, you can configure any associated license agreements.
|
||||
|
||||
If you select **Configure Software**, the following items can be configured using the Sequencer as part of this step:
|
||||
The following items can be configured using the Sequencer as part of this step:
|
||||
|
||||
- **Load Package**. The Sequencer loads the files that are associated with the package. It can take several seconds to an hour to decode the package.
|
||||
- **Load Package** loads files associated with the package. It can take several seconds to an hour to decode the package.
|
||||
|
||||
- **Run Each Program**. Optionally run the programs that are contained in the package. This step is helpful to complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at once, select at least one program, and then select **Run All**. To run specific programs, select the program or programs that you want to run, and then select **Run Selected**. Complete the required configuration tasks, and then close the applications. It can take several minutes for all programs to run. Select **Next**.
|
||||
- **Run Each Program** optionally runs programs contained within the package. This step can help you complete associated license or configuration tasks that must be completed before deploying and running the package on target computers. To run all the programs at once, select at least one program, and then select **Run All**. To run specific programs, select the program or programs that you want to run, and then select **Run Selected**. Complete the required configuration tasks, then close the applications. It can take several minutes for all programs to run. Select **Next**.
|
||||
|
||||
- **Save Package**. The Sequencer saves the package.
|
||||
- **Save Package** saves the package.
|
||||
|
||||
- **Primary Feature Block**. The Sequencer optimizes the package for streaming by rebuilding the primary feature block.
|
||||
- **Primary Feature Block** optimizes the package for streaming by rebuilding the primary feature block.
|
||||
|
||||
If you do not want to configure the applications, select **Skip this step**, and then select **Next**.
|
||||
If you don't want to configure the applications, select **Skip this step**, then select **Next**.
|
||||
|
||||
12. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, select **Close**.
|
||||
|
||||
The package is now available in the Sequencer. To edit the package properties, select **Edit \[Package Name\]**. For more information about how to modify a package, see [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md).
|
||||
The package is now available in the Sequencer. To edit the package properties, select **Edit \[Package Name\]**. For more information about how to modify a package, see [How to modify an existing virtual application package](appv-modify-an-existing-virtual-application-package.md).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
@ -76,4 +76,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
|
||||
|
||||
## Related topics
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -6,49 +6,47 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
|
||||
# Create and apply an App-V project template to a sequenced App-V package
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
You can use an App-V project template (.appvt) file to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages. App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic.
|
||||
You can use an App-V project template (.appvt) file to save commonly applied settings associated with an existing virtual application package. You can then apply these settings whenever you create new virtual application packages in your environment, streamlining the package creation process. App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. To learn more about Package Accelerators, see [How to create a Package Accelerator](appv-create-a-package-accelerator.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
>In Windows 10, version 1703, running the **New-AppvSequencerPackage** or the **Update-AppvSequencerPackage** cmdlets will automatically capture and store your customizations as an App-V project template. If you want to make changes to this package later, you can automatically load your customizations from this template file. If you have an auto-saved template and you attempt to load another template through the *TemplateFilePath* parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
## Create a project template
|
||||
|
||||
You must first create and save a project template, including a virtual app package with settings to be used by the template.
|
||||
|
||||
**To create a project template**
|
||||
|
||||
1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
1. On the device running the App-V Sequencer, select **Start**, select **All Programs**, select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
>[!NOTE]
|
||||
>If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure.
|
||||
|
||||
2. On the **File** menu, click **Open**, click **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V project template, and then click **Edit** to change any of the settings or info included in the file.
|
||||
2. On the **File** menu, select **Open**, select **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V project template, and then select **Edit** to change any of the settings or info included in the file.
|
||||
|
||||
3. On the **File** menu, click **Save As Template**, review the settings associated with the new template, click **OK**, name your new template, and then click **Save**.
|
||||
3. On the **File** menu, select **Save As Template**, review the settings associated with the new template, select **OK**, name your new template, and then select **Save**.
|
||||
|
||||
The new App-V project template is saved in the folder you specified.
|
||||
|
||||
## Apply a project template
|
||||
|
||||
After creating the template, you can apply it to all of your new virtual app packages, automatically including all of the settings.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Virtual app packages don't support using both a project template and a Package Accelerator together.
|
||||
>Virtual app packages don't support using both a project template and a Package Accelerator at the same time.
|
||||
|
||||
1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
1. On the device running the App-V Sequencer, select **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. On the **File** menu, click **New From Template**, browse to your newly created project template, and then click **Open**.
|
||||
2. On the **File** menu, select **New From Template**, browse to your newly created project template and select **Open**.
|
||||
|
||||
3. Create your new virtual app package. The settings saved with your template are automatically applied.
|
||||
|
||||
### Related topics
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
@ -61,5 +59,6 @@ After creating the template, you can apply it to all of your new virtual app pac
|
||||
|
||||
- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
|
||||
**Have a suggestion for App-V?**<p>
|
||||
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).
|
||||
## 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).
|
||||
|
||||
@ -6,35 +6,32 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 07/10/2018
|
||||
---
|
||||
|
||||
|
||||
# How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
|
||||
|
||||
**To customize virtual applications extensions for an AD group**
|
||||
## Customize virtual applications extensions for an AD group
|
||||
|
||||
1. To view the package that you want to configure, open the App-V Management Console. To view the configuration that is assigned to a given user group, select the package, and right-click the package name and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
|
||||
1. To view the package that you want to configure, open the App-V Management Console. To view the configuration assigned to a given user group, select the package, then right-click the package name and select **Edit active directory access**. Alternatively, select the package and select **EDIT** in the **AD ACCESS** pane.
|
||||
|
||||
2. To customize an AD group, you can find the group from the list of **AD Entities with Access**. Then, using the drop-down box in the **Assigned Configuration** pane, select **Custom**, and then click **EDIT**.
|
||||
2. To customize an AD group, you can find the group from the list of **AD Entities with Access**. Then, using the drop-down box in the **Assigned Configuration** pane, select **Custom**, and then select **EDIT**.
|
||||
|
||||
3. To disable all extensions for a given application, clear **ENABLE**.
|
||||
3. To disable all extensions for a given application, clear **ENABLE**.
|
||||
|
||||
To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane, and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane, and select **Remove Shortcut**. To edit an existing shortcut, right-click the application, and select **Edit Shortcut**.
|
||||
To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane, and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane and select **Remove Shortcut**. To edit an existing shortcut, right-click the application and select **Edit Shortcut**.
|
||||
|
||||
4. To view any other application extensions, click **Advanced**, and click **Export Configuration**. Type in a filename and click **Save**. You can view all application extensions that are associated with the package using the configuration file.
|
||||
4. To view any other application extensions, select **Advanced**, and select **Export Configuration**. Enter a filename and select **Save**. You can view all application extensions that are associated with the package using the configuration file.
|
||||
|
||||
5. To edit additional application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog, click **Overwrite** to complete the process.
|
||||
5. To edit additional application extensions, modify the configuration file and select **Import and Overwrite this Configuration**. Select the modified file and select **Open**. In the dialog, select **Overwrite** to complete the process.
|
||||
|
||||
## 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)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
Reference in New Issue
Block a user