deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-16 07:17:24 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #96 from JanKeller1/6675772d

Browse Source 
Removing unneeded files and removing links to those files
This commit is contained in:
Brian Lich 2016-07-29 18:02:02 -07:00 committed by GitHub
commit a4202ede0c
13 changed files with 12 additions and 1016 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/manage/appv-client-configuration-settings.md
View File

@ -10,7 +10,7 @@ ms.prod: w10
# About Client Configuration Settings
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V see [Administering App-V by Using PowerShell](https://microsoft.sharepoint.com/teams/osg_core_dcp/cpub/partner/Shared%20Documents/APPV&UEV-for-Windows-RS1/App-V/App-V%20updated%20topics%20from%20JAN%20-%20PM%20reviews/appv-administering-appv-with-powershell.md).
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
@ -108,8 +108,6 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Deploying the App-V Sequencer and Client](https://microsoft.sharepoint.com/teams/osg_core_dcp/cpub/partner/Shared%20Documents/APPV&UEV-for-Windows-RS1/App-V/App-V%20updated%20topics%20from%20JAN%20-%20PM%20reviews/appv-deploying-the-appv-sequencer-and-client.md)
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](https://microsoft.sharepoint.com/teams/osg_core_dcp/cpub/partner/Shared%20Documents/APPV&UEV-for-Windows-RS1/App-V/App-V%20updated%20topics%20from%20JAN%20-%20PM%20reviews/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
[How to Deploy the App-V Client](https://microsoft.sharepoint.com/teams/osg_core_dcp/cpub/partner/Shared%20Documents/APPV&UEV-for-Windows-RS1/App-V/App-V%20updated%20topics%20from%20JAN%20-%20PM%20reviews/appv-deploy-the-appv-client.md)
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)

7
windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md
View File

@ -72,11 +72,8 @@ To upgrade a package in some earlier versions of App-V, you had to perform sever
<li><p>Publish-AppvClientPackage</p></li>
</ul></li>
</ol>
<p>For more information, see:</p>
<ul>
<li><p>The example XML file, <strong>Connection group XML file with optional packages</strong>, in this section: [How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md#bkmk-apps-plugs-optional)</p></li>
<li><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></li>
</ul></td>
<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>

2
windows/manage/appv-connection-group-file.md
View File

@ -139,7 +139,7 @@ In the &lt;Packages&gt; section of the connection group XML file, you list the m
<li><p><strong>“true”</strong> – package is optional in the connection group</p></li>
<li><p><strong>“false”</strong> – package is required in the connection group</p></li>
</ul>
<p>See [How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md).</p></td>
</td>
</tr>
</tbody>
</table>

11
windows/manage/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md
View File

@ -80,14 +80,3 @@ You can create user-entitled connection groups that contain both user-published
[Managing Connection Groups](appv-managing-connection-groups.md)
[How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md)
 
 

63
windows/manage/appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md
View File

@ -1,63 +0,0 @@
---
title: How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer (Windows 10)
description: How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer
Use the following information to install the Microsoft Application Virtualization (App-V) client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md).
**To deploy the App-V client and App-V 4.6.x client on the same computer**
1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6.
- [Microsoft Application Virtualization 4.6 Service Pack 2](http://go.microsoft.com/fwlink/?LinkId=262687)
- [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)
2. Install the App-V client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V client.
3. Convert or re-sequence the packages gradually.
- To convert the packages, use the App-V package converter and convert the required packages to the App-V (**.appv**) file format.
- To re-sequence the packages, consider using the latest version of the Sequencer for best results.
For more information about publishing packages, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md).
4. Deploy packages to the client computers.
5. Convert extension points, as needed. For more information, see the following resources:
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md)
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md)
- [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
6. Test that your App-V packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
**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).
## Related topics
[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
 
 

345
windows/manage/appv-deploy-the-appv-client.md
View File

@ -1,345 +0,0 @@
---
title: How to Deploy the App-V Client (Windows 10)
description: How to Deploy the App-V Client
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Deploy the App-V Client
Use the following procedure to install the Microsoft Application Virtualization (App-V) client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer.
## What to do before you start
1. Review and install the software prerequisites:
Install the prerequisite software that corresponds to the version of App-V that you are installing:
- [About App-V](appv-about-appv.md)
- [App-V Prerequisites](appv-prerequisites.md)
2. Review the client coexistence and unsupported scenarios, as applicable to your installation:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>Deploying coexisting App-V clients</p></td>
<td align="left"><p>[Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)</p></td>
</tr>
<tr class="even">
<td align="left"><p>Unsupported or limited installation scenarios</p></td>
<td align="left"><p>See the client section in [App-V Supported Configurations](appv-supported-configurations.md)</p></td>
</tr>
</tbody>
</table>
3. Review the locations for client registry, log, and troubleshooting information:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>Client registry information</p></td>
<td align="left"><ul>
<li><p>By default, after you install the App-V client, the client information is stored in the registry in the following registry key:</p>
<p><strong>HKEY_LOCAL_MACHINE \ SOFTWARE \ MICROSOFT \ APPV \ CLIENT</strong></p></li>
<li><p>When you deploy a virtualized package to a computer that is running the App-V client, the associated package data is stored in the following location:</p>
<p><strong>C: \ ProgramData \ App-V</strong></p>
<p>However, you can reconfigure this location with the following registry key:</p>
<p><strong>HKEY_LOCAL_MACHINE \ SOFTWARE \ MICROSOFT \ SOFTWARE \ MICROSOFT \ APPV \ CLIENT \ STREAMING \ PACKAGEINSTALLATIONROOT</strong></p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Client log files</p></td>
<td align="left"><ul>
<li><p>For log file information that is associated with the App-V Client, search in the following log:</p>
<p><strong>Event logs / Applications and Services Logs / Microsoft / AppV</strong></p></li>
<li><p>In App-V 5.0 SP3, some logs were consolidated and moved to the following location:</p>
<p><strong>Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog</strong></p>
<p>For a list of the moved logs, see [About App-V 5.0 SP3](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50-sp3#bkmk-event-logs-moved).</p></li>
<li><p>Packages that are currently stored on computers that run the App-V Client are saved to the following location:</p>
<p><strong>C:\ProgramData\App-V\&lt;package id&gt;\&lt;version id&gt;</strong></p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Client installation troubleshooting information</p></td>
<td align="left"><p>See the error log in the <strong>%temp%</strong> folder. To review the log files, click <strong>Start</strong>, type <strong>%temp%</strong>, and then look for the <strong>appv_ log</strong>.</p></td>
</tr>
</tbody>
</table>
## To install the App-V Client
1. Copy the App-V client installation file to the computer on which it will be installed. Choose from the following client types:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Client type</th>
<th align="left">File to use</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Standard version of the client</p></td>
<td align="left"><p><strong>appv_client_setup.exe</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>Remote Desktop Services version of the client</p></td>
<td align="left"><p><strong>appv_client_setup_rds.exe</strong></p></td>
</tr>
</tbody>
</table>
2. Double-click the installation file, and click **Install**. Before the installation begins, the installer checks the computer for any missing [App-V Prerequisites](appv-prerequisites.md).
3. Review and accept the Software License Terms, choose whether to use Microsoft Update and whether to participate in the Microsoft Customer Experience Improvement Program, and click **Install**.
4. On the **Setup completed successfully** page, click **Close**.
The installation creates the following entries for the App-V client in **Programs**:
- **.exe**
- **.msi**
- **language pack**
**Note**  
After the installation, only the .exe file can be uninstalled.
## To install the App-V client using a script
1. Install all of the required prerequisite software on the target computers. See [What to do before you start](#bkmk-clt-install-prereqs). If you install the client by using an .msi file, the installation will fail if any prerequisites are missing.
2. To use a script to install the App-V client, use the following parameters with **appv\_client\_setup.exe**.
**Note**  
The client Windows Installer (.msi) supports the same set of switches, except for the **/LOG** parameter.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>/INSTALLDIR</p></td>
<td align="left"><p>Specifies the installation directory. Example usage: <strong>/INSTALLDIR=C:\Program Files\AppV Client</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/CEIPOPTIN</p></td>
<td align="left"><p>Enables participation in the Customer Experience Improvement Program. Example usage: <strong>/CEIPOPTIN=[0|1]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/MUOPTIN</p></td>
<td align="left"><p>Enables Microsoft Update. Example usage: <strong>/MUOPTIN=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/PACKAGEINSTALLATIONROOT</p></td>
<td align="left"><p>Specifies the directory in which to install all new applications and updates. Example usage: <strong>/PACKAGEINSTALLATIONROOT='C:\App-V Packages'</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/PACKAGESOURCEROOT</p></td>
<td align="left"><p>Overrides the source location for downloading package content. Example usage: <strong>/PACKAGESOURCEROOT='http://packageStore'</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/AUTOLOAD</p></td>
<td align="left"><p>Specifies how new packages will be loaded by App-V on a specific computer. The following options are enabled: [1]; automatically load all packages [2]; or automatically load no packages [0].<strong>Example usage: /AUTOLOAD=[0|1|2]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/SHAREDCONTENTSTOREMODE</p></td>
<td align="left"><p>Specifies that streamed package contents will be not be saved to the local hard disk. Example usage: <strong>/SHAREDCONTENTSTOREMODE=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/MIGRATIONMODE</p></td>
<td align="left"><p>Allows the App-V client to modify the shortcuts and FTAs that are associated with the packages that are created with a previous version. Example usage: <strong>/MIGRATIONMODE=[0|1]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/ENABLEPACKAGESCRIPTS</p></td>
<td align="left"><p>Enables the scripts that are defined in the package manifest file or configuration files that should run. Example usage: <strong>/ENABLEPACKAGESCRIPTS=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/ROAMINGREGISTRYEXCLUSIONS</p></td>
<td align="left"><p>Specifies the registry paths that will not roam with a user profile. Example usage: <strong>/ROAMINGREGISTRYEXCLUSIONS=software\classes;software\clients</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/ROAMINGFILEEXCLUSIONS</p></td>
<td align="left"><p>Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: <strong>/ROAMINGFILEEXCLUSIONS 'desktop;my pictures'</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/S[1-5]PUBLISHINGSERVERNAME</p></td>
<td align="left"><p>Displays the name of the publishing server. Example usage: <strong>/S2PUBLISHINGSERVERNAME=MyPublishingServer</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/S[1-5]PUBLISHINGSERVERURL</p></td>
<td align="left"><p>Displays the URL of the publishing server. Example usage: <strong>/S2PUBLISHINGSERVERURL=\\pubserver</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/S[1-5]GLOBALREFRESHENABLED -</p></td>
<td align="left"><p>Enables a global publishing refresh. Example usage: <strong>/S2GLOBALREFRESHENABLED=[0|1]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/S[1-5]GLOBALREFRESHONLOGON</p></td>
<td align="left"><p>Initiates a global publishing refresh when a user logs on. Example usage: <strong>/S2LOGONREFRESH=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/S[1-5]GLOBALREFRESHINTERVAL -</p></td>
<td align="left"><p>Specifies the publishing refresh interval, where <strong>0</strong> indicates do not periodically refresh. Example usage: <strong>/S2PERIODICREFRESHINTERVAL=[0-744]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/S[1-5]GLOBALREFRESHINTERVALUNIT</p></td>
<td align="left"><p>Specifies the interval unit (Hours[0], Days[1]). Example usage: <strong>/S2GLOBALREFRESHINTERVALUNIT=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/S[1-5]USERREFRESHENABLED</p></td>
<td align="left"><p>Enables user publishing refresh. Example usage: <strong>/S2USERREFRESHENABLED=[0|1]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/S[1-5]USERREFRESHONLOGON</p></td>
<td align="left"><p>Initiates a user publishing refresh when a user logs on. Example usage: <strong>/S2LOGONREFRESH=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/S[1-5]USERREFRESHINTERVAL -</p></td>
<td align="left"><p>Specifies the publishing refresh interval, where <strong>0</strong> indicates do not periodically refresh. Example usage: <strong>/S2PERIODICREFRESHINTERVAL=[0-744]</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/S[1-5]USERREFRESHINTERVALUNIT</p></td>
<td align="left"><p>Specifies the interval unit (Hours[0], Days[1]). Example usage: <strong>/S2USERREFRESHINTERVALUNIT=[0|1]</strong></p></td>
</tr>
<tr class="even">
<td align="left"><p>/Log</p></td>
<td align="left"><p>Specifies a location where the log information is saved. The default location is %Temp%. Example usage: <strong>/log C:\logs\log.log</strong></p></td>
</tr>
<tr class="odd">
<td align="left"><p>/q</p></td>
<td align="left"><p>Specifies an unattended installation.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/REPAIR</p></td>
<td align="left"><p>Repairs a previous client installation.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/NORESTART</p></td>
<td align="left"><p>Prevents the computer from rebooting after the client installation.</p>
<p>The parameter prevents the end-user computer from rebooting after each update is installed and lets you schedule the reboot at your convenience. For example, you can install App-V and then install Hotfix Package Y without rebooting after the Service Pack installation. After the installation, you must reboot before you start using App-V.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/UNINSTALL</p></td>
<td align="left"><p>Uninstalls the client.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/ACCEPTEULA</p></td>
<td align="left"><p>Accepts the license agreement. This is required for an unattended installation. Example usage: <strong>/ACCEPTEULA</strong> or <strong>/ACCEPTEULA=1</strong>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/LAYOUT</p></td>
<td align="left"><p>Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V. No value is expected.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>/LAYOUTDIR</p></td>
<td align="left"><p>Specifies the layout directory. Requires a string value. Example usage: <strong>/LAYOUTDIR=”C:\Application Virtualization Client”</strong>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>/?, /h, /help</p></td>
<td align="left"><p>Requests help about the previous installation parameters.</p></td>
</tr>
</tbody>
</table>
## To install the App-V client by using the Windows Installer (.msi) file
1. Install the required prerequisites on the target computers. See [What to do before you start](#bkmk-clt-install-prereqs). If any prerequisites are not met, the installation will fail.
2. Ensure that the target computers do not have any pending restarts before you install the client using the App-V Windows Installer (.msi) files. The Windows Installer files do not flag a pending restart.
3. Deploy one of the following Windows Installer files to the target computer. The file that you specify must match the configuration of the target computer.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Type of deployment</th>
<th align="left">Deploy this file</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Computer is running a 32-bit Microsoft Windows operating system</p></td>
<td align="left"><p>appv_client_MSI_x86.msi</p></td>
</tr>
<tr class="even">
<td align="left"><p>Computer is running a 64-bit Microsoft Windows operating system</p></td>
<td align="left"><p>appv_client_MSI_x64.msi</p></td>
</tr>
<tr class="odd">
<td align="left"><p>You are deploying the App-V Remote Desktop Services client</p></td>
<td align="left"><p>appv_client_rds_MSI_x64.msi</p></td>
</tr>
</tbody>
</table>
4. Using the information in the following table, select the appropriate language pack **.msi** to install, based on the desired language for the target computer. The **xxxx** in the table refers to the target locale of the language pack.
**What to know before you start:**
- The language packs are common to both the standard App-V client and the Remote Desktop Services version of the App-V client.
- If you install the App-V client using the **.exe**, the installer will deploy only the language pack that matches the operating system running on the target computer.
- To deploy additional language packs on a target computer, use the procedure **To install the App-V client by using Windows Installer (.msi) file**.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Type of deployment</th>
<th align="left">Deploy this file</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Computer is running a 32-bit Microsoft Windows operating system</p></td>
<td align="left"><p>appv_client_LP_xxxx_ x86.msi</p></td>
</tr>
<tr class="even">
<td align="left"><p>Computer is running a 64-bit Microsoft Windows operating system</p></td>
<td align="left"><p>appv_client_LP_xxxx_ x64.msi</p></td>
</tr>
</tbody>
</table>
## 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
[Deploying App-V](appv-deploying-appv.md)
[About Client Configuration Settings](appv-client-configuration-settings.md)
[How to Uninstall the App-V Client](appv-uninstall-the-appv-client.md)

18
windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md
View File

@ -16,9 +16,9 @@ Use the following procedure to configure the App-V for reporting.
**To configure the computer running the App-V client for reporting**
1. Install the App-V client. For more information about installing the client see [How to Deploy the App-V Client](appv-deploy-the-appv-client.md).
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 installed 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** PowerShell to configure appropriate Reporting Configuration settings:
<table>
<colgroup>
@ -76,18 +76,12 @@ Use the following procedure to configure the App-V for reporting.
Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** PowerShell cmdlet.
**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 PowerShell](appv-administering-appv-with-powershell.md)
 
 

73
windows/manage/appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md
View File

@ -1,73 +0,0 @@
---
title: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer (Windows 10)
description: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer
Use the following procedure to migrate extension points from an App-V 4.6 package to a App-V package using the deployment configuration file.
**Note**  
This procedure assumes that you are running the latest version of App-V 4.6.
The following procedure does not require an App-V management server.
 
**To migrate extension points from a package from an App-V 4.6 package to a converted App-V package using the deployment configuration file**
1. Locate the directory that contains the deployment configuration file for the package you want to migrate. To set the policy, make the following update to the **userConfiguration** section:
**ManagingAuthority TakeoverExtensionPointsFrom46="true" PackageName=&lt;Package ID&gt;**
The following is an example of content from a deployment configuration file:
&lt;?xml version="1.0" ?&gt;
&lt;DeploymentConfiguration
xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration" PackageId=&lt;Package ID&gt; DisplayName=&lt;Display Name&gt;
&lt;MachineConfiguration/&gt;
&lt;UserConfiguration&gt;
&lt;ManagingAuthority TakeoverExtensionPointsFrom46="true"
PackageName=&lt;Package ID&gt;
&lt;/UserConfiguration&gt;
&lt;/DeploymentConfiguration&gt;
2. To add the App-V package, in an elevated PowerShell command prompt type:
PS&gt;**$pkg= Add-AppvClientPackage** **–Path** &lt;Path to package location&gt; -**DynamicDeploymentConfiguration** &lt;Path to the deployment configuration file&gt;
PS&gt;**Publish-AppVClientPackage $pkg**
3. To test the migration, open the virtual application using associated FTAs or shortcuts. The application opens with App-V. Both, the App-V 4.6 package and the converted App-V package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the 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).
## Related topics
[How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md)
[Operations for App-V](appv-operations.md)
 
 

62
windows/manage/appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md
View File

@ -1,62 +0,0 @@
---
title: How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User (Windows 10)
description: How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User
Use the following procedure to migrate packages created with App-V using the user configuration file.
**Note**  
This procedure assumes that you are running the latest version of App-V 4.6.
**To convert a package**
1. Locate the user configuration file for the package you want to convert. To set the policy, perform the following updates in the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="true" PackageName=&lt;Package ID&gt;**.
The following is an example of a user configuration file:
&lt;?xml version="1.0" ?&gt;
&lt;UserConfiguration PackageId=&lt;Package ID&gt; DisplayName=&lt;Name of the Package&gt;
xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration"&gt; &lt;ManagingAuthority TakeoverExtensionPointsFrom46="true"
PackageName=&lt;Package ID&gt;
&lt;/UserConfiguration&gt;
2. To add the App-V package, type the following in an elevated PowerShell command prompt window:
PS&gt;**$pkg= Add-AppvClientPackage –Path** &lt;Path to package location&gt;
PS&gt;**Publish-AppVClientPackage $pkg -DynamicUserConfiguration** &lt;Path to the user configuration file&gt;
3. Open the application using FTAs or shortcuts now. The application should open using App-V.
The App-V 4.6 package and the converted App-V package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the 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).
## Related topics
[Operations for App-V](appv-operations.md)
[How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md)
 
 

48
windows/manage/appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md
View File

@ -1,48 +0,0 @@
---
title: How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User (Windows 10)
description: How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User
Use the following procedure to revert an App-V package to the App-V file format using the user configuration file.
**To revert a package**
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md).
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=&lt;Package ID&gt;**
2. From an elevated command prompt, type:
PS&gt;**Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath** &lt;path to user configuration file&gt;
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6.
**Note**  
If you do not need the App-V package anymore, you can unpublish the App-V package and the extension points will automatically revert to App-V 4.6.
 
**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).
## Related topics
[Operations for App-V](appv-operations.md)
 
 

52
windows/manage/appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md
View File

@ -1,52 +0,0 @@
---
title: How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer (Windows 10)
description: How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer
Use the following procedure to revert extension points from an App-V package to the App-V 4.6 file format using the deployment configuration file.
**To revert a package**
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md).
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=&lt;Package ID&gt;**
2. From an elevated command prompt, type:
PS&gt;**Set-AppvClientPackage $pkg –DynamicDeploymentConfiguration** &lt;path to deployment configuration file&gt;
PS&gt;**Publish-AppVClientPackage $pkg –DynamicUserConfigurationType useDeploymentConfiguration**
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 package.
Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6.
**Note**  
If you do not need the App-V package anymore, you can unpublish the App-V package and the extension points will automatically revert to App-V 4.6.
 
**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).
## Related topics
[Operations for App-V](appv-operations.md)
 
 

44
windows/manage/appv-use-an-appv-46-sp1-application-from-an-appv-51-application.md
View File

@ -1,44 +0,0 @@
---
title: How to Use an App-V 4.6 Application From an App-V Application (Windows 10)
description: How to Use an App-V 4.6 Application From an App-V Application
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Use an App-V 4.6 Application From an App-V Application
Use the following procedure to run an App-V 4.6 application with App-V applications on a standalone client.
**Note**  
This procedure assumes that you are running the latest version of App-V 4.6.
**To run applications on a standalone client**
1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat.
2. Convert the packages, or create a new package for either of the applications using the App-V format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md).
3. Add and provision the package using the App-V management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md).
4. The converted application now runs using App-V and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V package and Adobe Acrobat is still running as an App-V 4.6 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
**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).
## Related topics
[Operations for App-V](appv-operations.md)
 
 

295
windows/manage/appv-use-optional-packages-in-connection-groups.md
View File

@ -1,295 +0,0 @@
---
title: How to Use Optional Packages in Connection Groups (Windows 10)
description: How to Use Optional Packages in Connection Groups
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
---
# How to Use Optional Packages in Connection Groups
Starting in Microsoft Application Virtualization (App-V) 5.0 SP3, you can add optional packages to your connection groups to simplify connection group management. The following table summarizes the tasks that you can complete more easily by using optional packages, and provides links to instructions for each task.
**Note**  
**Optional packages are not supported in releases prior to App-V 5.0 SP3.**
 
Before using optional packages, see [Requirements for using optional packages in connection groups](#bkmk-reqs-using-cg).
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Link to instructions</th>
<th align="left">Task</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Use one connection group, with optional packages, for multiple users who have different packages entitled to them](#bkmk-apps-plugs-optional)</p></td>
<td align="left"><p>Use a single connection group to make different groups of applications and plug-ins available to different end users.</p>
<p>For example, you want to distribute Microsoft Office to all end users, but distribute different plug-ins to different subsets of users.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Unpublish or delete an optional package, or unpublish an optional package and republish it later, without changing the connection group](#bkmk-unpub-del-optl-pkg)</p></td>
<td align="left"><p>Unpublish, delete, or republish an optional package without having to disable, remove, edit, add, and re-enable the connection group on the App-V Client.</p>
<p>You can also unpublish the optional package and republish it later without having to disable or republish the connection group.</p></td>
</tr>
</tbody>
</table>
 
## <a href="" id="bkmk-apps-plugs-optional"></a>Use one connection group, with optional packages, for multiple users with different packages entitled to them
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Task description</th>
<th align="left">How to perform the task</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>With App-V 5.0 SP3 and App-V</strong></p>
<p>You can add optional packages to connection groups, which enables you to provide different combinations of applications and plug-ins to different end users.</p>
<p><strong>Example</strong>: You want to distribute Microsoft Office to your end users, but enable a certain plug-in for only a subset of users.</p>
<p>To do this, create a connection group that contains a package with Office, and another package with Office plug-ins, and then make the plug-ins package optional.</p>
<p>End users who are not entitled to the plug-in package will still be able to run Office.</p></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> to display the Connection Groups library.</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>Optional</strong> next to the package name.</p></li>
<li><p>Select the <strong>ADD PACKAGE ACCESS TO GROUP ACCESS</strong> check box. This required step adds to the connection group the package entitlements that you configured earlier when you assigned packages to Active Directory groups.</p></li>
</ol></td>
</tr>
<tr class="even">
<td align="left"><p>App-V Server - PowerShell cmdlet</p></td>
<td align="left"><p>Use the following cmdlet, and specify the <strong>-Optional</strong> parameter:</p>
<p><strong>Add-AppvServerConnectionGroupPackage</strong></p>
<p><strong>Syntax:</strong></p>
<p><code>Add-AppvServerConnectionGroupPackage [-AppvServerConnectionGroup] &lt;SerializableConnectionGroup&gt; [[-AppvServerPackage] &lt;PackageVersion&gt;] [-Optional] [-Order &lt;int&gt;] [-UseAnyPackageVersion]</code></p>
<p><strong>Example:</strong></p>
<p><code>Add-AppvServerConnectionGroupPackage -Name &quot;Connection Group 1&quot; -PackageName &quot;Package 1&quot; -Optional</code></p></td>
</tr>
<tr class="odd">
<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, and set the <strong>Package</strong> tag attribute <strong>IsOptional</strong> to <strong>“true”.</strong></p></li>
<li><p>Use the following cmdlets to add and enable the connection group:</p>
<ul>
<li><p>Add-AppvClientConnectionGroup</p></li>
<li><p>Enable-AppvClientConnectionGroup</p></li>
</ul></li>
</ol>
<p><strong>Example connection group XML document with optional packages:</strong></p>
<pre class="syntax" space="preserve"><code>&lt;?xml version=&quot;1.0&quot; ?&gt;
&lt;AppConnectionGroup
xmlns=&quot;http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup&quot;
AppConnectionGroupId=&quot;8105CCD5-244B-4BA1-8888-E321E688D2CB&quot;
VersionId=&quot;84CE3797-F1CB-4475-A223-757918929EB4&quot;
DisplayName=&quot;Contoso Software Connection Group&quot; &gt;
&lt;Packages&gt;
&lt;Package
PackageId=&quot;7735d1a8-5ef9-4df9-a1cf-3aa92ef54fe7&quot;
VersionId=&quot;ec560d6f-e62e-48eb-a9e5-7c52a8c2e149&quot;
DisplayName=&quot;Contoso Business Manager&quot;
/&gt;
&lt;Package
PackageId=&quot;fc6fe0f7-be3d-4643-b37d-fc3f62d4dd5c&quot;
VersionId=&quot;c67a71cd-3542-4a48-93e8-20c643c50970&quot;
DisplayName=&quot;Contoso Forms&quot;
IsOptional=&quot;false&quot;
/&gt;
&lt;Package
PackageId=&quot;8f6301a5-4348-4039-9560-b27a5bb72711&quot;
VersionId=&quot;6c694b45-3e19-46c6-a327-d159aa39e1d2&quot;
DisplayName=&quot;Contoso Tax&quot;
IsOptional=&quot;true&quot;
/&gt;
&lt;Package
PackageId=&quot;89d701bc-d507-4299-b6b6-000000003472&quot;
VersionId=&quot;*&quot;
DisplayName=&quot;Contoso Accounts&quot;
IsOptional=&quot;true&quot;
/&gt;
&lt;/Packages&gt;
&lt;/AppConnectionGroup&gt;</code></pre></td>
</tr>
</tbody>
</table>
<p> </p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>With versions earlier than App-V 5.0 SP3</strong></p></td>
<td align="left"><p>You had to create many connection groups to make specific application and plug-in combinations available to specific users.</p></td>
</tr>
</tbody>
</table>
 
## <a href="" id="bkmk-unpub-del-optl-pkg"></a>Unpublish or delete an optional package, or unpublish an optional package and republish it later, without changing the connection group
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Task description</th>
<th align="left">How to perform the task</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>With App-V 5.0 SP3 and App-V</strong></p>
<p>You can unpublish, delete, or republish an optional package, which is in a connection group, without having to disable or re-enable the connection group on the App-V Client.</p>
<p>You can also unpublish an optional package and republish it later without having to disable or republish the connection group.</p>
<p><strong>Example</strong>: If you publish an optional package that contains a Microsoft Office plug-in, and you want to remove the plug-in, you can unpublish the package without having to disable the connection group.</p></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"><ul>
<li><p>To unpublish the package: In the Management Console, select elect the <strong>PACKAGES</strong> page, click or right-click the package that you want to unpublish, and click <strong>Unpublish</strong>.</p></li>
<li><p>To remove an optional package from a connection group: On the <strong>CONNECTION GROUPS</strong> page, select the package that you want to remove, and click the right arrow to remove the package from the connection group pane on the bottom left.</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>App-V Client on a Stand-alone computer</p></td>
<td align="left"><p>Use the following existing cmdlets:</p>
<ul>
<li><p>Unpublish-AppvClientPackage</p></li>
<li><p>Remove-AppvClientPackage</p></li>
</ul>
<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>
<tr class="even">
<td align="left"><p><strong>With versions earlier than App-V 5.0 SP3</strong></p></td>
<td align="left"><p>You had to:</p>
<ol>
<li><p>Remove the connection group from each App-V Client computer where it was enabled.</p></li>
<li><p>Unpublish the package.</p></li>
<li><p>Remove the package from the connection group’s definition.</p></li>
<li><p>Republish the connection group.</p></li>
</ol></td>
</tr>
</tbody>
</table>
 
## <a href="" id="bkmk-reqs-using-cg"></a>Requirements for using optional packages in connection groups
Review the following requirements before using optional packages in connection groups:
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Requirement</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Connection groups must contain at least one non-optional package.</p></td>
<td align="left"><ul>
<li><p>Check carefully that you meet this requirement, as the App-V Server and the PowerShell cmdlet don’t validate that the requirement has been met.</p></li>
<li><p>If you accidentally create a connection group that does not contain at least one non-optional package, and the end user tries to open a packaged application in that connection group, the connection group will fail.</p></li>
</ul>
<p></p></td>
</tr>
<tr class="even">
<td align="left"><ul>
<li><p>User-published connection groups can contain packages that are published globally or to the user.</p></li>
<li><p>Globally published connection groups must contain only globally published packages.</p></li>
</ul></td>
<td align="left"><p>Globally published connection groups must contain packages that are published globally to ensure that the packages will be available when starting the connection group’s virtual environment.</p>
<p>If you try to add or enable globally published connection groups that contain user-published packages, the connection group will fail.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>You must publish all non-optional packages before publishing the connection group that contains those packages.</p></td>
<td align="left"><p>A connection group’s virtual environment cannot start if any non-optional packages are missing.</p>
<p>The App-V Client fails to add or enable a connection group if any non-optional packages have not been published.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Before you unpublish a globally published package, ensure that the connection groups that are entitled to all the users on that computer no longer require the package.</p></td>
<td align="left"><p>The system does not check whether the package is part of another user’s connection group. Unpublishing a global package will make it unavailable to every user on that computer, so make sure that each user’s connection groups no longer contain the package, or alternatively make the package optional.</p></td>
</tr>
</tbody>
</table>
 
## 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)