mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
Making sure PowerShell has Windows in front of it
This commit is contained in:
JanKeller1
parent
2e636b86d0
commit
02f1e34ce1
@ -33,15 +33,15 @@ Use the following Windows PowerShell procedures to perform various App-V tasks.
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)</p></td>
|
||||
<td align="left"><p>[How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)</p></td>
|
||||
<td align="left"><p>Describes how to install the Windows PowerShell cmdlets and find cmdlet help and examples.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to manage the client package lifecycle on a stand-alone computer by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to manage connection groups by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -49,27 +49,27 @@ Use the following Windows PowerShell procedures to perform various App-V tasks.
|
||||
<td align="left"><p>Describes how to modify the client by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to apply a user configuration file by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to apply a deployment configuration file by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Sequence a Package by Using PowerShell](appv-sequence-a-package-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Sequence a Package by Using Windows PowerShell](appv-sequence-a-package-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to create a new package by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Create a Package Accelerator by Using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to create a package accelerator by using Windows PowerShell. You can use package accelerators automatically sequence large, complex applications.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to enable the computer running the App-V to send reporting information.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)</p></td>
|
||||
<td align="left"><p>[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -90,7 +90,7 @@ Make sure that any script you execute with your App-V packages matches the execu
|
||||
## Windows PowerShell Error Handling
|
||||
|
||||
|
||||
Use the following table for information about App-V PowerShell error handling.
|
||||
Use the following table for information about Windows PowerShell error handling for App-V.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -116,8 +116,8 @@ Use the following table for information about App-V PowerShell error handling.
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Package name contains <strong>$</strong></p></td>
|
||||
<td align="left"><p>If a package name contains the character ( <strong>$</strong> ), you must use a single-quote ( <strong>‘</strong> ), for example,</p>
|
||||
<p><strong>Add-AppvClientPackage ‘Contoso$App.appv’</strong></p></td>
|
||||
<td align="left"><p>If a package name contains the character ( <strong>$</strong> ), you must use a single-quote ( <strong>'</strong> ), for example,</p>
|
||||
<p><strong>Add-AppvClientPackage 'Contoso$App.appv'</strong></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -15,10 +15,8 @@ Applies to: Windows 10, version 1607
|
||||
|
||||
You can configure the App-V client so that only administrators (not end users) can enable or disable connection groups. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
**Note**
|
||||
**This feature is supported starting in App-V 5.0 SP3.**
|
||||
|
||||
|
||||
**Note**<br>
|
||||
This feature is supported starting in App-V 5.0 SP3.
|
||||
|
||||
Use one of the following methods to allow only administrators to enable or disable connection groups.
|
||||
|
||||
@ -40,32 +38,22 @@ Use one of the following methods to allow only administrators to enable or disab
|
||||
<p><strong>Computer Configuration > Administrative Templates > System > App-V > Publishing</strong></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PowerShell cmdlet</p></td>
|
||||
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>–RequirePublishAsAdmin</strong> parameter.</p>
|
||||
<td align="left"><p>Windows PowerShell cmdlet</p></td>
|
||||
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>-RequirePublishAsAdmin</strong> parameter.</p>
|
||||
<p>Parameter values:</p>
|
||||
<ul>
|
||||
<li><p>0 - False</p></li>
|
||||
<li><p>1 - True</p></li>
|
||||
</ul>
|
||||
<p><strong>Example:</strong>: Set-AppvClientConfiguration –RequirePublishAsAdmin1</p></td>
|
||||
<p>Example: <strong>Set-AppvClientConfiguration -RequirePublishAsAdmin 1</strong></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
**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).
|
||||
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
|
||||
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -384,7 +384,7 @@ App-V Packages are staged upon addition to the computer with the App-V Client. T
|
||||
|
||||
### Mounting packages
|
||||
|
||||
Packages can be explicitly loaded using the PowerShell `Mount-AppVClientPackage` or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store.
|
||||
Packages can be explicitly loaded using the Windows PowerShell `Mount-AppVClientPackage` or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store.
|
||||
|
||||
### Streaming packages
|
||||
|
||||
@ -442,7 +442,7 @@ These settings affect the behavior of streaming App-V package assets to the clie
|
||||
|
||||
### Background streaming
|
||||
|
||||
The PowerShell cmdlet `Get-AppvClientConfiguration` can be used to determine the current mode for background streaming with the AutoLoad setting and modified with the cmdlet Set-AppvClientConfiguration or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can be disabled all together (value=0) or enabled for all packages (value=2), whether they have been launched.
|
||||
The Windows PowerShell cmdlet `Get-AppvClientConfiguration` can be used to determine the current mode for background streaming with the AutoLoad setting and modified with the cmdlet Set-AppvClientConfiguration or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can be disabled all together (value=0) or enabled for all packages (value=2), whether they have been launched.
|
||||
|
||||
### Optimized streaming
|
||||
|
||||
@ -458,7 +458,7 @@ App-V Packages require updating throughout the lifecycle of the application. App
|
||||
|
||||
### Package removal
|
||||
|
||||
The behavior of the App-V Client when packages are removed depends on the method used for removal. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but retains the package store location and COW locations. When the PowerShell cmdlet `Remove-AppVClientPackge` is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server does not perform a Remove operation. Neither operation will remove the Package Store package files.
|
||||
The behavior of the App-V Client when packages are removed depends on the method used for removal. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but retains the package store location and COW locations. When the Windows PowerShell cmdlet `Remove-AppVClientPackge` is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server does not perform a Remove operation. Neither operation will remove the Package Store package files.
|
||||
|
||||
## <a href="" id="bkmk-roaming-reg-data"></a>Roaming registry and data
|
||||
|
||||
@ -599,11 +599,11 @@ This process will re-create both the local and network locations for AppData and
|
||||
## App-V client application lifecycle management
|
||||
|
||||
|
||||
In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of PowerShell commands initiated on the computer running the App-V Client.
|
||||
In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of Windows PowerShell commands initiated on the computer running the App-V Client.
|
||||
|
||||
This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012, see [Integrating Virtual Application Management with App-V 5 and Configuration Manager 2012 SP1](https://www.microsoft.com/en-us/download/details.aspx?id=38177).
|
||||
|
||||
The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) or use Windows PowerShell:
|
||||
The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with Windows PowerShell commands. See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) or use Windows PowerShell:
|
||||
|
||||
``` syntax
|
||||
get-command *appv*
|
||||
@ -611,7 +611,7 @@ get-command *appv*
|
||||
|
||||
### Publishing refresh
|
||||
|
||||
The publishing refresh process is comprised of several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process at user logon, machine startup, and at scheduled intervals. The configuration of the client during setup listed above is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following PowerShell cmdlets:
|
||||
The publishing refresh process is comprised of several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process at user logon, machine startup, and at scheduled intervals. The configuration of the client during setup listed above is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following Windows PowerShell cmdlets:
|
||||
|
||||
- **Add-AppVPublishingServer:** Configures the client with an App-V Publishing Server that provides App-V packages.
|
||||
|
||||
@ -629,7 +629,7 @@ The focus of the following sections is to detail the operations that occur durin
|
||||
|
||||
### Adding an App-V package
|
||||
|
||||
Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the `Add-AppVClientPackage` cmdlet in PowerShell, except during the publishing refresh add process, the configured publishing server is contacted and passes a high-level list of applications back to the client to pull more detailed information and not a single package add operation. The process continues by configuring the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following is a detailed workflow of the process, assuming the package is configured for Fault Streaming.
|
||||
Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the `Add-AppVClientPackage` cmdlet in Windows PowerShell, except during the publishing refresh add process, the configured publishing server is contacted and passes a high-level list of applications back to the client to pull more detailed information and not a single package add operation. The process continues by configuring the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following is a detailed workflow of the process, assuming the package is configured for Fault Streaming.
|
||||
|
||||
**How to add an App-V package**
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Apply the Deployment Configuration File by Using PowerShell (Windows 10)
|
||||
description: How to Apply the Deployment Configuration File by Using PowerShell
|
||||
title: How to Apply the Deployment Configuration File by Using Windows PowerShell (Windows 10)
|
||||
description: How to Apply the Deployment Configuration File by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Apply the Deployment Configuration File by Using PowerShell
|
||||
# How to Apply the Deployment Configuration File by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
@ -19,31 +19,22 @@ The dynamic deployment configuration file is applied when a package is added or
|
||||
|
||||
**c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
||||
|
||||
**To Apply the Deployment Configuration File Using PowerShell**
|
||||
**To Apply the Deployment Configuration File Using Windows PowerShell**
|
||||
|
||||
- To specify a new default set of configurations for all users who will run the package on a specific computer, using a PowerShell console type the following:
|
||||
- To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, type the following:
|
||||
|
||||
**Add-AppVClientPackage –Path c:\\Packages\\Contoso\\MyApp.appv -DynamicDeploymentConfiguration c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
||||
`Add-AppVClientPackage -Path c:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration c:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml`
|
||||
|
||||
**Note**
|
||||
**Note**<br>
|
||||
This command captures the resulting object into $pkg. If the package is already present on the computer, the **Set-AppVclientPackage** cmdlet can be used to apply the deployment configuration document:
|
||||
|
||||
**Set-AppVClientPackage –Name Myapp –Path c:\\Packages\\Contoso\\MyApp.appv -DynamicDeploymentConfiguration c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
||||
`Set-AppVClientPackage -Name Myapp -Path c:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration c:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml`
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
**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).
|
||||
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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Apply the User Configuration File by Using PowerShell (Windows 10)
|
||||
description: How to Apply the User Configuration File by Using PowerShell
|
||||
title: How to Apply the User Configuration File by Using Windows PowerShell (Windows 10)
|
||||
description: How to Apply the User Configuration File by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Apply the User Configuration File by Using PowerShell
|
||||
# How to Apply the User Configuration File by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
@ -21,26 +21,19 @@ Use the following procedure to specify a user-specific configuration file. The f
|
||||
|
||||
**To apply a user Configuration file**
|
||||
|
||||
1. To add the package to the computer using the PowerShell console type the following command:
|
||||
1. To add the package to the computer using the Windows PowerShell console, type the following command:
|
||||
|
||||
**Add-AppVClientPackage c:\\Packages\\Contoso\\MyApp.appv**.
|
||||
`Add-AppVClientPackage c:\Packages\Contoso\MyApp.appv`
|
||||
|
||||
2. Use the following command to publish the package to the user and specify the updated the dynamic user configuration file:
|
||||
|
||||
**Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath c:\\Packages\\Contoso\\config.xml**
|
||||
`Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath c:\Packages\Contoso\config.xml`
|
||||
|
||||
**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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -13,93 +13,50 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
|
||||
Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
|
||||
|
||||
To upgrade a package in some earlier versions of App-V, you had to perform several steps, including disabling the connection group and modifying the connection group’s XML definition file.
|
||||
You can configure a connection group to accept any version of a package, which enables you to upgrade the package without having to disable the connection group:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task description with App-V</th>
|
||||
<th align="left">How to perform the task with App-V</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You can configure a connection group to accept any version of a package, which enables you to upgrade the package without having to disable the connection group.</p>
|
||||
<p><strong>How the feature works:</strong></p>
|
||||
<ul>
|
||||
<li><p>If the connection group has access to multiple versions of a package, the latest version is used.</p></li>
|
||||
<li><p>If the connection group contains an optional package that has an incorrect version, the package is ignored and won’t block the connection group’s virtual environment from being created.</p></li>
|
||||
<li><p>If the connection group contains a non-optional package that has an incorrect version, the connection group’s virtual environment cannot be created.</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">Steps</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Server – Management Console</p></td>
|
||||
<td align="left"><ol>
|
||||
<li><p>In the Management Console, select <strong>CONNECTION GROUPS</strong>.</p></li>
|
||||
<li><p>Select the correct connection group from the Connection Groups library.</p></li>
|
||||
<li><p>Click <strong>EDIT</strong> in the CONNECTED PACKAGES pane.</p></li>
|
||||
<li><p>Select <strong>Use Any Version</strong> check box next to the package name, and click <strong>Apply</strong>.</p></li>
|
||||
</ol>
|
||||
<p>For more about adding or upgrading packages, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V Client on a Stand-alone computer</p></td>
|
||||
<td align="left"><ol>
|
||||
<li><p>Create the connection group XML document.</p></li>
|
||||
<li><p>For the package to be upgraded, set the <strong>Package</strong> tag attribute <strong>VersionID</strong> to an asterisk (<strong>*</strong>).</p></li>
|
||||
<li><p>Use the following cmdlet to add the connection group, and include the path to the connection group XML document:</p>
|
||||
<p><strong>Add-AppvClientConnectionGroup</strong></p></li>
|
||||
<li><p>When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:</p>
|
||||
<ul>
|
||||
<li><p>RemoveAppvClientPackage</p></li>
|
||||
<li><p>Add-AppvClientPackage</p></li>
|
||||
<li><p>Publish-AppvClientPackage</p></li>
|
||||
</ul></li>
|
||||
</ol>
|
||||
<p>For more information, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
- If the connection group has access to multiple versions of a package, the latest version is used.
|
||||
|
||||
|
||||
- If the connection group contains an optional package that has an incorrect version, the package is ignored and won’t block the connection group’s virtual environment from being created.
|
||||
|
||||
- If the connection group contains a non-optional package that has an incorrect version, the connection group’s virtual environment cannot be created.
|
||||
|
||||
## To make a connection group ignore the package version by using the App-V Server Management Console
|
||||
|
||||
1. In the Management Console, select **CONNECTION GROUPS**.
|
||||
|
||||
2. Select the correct connection group from the Connection Groups library.
|
||||
|
||||
3. Click **EDIT** in the CONNECTED PACKAGES pane.
|
||||
|
||||
4. Select **Use Any Version** check box next to the package name, and click **Apply**.
|
||||
|
||||
For more about adding or upgrading packages, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).
|
||||
|
||||
## To make a connection group ignore the package version from the App-V client on a stand-alone computer
|
||||
|
||||
1. Create the connection group XML document.
|
||||
|
||||
2. For the package to be upgraded, set the **Package** tag attribute **VersionID** to an asterisk (**\***).
|
||||
|
||||
3. Use the following cmdlet to add the connection group, and include the path to the connection group XML document:
|
||||
|
||||
`Add-AppvClientConnectionGroup`
|
||||
|
||||
4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:
|
||||
|
||||
- RemoveAppvClientPackage
|
||||
- Add-AppvClientPackage
|
||||
- Publish-AppvClientPackage
|
||||
|
||||
For more information, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ Deploying packages and connection groups using the App-V publishing server is he
|
||||
|
||||
Use the following steps to configure the App-V client to receive updates from the publishing server.
|
||||
|
||||
**Note**
|
||||
**Note**<br>
|
||||
For the following procedures the management server was installed on a computer named **MyMgmtSrv**, and the publishing server was installed on a computer named **MyPubSrv**.
|
||||
|
||||
|
||||
@ -28,56 +28,37 @@ For the following procedures the management server was installed on a computer n
|
||||
|
||||
2. To open the management console click the following link, open a browser and type the following: http://MyMgmtSrv/AppvManagement/Console.html in a web browser, and import, publish, and entitle all the packages and connection groups which will be necessary for a particular set of users.
|
||||
|
||||
3. On the computer running the App-V client, open an elevated PowerShell command prompt, run the following command:
|
||||
3. On the computer running the App-V client, open an elevated Windows PowerShell command prompt, and run the following command:
|
||||
|
||||
**Add-AppvPublishingServer -Name ABC -URL http:// MyPubSrv/AppvPublishing**
|
||||
`Add-AppvPublishingServer -Name ABC -URL http://MyPubSrv/AppvPublishing`
|
||||
|
||||
This command will configure the specified publishing server. You should see output similar to the following:
|
||||
|
||||
|
||||
```
|
||||
Id : 1
|
||||
|
||||
SetByGroupPolicy : False
|
||||
|
||||
Name : ABC
|
||||
|
||||
URL : http:// MyPubSrv/AppvPublishing
|
||||
|
||||
GlobalRefreshEnabled : False
|
||||
|
||||
GlobalRefreshOnLogon : False
|
||||
|
||||
GlobalRefreshInterval : 0
|
||||
|
||||
GlobalRefreshIntervalUnit : Day
|
||||
|
||||
UserRefreshEnabled : True
|
||||
|
||||
UserRefreshOnLogon : True
|
||||
|
||||
UserRefreshInterval : 0
|
||||
|
||||
UserRefreshIntervalUnit : Day
|
||||
```
|
||||
|
||||
The returned Id – in this case 1
|
||||
4. On the computer running the App-V client, open a Windows PowerShell command prompt, and type the following command:
|
||||
|
||||
4. On the computer running the App-V client, open a PowerShell command prompt, and type the following command:
|
||||
|
||||
**Sync-AppvPublishingServer -ServerId 1**
|
||||
`Sync-AppvPublishingServer -ServerId 1`
|
||||
|
||||
The command will query the publishing server for the packages and connection groups that need to be added or removed for this particular client based on the entitlements for the packages and connection groups as configured on the management server.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -15,11 +15,11 @@ Applies to: Windows 10, version 1607
|
||||
|
||||
You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods:
|
||||
|
||||
- [How to use PowerShell cmdlets to create the user-entitled connection groups](#bkmk-posh-userentitled-cg)
|
||||
- [How to use Windows PowerShell cmdlets to create user-entitled connection groups](#how-to-use-powershell-cmdlets-to-create-user-entitled-connection-groups)
|
||||
|
||||
- [How to use the App-V Server to create the user-entitled connection groups](#bkmk-appvserver-userentitled-cg)
|
||||
- [How to use the App-V Server to create user-entitled connection groups](#how-to-use-the-app-v-server-to-create-user-entitled-connection-groups)
|
||||
|
||||
**What to know before you start:**
|
||||
## What to know before you start:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -47,27 +47,27 @@ You can create user-entitled connection groups that contain both user-published
|
||||
|
||||
|
||||
|
||||
**How to use PowerShell cmdlets to create user-entitled connection groups**
|
||||
## How to use Windows PowerShell cmdlets to create user-entitled connection groups
|
||||
|
||||
1. Add and publish packages by using the following commands:
|
||||
|
||||
**Add-AppvClientPackage Pacakage1\_AppV\_file\_Path**
|
||||
|
||||
**Add-AppvClientPackage Pacakage2\_AppV\_file\_Path**
|
||||
|
||||
**Publish-AppvClientPackage -PackageId Package1\_ID -VersionId Package1\_Version ID -Global**
|
||||
|
||||
**Publish-AppvClientPackage -PackageId Package2\_ID -VersionId Package2\_ID**
|
||||
|
||||
```
|
||||
Add-AppvClientPackage <Package1_AppV_file_Path>
|
||||
Add-AppvClientPackage <Package2_AppV_file_Path>
|
||||
Publish-AppvClientPackage -PackageId <Package1_ID> -VersionId <Package1_Version_ID> -Global
|
||||
Publish-AppvClientPackage -PackageId <Package2_ID> -VersionId <Package2_Version_ID>
|
||||
```
|
||||
|
||||
2. Create the connection group XML file. For more information, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
|
||||
3. Add and publish the connection group by using the following commands:
|
||||
|
||||
```
|
||||
Add-AppvClientConnectionGroup <Connection_Group_XML_file_Path>
|
||||
Enable-AppvClientConnectionGroup -GroupId <CG_Group_ID> -VersionId <CG_Version_ID>
|
||||
```
|
||||
|
||||
**Add-AppvClientConnectionGroup Connection\_Group\_XML\_file\_Path**
|
||||
|
||||
**Enable-AppvClientConnectionGroup -GroupId CG\_Group\_ID -VersionId CG\_Version\_ID**
|
||||
|
||||
**How to use the App-V Server to create user-entitled connection groups**
|
||||
## How to use the App-V Server to create user-entitled connection groups
|
||||
|
||||
1. Open the App-V Management Console.
|
||||
|
||||
@ -75,7 +75,9 @@ You can create user-entitled connection groups that contain both user-published
|
||||
|
||||
3. Follow the instructions in [How to Create a Connection Group](appv-create-a-connection-group.md) to create the connection group, and add the user-published and globally published packages.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use PowerShell to create connection groups, see [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use Windows PowerShell to create connection groups, see [How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
When you place packages in a connection group, their package root paths are merged. If you remove packages, only the remaining packages maintain the merged root.
|
||||
|
||||
@ -33,27 +33,17 @@ When you place packages in a connection group, their package root paths are merg
|
||||
|
||||
To reprioritize the applications in your connection group, use the arrows in the **PACKAGES IN** pane.
|
||||
|
||||
**Important**
|
||||
**Important**<br>
|
||||
By default, the Active Directory Domain Services access configurations that are associated with a specific application are not added to the connection group. To transfer the Active Directory access configuration, select **ADD PACKAGE ACCESS TO GROUP ACCESS**, which is located in the **PACKAGES IN** pane.
|
||||
|
||||
|
||||
|
||||
6. After adding all the applications and configuring Active Directory access, click **Apply**.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -15,63 +15,42 @@ Applies to: Windows 10, version 1607
|
||||
|
||||
App-V package accelerators automatically generate new virtual application packages.
|
||||
|
||||
**Note**
|
||||
You can use PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using 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**
|
||||
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.
|
||||
>**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.
|
||||
|
||||
|
||||
## To create a package accelerator
|
||||
|
||||
**Important**
|
||||
Before you begin the following procedure, you should 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.
|
||||
|
||||
|
||||
|
||||
**To create a package accelerator**
|
||||
|
||||
1. **Important**
|
||||
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.
|
||||
|
||||
|
||||
|
||||
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 that is running the sequencer, click **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**.
|
||||
|
||||
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).
|
||||
|
||||
**Tip**
|
||||
**Tip**<br>
|
||||
Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer.
|
||||
|
||||
|
||||
|
||||
|
||||
Click **Next**.
|
||||
|
||||
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.
|
||||
|
||||
**Tip**
|
||||
**Tip**<br>
|
||||
Copy the folder that contains the required installation files to the computer running the Sequencer.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
**Note**
|
||||
**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.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
@ -84,25 +63,15 @@ Before you begin the following procedure, you should perform the following:
|
||||
|
||||
11. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**.
|
||||
|
||||
**Important**
|
||||
**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.
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
**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).
|
||||
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
|
||||
|
||||
|
||||
[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)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ Use one of the following methods to publish packages to App-V client computers w
|
||||
| - | - |
|
||||
| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.|
|
||||
| Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. |
|
||||
| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|
|
||||
| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|
|
||||
|
||||
|
||||
|
||||
|
||||
@ -88,7 +88,7 @@ You can deploy Office 2010 packages by using any of the following App-V deployme
|
||||
|
||||
- App-V server
|
||||
|
||||
- Stand-alone through PowerShell commands
|
||||
- Stand-alone through Windows PowerShell commands
|
||||
|
||||
## Office App-V package management and customization
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
>**Note** If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10.
|
||||
>**Note**<br>If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10.
|
||||
|
||||
You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V Security Considerations](appv-security-considerations.md).
|
||||
|
||||
@ -102,7 +102,7 @@ The reporting information will be maintained until it is successfully sent to th
|
||||
|
||||
If you want to retrieve report information, you must use Microsoft SQL Server Reporting Services (SSRS) which is available with Microsoft SQL. SSRS is not installed when you install the App-V reporting server and it must be deployed separately to generate the associated reports.
|
||||
|
||||
For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
|
||||
## Other resources for the App-V server
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
@ -737,8 +737,8 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
[How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
|
||||
[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
[How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -23,15 +23,8 @@ Starting in App-V 5.0 SP3, you can configure the App-V client so that only admin
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
|
||||
|
||||
**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).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
To instead use Windows PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
|
||||
|
||||
## 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).
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Enable Reporting on the App-V Client by Using PowerShell (Windows 10)
|
||||
description: How to Enable Reporting on the App-V Client by Using PowerShell
|
||||
title: How to Enable Reporting on the App-V Client by Using Windows PowerShell (Windows 10)
|
||||
description: How to Enable Reporting on the App-V Client by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Enable Reporting on the App-V Client by Using PowerShell
|
||||
# How to Enable Reporting on the App-V Client by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
@ -19,7 +19,7 @@ Use the following procedure to configure the App-V for reporting.
|
||||
|
||||
1. Enable the App-V client. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** PowerShell to configure appropriate Reporting Configuration settings:
|
||||
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -75,7 +75,7 @@ Use the following procedure to configure the App-V for reporting.
|
||||
|
||||
3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server.
|
||||
|
||||
Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** PowerShell cmdlet.
|
||||
Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** cmdlet.
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
@ -85,7 +85,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
|
||||
|
||||
**Note**
|
||||
For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
|
||||
For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
|
||||
|
||||
5. Run the scripts on the computer running Microsoft SQL Server.
|
||||
|
||||
@ -95,14 +95,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -56,13 +56,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
[How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell (Windows 10)
|
||||
description: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
|
||||
title: How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell (Windows 10)
|
||||
description: How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,12 +9,12 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
|
||||
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
|
||||
The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell:
|
||||
The following sections explain how to perform various management tasks on a stand-alone client computer by using Windows PowerShell:
|
||||
|
||||
- [To return a list of packages](#bkmk-return-pkgs-standalone-posh)
|
||||
|
||||
@ -169,7 +169,7 @@ Use the following information to remove a package from the computer.
|
||||
**Example**: Remove-AppvClientPackage “ContosoApplication”
|
||||
|
||||
**Note**
|
||||
App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](http://go.microsoft.com/fwlink/?LinkId=324466).
|
||||
App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).
|
||||
|
||||
|
||||
|
||||
@ -213,7 +213,7 @@ To use the App-V Management console to set this configuration, see [How to Publi
|
||||
## <a href="" id="bkmk-understd-pend-pkgs"></a>Understanding pending packages (UserPending and GlobalPending)
|
||||
|
||||
|
||||
**Starting in App-V 5.0 SP2**: If you run a PowerShell cmdlet that affects a package that is currently in use, the task that you are trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows:
|
||||
**Starting in App-V 5.0 SP2**: If you run a Windows PowerShell cmdlet that affects a package that is currently in use, the task that you are trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -273,24 +273,15 @@ The pending task will run later, according to the following rules:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
For more information about pending tasks, see [Upgrading an in-use App-V package](appv-application-publishing-and-client-interaction.md#upgrading-an-in-use-app-v-package).
|
||||
|
||||
**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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell (Windows 10)
|
||||
description: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
|
||||
title: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell (Windows 10)
|
||||
description: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
|
||||
# How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
@ -82,8 +82,8 @@ This topic explains the following procedures:
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Disable -AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Disable -AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -116,19 +116,19 @@ This topic explains the following procedures:
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Set-AppvClientConfiguration</p></td>
|
||||
<td align="left"><p>–RequirePublishAsAdmin</p>
|
||||
<td align="left"><p>-RequirePublishAsAdmin</p>
|
||||
<ul>
|
||||
<li><p>0 - False</p></li>
|
||||
<li><p>1 - True</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>Set-AppvClientConfiguration –RequirePublishAsAdmin1</p></td>
|
||||
<td align="left"><p>Set-AppvClientConfiguration -RequirePublishAsAdmin 1</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
**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).
|
||||
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
|
||||
|
||||
@ -136,12 +136,3 @@ This topic explains the following procedures:
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -161,7 +161,7 @@ ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
|
||||
## Converting packages created using a prior version of App-V
|
||||
|
||||
|
||||
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion. App-V packages created with App-V 5.x don't need to be converted.
|
||||
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses Windows PowerShell to convert packages and can help automate the process if you have many packages that require conversion. App-V packages created with App-V 5.x don't need to be converted.
|
||||
|
||||
|
||||
**Important**
|
||||
|
||||
@ -15,7 +15,7 @@ Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
|
||||
2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppvClientConfiguration** with any required parameters. For example:
|
||||
|
||||
|
||||
@ -536,9 +536,9 @@ Removing FB1 does not require the original application installer. After completi
|
||||
|
||||
3. Move to **Create Package**.
|
||||
|
||||
**PowerShell** - Update an Existing Virtual Application Package.
|
||||
**Windows PowerShell** - Update an Existing Virtual Application Package.
|
||||
|
||||
1. Open an elevated PowerShell session.
|
||||
1. Open an elevated Windows PowerShell session.
|
||||
|
||||
2. Import-module **appvsequencer**.
|
||||
|
||||
@ -619,7 +619,7 @@ When publishing a virtual application package, the App-V Client will detect if a
|
||||
|
||||
|
||||
|
||||
### Disabling a Dynamic Configuration using Powershell
|
||||
### Disabling a Dynamic Configuration by using Windows Powershell
|
||||
|
||||
- For already published packages, you can use `Set-AppVClientPackage –Name Myapp –Path c:\Packages\Apps\MyApp.appv` without
|
||||
|
||||
@ -631,9 +631,9 @@ When publishing a virtual application package, the App-V Client will detect if a
|
||||
|
||||
For documentation on How to Apply a Dynamic Configuration, see:
|
||||
|
||||
- [How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
- [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
|
||||
- [How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -653,7 +653,7 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Account for Synchronous Script Execution during Package Lifecycle.</p></td>
|
||||
<td align="left"><p>If script collateral is embedded in the package, Add (Powershell) may be significantly slower.</p>
|
||||
<td align="left"><p>If script collateral is embedded in the package, Add cmdlets may be significantly slower.</p>
|
||||
<p>Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.</p></td>
|
||||
<td align="left"><p>Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.</p></td>
|
||||
<td align="left"><p>This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.</p></td>
|
||||
@ -677,18 +677,15 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
||||
|
||||
- Open AppxManifest.xml and locate the following:
|
||||
|
||||
<appv:Extension Category="AppV.Fonts">
|
||||
```
|
||||
<appv:Extension Category="AppV.Fonts">
|
||||
<appv:Fonts>
|
||||
<appv:Font Path="[{Fonts}]\private\CalibriL.ttf" DelayLoad="true"></appv:Font>
|
||||
</appv:Fonts>
|
||||
```
|
||||
|
||||
<appv:Fonts>
|
||||
**Note** If there are fonts marked as **DelayLoad**, those will not impact first launch.
|
||||
|
||||
<appv:Font Path="\[{Fonts}\]\\private\\CalibriL.ttf" DelayLoad="true"></appv:Font>
|
||||
|
||||
**Note**
|
||||
If there are fonts marked as **DelayLoad**, those will not impact first launch.
|
||||
|
||||
|
||||
|
||||
</appv:Fonts>
|
||||
|
||||
### Excluding virtual fonts from the package
|
||||
|
||||
@ -698,11 +695,11 @@ Use the dynamic configuration file that best suits the user scope – deployment
|
||||
|
||||
Fonts
|
||||
|
||||
-->
|
||||
|
||||
<Fonts Enabled="false" />
|
||||
|
||||
<!--
|
||||
```
|
||||
-->
|
||||
<Fonts Enabled="false" />
|
||||
<!--
|
||||
```
|
||||
|
||||
## <a href="" id="bkmk-terms1"></a> App-V Performance Guidance Terminology
|
||||
|
||||
@ -729,7 +726,7 @@ The following terms are used when describing concepts and actions related to App
|
||||
|
||||
- From the point that users initiate a log-in to when they are able to manipulate the desktop.
|
||||
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage Powershell** commands are initiated.
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in Windows PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage** Windows Powershell commands are initiated.
|
||||
|
||||
- From start to completion of the publishing refresh. In standalone instances, this is the first to last virtual application published.
|
||||
|
||||
|
||||
@ -21,20 +21,12 @@ After you create a connection group, you must publish it to computers that run t
|
||||
|
||||
2. Right-click the connection group to be published, and select **publish**.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -36,22 +36,14 @@ The ability to enable only administrators to publish or unpublish packages (desc
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
|
||||
To instead use Windows PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
|
||||
|
||||
**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
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -120,13 +120,13 @@ When you run Repair-AppvClientConnectionGroup, the following error is displayed,
|
||||
|
||||
- Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-AppvClientConnectionGroup command.
|
||||
|
||||
Determine which packages are available to users and then run the Repair-AppvClientPackage command once for each package. Use PowerShell cmdlets to do the following:
|
||||
Determine which packages are available to users and then run the **Repair-AppvClientPackage** command once for each package. Use Windows PowerShell cmdlets to do the following:
|
||||
|
||||
1. Get all the packages in a connection group.
|
||||
|
||||
2. Check to see if each package is currently published.
|
||||
|
||||
3. If the package is currently published, run Repair-AppvClientPackage on that package.
|
||||
3. If the package is currently published, run **Repair-AppvClientPackage** on that package.
|
||||
|
||||
## Icons not displayed properly in Sequencer
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ Use any of the following methods to open a local application inside the App-V vi
|
||||
|
||||
- [RunVirtual registry key](#bkmk-runvirtual-regkey)
|
||||
|
||||
- [Get-AppvClientPackage PowerShell cmdlet](#bkmk-get-appvclientpackage-posh)
|
||||
- [Get-AppvClientPackage Windows PowerShell cmdlet](#bkmk-get-appvclientpackage-posh)
|
||||
|
||||
- [Command line switch /appvpid:<PID>](#bkmk-cl-switch-appvpid)
|
||||
|
||||
@ -101,7 +101,7 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
|
||||
@="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555
|
||||
```
|
||||
|
||||
## <a href="" id="bkmk-get-appvclientpackage-posh"></a>Get-AppvClientPackage PowerShell cmdlet
|
||||
## <a href="" id="bkmk-get-appvclientpackage-posh"></a>Get-AppvClientPackage Windows PowerShell cmdlet
|
||||
|
||||
|
||||
You can use the **Start-AppVVirtualProcess** cmdlet to retrieve the package name and then start a process within the specified package's virtual environment. This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user