Making sure PowerShell has Windows in front of it

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

View File

@ -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 groups 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 wont block the connection groups 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 groups 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 wont block the connection groups virtual environment from being created.
- If the connection group contains a non-optional package that has an incorrect version, the connection groups 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)