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

Merged PR 9329: Updated four more App-V articles for voice and style

Browse Source 
Updated the following four articles for voice and style:

- appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
- appv-connection-group-file.md
- appv-connection-group-file.md
- appv-connect-to-the-management-console.md

Also updated the tables from HTML to simple Markdown format.
This commit is contained in:
Heidi Lohr
2018-06-25 18:38:49 +00:00
parent 12d8e9d4af 139bc297d5
commit 9dac292bf3
4 changed files with 122 additions and 296 deletions
Download Patch File Download Diff File Expand all files Collapse all files

53
windows/application-management/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
View File

@ -1,46 +1,41 @@
---
title: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server (Windows 10)
description: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
title: How to configure the client to receive package and connection groups updates from the publishing server (Windows 10)
description: How to configure the client to receive package and connection groups updates from the publishing server.
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.date: 06/25/2018
---
# How to configure the client to receive package and connection groups updates from the publishing server
>Applies to: Windows 10, version 1607
# How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
The App-V publishing server's single-point management and high scalability lets you deploy packages and connection groups and keep them up to date.
**Applies to**
- Windows 10, version 1607
This article will tell you how to configure the App-V client to receive updates from the publishing server.
Deploying packages and connection groups using the App-V publishing server is helpful because it offers single-point management and high scalability.
>[!NOTE]
>The following example has the management server installed on a computer named **MyMgmtSrv**, and the publishing server installed on a computer named **MyPubSrv**. If the computers you'll be configuring the App-V client on have different names, you should replace the example's names with your computer's names.
Use the following steps to configure the App-V client to receive updates from the publishing server.
## Configure the App-V client to receive updates from the publishing server
**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**.
1. Deploy the App-V management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, 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 create a connection group](appv-create-a-connection-group.md).
2. To open the management console, open a web browser and enter the following URL: <https://MyMgmtSrv/AppvManagement/Console.html>. Import, publish, and entitle all packages and connection groups that your users will need.
3. On the computer running the App-V client, open an elevated Windows PowerShell command prompt, and run the following command:
 
**To configure the App-V client to receive updates from the publishing server**
1. Deploy the App-V management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, 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 Create a Connection Group](appv-create-a-connection-group.md).
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 Windows PowerShell command prompt, and run the following command:
`Add-AppvPublishingServer -Name ABC -URL http://MyPubSrv/AppvPublishing`
```PowerShell
Add-AppvPublishingServer -Name ABC -URL https://MyPubSrv/AppvPublishing
```
This command will configure the specified publishing server. You should see output similar to the following:
```
```PowerShell
Id                        : 1
SetByGroupPolicy          : False
Name                      : ABC
URL                       : http:// MyPubSrv/AppvPublishing
URL                       : https://MyPubSrv/AppvPublishing
GlobalRefreshEnabled      : False
GlobalRefreshOnLogon      : False
GlobalRefreshInterval     : 0
@ -51,16 +46,18 @@ For the following procedures the management server was installed on a computer n
UserRefreshIntervalUnit   : Day
```
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 Windows PowerShell command prompt and enter the following cmdlet:
`Sync-AppvPublishingServer -ServerId 1`
```PowerShell
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.
This cmdlet will query the publishing server for which packages and connection groups need to be added or removed for this particular client based on your configured entitlements for the packages and connection groups on the management server.
## Have a suggestion for App-V?
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
## Related topics
[Operations for App-V](appv-operations.md)
* [Operations for App-V](appv-operations.md)

20
windows/application-management/app-v/appv-connect-to-the-management-console.md
View File

@ -1,30 +1,28 @@
---
title: How to Connect to the Management Console (Windows 10)
description: How to Connect to the Management Console
title: How to connect to the Management Console (Windows 10)
description: How to Connect to the App-V Management Console.
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.date: 06/25/2018
---
# How to connect to the Management Console
# How to Connect to the Management Console
**Applies to**
- Windows 10, version 1607
>Applies to: Windows 10, version 1607
Use the following procedure to connect to the App-V Management Console.
**To connect to the App-V Management Console**
## Connect to the App-V Management Console
1. Open Internet Explorer browser and type the address for the App-V Management server. For example, **https://\<_management server name_\>:\<_management service port number_\>/console.html**.
1. Open your web browser and enter the address for the App-V Management server. For example, **https://\<_management server name_\>:\<_management service port number_\>/console.html**.
2. To view different sections of the console, click the desired section in the navigation pane.
2. To view different sections of the console, select your desired section in the navigation pane.
## Have a suggestion for App-V?
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
## Related topics

246
windows/application-management/app-v/appv-connection-group-file.md
View File

@ -1,159 +1,62 @@
---
title: About the Connection Group File (Windows 10)
description: About the Connection Group File
title: About the connection group file (Windows 10)
description: A summary of what the connection group file is and how to configure it.
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.date: 06/25/2018
---
# About the connection group file
>Applies to: Windows 10, version 1607
# About the Connection Group File
## Connection group file overview
**Applies to**
- Windows 10, version 1607
### What is a connection group?
**In this topic:**
A connection group is an App-V feature that can group packages together to create a virtual environment where applications within that package group can interact with each other.
- [Connection group file purpose and location](#bkmk-cg-purpose-loc)
For example, let's say you want to use plug-ins with Microsoft Office. You can create one package that contains the plug-ins and another package that contains Office, and then add both packages to the same connection group to enable Office to use those plug-ins.
- [Structure of the connection group XML file](#bkmk-define-cg-5-0sp3)
### How a connection group file works
- [Configuring the priority of packages in a connection group](#bkmk-config-pkg-priority-incg)
When you apply an App-V connection group file, all packages specified in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) connection group file to configure existing App-V connection groups.
- [Supported virtual application connection configurations](#bkmk-va-conn-configs)
An example file path for a package file would be %APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}.
## <a href="" id="bkmk-cg-purpose-loc"></a>Connection group file purpose and location
## Structure of the connection group XML file
This section will tell you more about the components of the connection group XML file.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>Connection group purpose</p></td>
<td align="left"><p>A connection group is an App-V feature that enables you to group packages together to create a virtual environment in which the applications in those packages can interact with each other.</p>
<p>Example: You want to use plug-ins with Microsoft Office. You can create a package that contains the plug-ins, and create another package that contains Office, and then add both packages to a connection group to enable Office to use those plug-ins.</p></td>
</tr>
<tr class="even">
<td align="left"><p>How the connection group file works</p></td>
<td align="left"><p>When you apply an App-V connection group file, the packages that are enumerated in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) connection group file to configure existing App-V connection groups.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Example file path</p></td>
<td align="left"><p>%APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}.</p></td>
</tr>
</tbody>
</table>
 
## <a href="" id="bkmk-define-cg-5-0sp3"></a>Structure of the connection group XML file
**In this section:**
- [Parameters that define the connection group](#bkmk-params-define-cg)
- [Parameters that define the packages in the connection group](#bkmk-params-define-pkgs-incg)
- [App-V example connection group XML file](#bkmk-50sp3-exp-cg-xml)
### <a href="" id="bkmk-params-define-cg"></a>Parameters that define the connection group
### Parameters that define the connection group
The following table describes the parameters in the XML file that define the connection group itself, not the packages.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Field</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Schema name</p></td>
<td align="left"><p>Name of the schema.</p>
<p>If you want to use the “optional packages” and “use any version” features that are described in this table, you must specify the following schema in the XML file:</p>
<p><code>xmlns=&quot;https://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup&quot;</code></p></td>
</tr>
<tr class="even">
<td align="left"><p>AppConnectionGroupId</p></td>
<td align="left"><p>Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.</p>
<p>You can create a new GUID by typing: <strong>[Guid]::NewGuid()</strong>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>VersionId</p></td>
<td align="left"><p>Version GUID identifier for this version of the connection group.</p>
<p>When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.</p></td>
</tr>
<tr class="even">
<td align="left"><p>DisplayName</p></td>
<td align="left"><p>Display name of the connection group.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Priority</p></td>
<td align="left"><p>Optional priority field for the connection group.</p>
<p><strong>“0”</strong> - indicates the highest priority.</p>
<p>If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined.</p></td>
</tr>
</tbody>
</table>
|Field|Description|
|-----|-----------|
|Schema name|Name of the schema.</br>If you want to use the “optional packages” and “use any version” features described in this table, you must specify the following schema in the XML file:</br>`xmlns="https://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"`|
|AppConnectionGroupId|Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.</br>You can create a new GUID by entering **[Guid]::NewGuid()**.|
|VersionId|Version GUID identifier for this version of the connection group.</br>When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.|
|DisplayName|Display name of the connection group.|
|Priority|Optional priority field for the connection group.</br>A value of **0** indicates the highest priority.</br>If a priority is required but has not been configured, the package will fail because it can't determine the correct connection group to use.|
 
### <a href="" id="bkmk-params-define-pkgs-incg"></a>Parameters that define the packages in the connection group
### Parameters that define the packages in the connection group
In the &lt;Packages&gt; section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Field</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>PackageId</p></td>
<td align="left"><p>Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.</p></td>
</tr>
<tr class="even">
<td align="left"><p>VersionId</p></td>
<td align="left"><p>Unique GUID identifier for the version of the package.</p>
<p>If you specify <strong>“*”</strong> for the package version, the GUID of the latest available package version is dynamically inserted.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>IsOptional</p></td>
<td align="left"><p>Parameter that enables you to make a package optional within the connection group. Valid entries are:</p>
<ul>
<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>
</td>
</tr>
</tbody>
</table>
|Field|Description|
|---|---|
|PackageId|Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.|
|VersionId|Unique GUID identifier for the version of the package. </br>If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted.|
|IsOptional|Parameter that enables you to make a package optional within the connection group. Valid entries are:</br>- “**true**”—package is optional in the connection group</br>- “**false**”—package is required in the connection group|
 
### App-V example connection group XML file
### <a href="" id="bkmk-50sp3-exp-cg-xml"></a>App-V example connection group XML file
The following example connection group XML file shows examples of the fields listed in the previous tables.
The following example connection group XML file shows examples of the fields in the previous tables.
```
```XML
<?xml version="1.0" encoding="UTF-16"?>
<appv:AppConnectionGroup
xmlns="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"
@ -167,7 +70,7 @@ xmlns:appv="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiong
PackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"
VersionId="*"
IsOptional=”true”
/>
/>
<appv:Package
PackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"
VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"
@ -176,8 +79,7 @@ xmlns:appv="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiong
</appv:Packages>
```
## <a href="" id="bkmk-config-pkg-priority-incg"></a>Configuring the priority of packages in a connection group
## Configuring the priority of packages in a connection group
Package precedence is configured using the package list order. The first package in the document has the highest precedence. Subsequent packages in the list have descending priority.
@ -185,84 +87,56 @@ Package precedence is the resolution for otherwise inevitable resource collision
You can use the connection group file to configure each connection group by using the following methods:
- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, click the connection group and then click **Edit**.
- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, select the connection group and then select **Edit**.
**Note**  
Priority is required only if the package is associated with more than one connection group.
>[!NOTE]
>A package only requires priority if it's associated with more than one connection group.
- Specify package precedence within the connection group.
 
The priority field is required when a running virtual application initiates from a native application request, such as Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
- Specify package precedence within the connection group.
If a virtual application is opened using another virtual application, the client will use the orignal virtual application's virtual environment. The priority field is not used in this case.
The priority field is required when a running virtual application initiates from a native application request, for example, Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
If a virtual application is opened using another virtual application the virtual environment of the original virtual application will be used. The priority field is not used in this case.
**Example:**
The following is an example of priority configuration:
The virtual application Microsoft Outlook is running in virtual environment **XYZ**. When you open an attached Microsoft Word document, a virtualized version Microsoft Word opens in the virtual environment **XYZ**, regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.
## <a href="" id="bkmk-va-conn-configs"></a>Supported virtual application connection configurations
## Supported virtual application connection configurations
The following application connection configurations are supported.
App-V supports the following application connection configurations.
- **An. exe file and plug-in (.dll)**. For example, you might want to distribute Microsoft Office to all users, but distribute a Microsoft Excel plug-in to only a subset of users.
- **An .exe file and plug-in (.dll)**. For example, you might want to distribute Microsoft Office to all users, but only distribute a Microsoft Excel plug-in to a small subset of those users.
Enable the connection group for the appropriate users. Update each package individually as required.
- **An. exe file and a middleware application**. You might have an application that requires a middleware application, or several applications that all depend on the same middleware runtime version.
- **An .exe file and a middleware application**. This is for cases where you have an application that requires a middleware application, or several applications that all depend on the same middleware runtime version.
All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime. You can optionally combine multiple middleware applications into a single connection group.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Example</th>
<th align="left">Example description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Virtual application connection group for the financial division</p></td>
<td align="left"><ul>
<li><p>Middleware application 1</p></li>
<li><p>Middleware application 2</p></li>
<li><p>Middleware application 3</p></li>
<li><p>Middleware application runtime</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Virtual application connection group for HR division</p></td>
<td align="left"><ul>
<li><p>Middleware application 5</p></li>
<li><p>Middleware application 6</p></li>
<li><p>Middleware application runtime</p></li>
</ul></td>
</tr>
</tbody>
</table>
|Example|Example description|
|---|---|
|Virtual application connection group for the financial division|- Middleware application 1</br>- Middleware application 2</br>- Middleware application 3</br>- Middleware application runtime|
|Virtual application connection group for HR division|- Middleware application 5</br>- Middleware application 6</br>- Middleware application runtime|
- **An. exe file and an .exe file**. You might have an application that relies on another application, and you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.
- **An. exe file and an .exe file**. This is for cases where you have an application that relies on another application, but you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.
For example, if you are deploying Microsoft Lync 2010, you can use three packages:
- Microsoft Office 2010
- Microsoft Office 2010
- Microsoft Communicator 2007
- Microsoft Lync 2010<br><br>
You can manage the deployment using the following connection groups:
- Microsoft Lync 2010
You can manage the deployment with the following connection groups:
- Microsoft Office 2010 and Microsoft Communicator 2007
- Microsoft Office 2010 and Microsoft Lync 2010<br><br>
When the deployment has completed, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package, or keep and maintain them as separate packages and deploy them by using a connection group.
- Microsoft Office 2010 and Microsoft Lync 2010
After deployment, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package or keep and maintain them as separate packages and deploy them with a connection group.
## Have a suggestion for App-V?
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
## Related topics
[Managing Connection Groups](appv-managing-connection-groups.md)
- [Managing connection groups](appv-managing-connection-groups.md)

99
windows/application-management/app-v/appv-connection-group-virtual-environment.md
View File

@ -1,112 +1,69 @@
---
title: About the Connection Group Virtual Environment (Windows 10)
description: About the Connection Group Virtual Environment
title: About the connection group virtual environment (Windows 10)
description: Overview of how the connection group virtual environment works.
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.date: 06/25/2018
---
# About the connection group virtual environment
>Applies to: Windows 10, version 1607
# About the Connection Group Virtual Environment
## How package priority is determined
**Applies to**
- Windows 10, version 1607
**In this topic:**
- [How package priority is determined](#bkmk-pkg-priority-deter)
- [Merging identical package paths into one virtual directory in connection groups](#bkmk-merged-root-ve-exp)
## <a href="" id="bkmk-pkg-priority-deter"></a>How package priority is determined
The virtual environment and its current state are associated with the connection group, not with the individual packages. If an App-V package is removed from the connection group, the state that existed as part of the connection group will not migrate with the package.
The virtual environment and its current state are associated with the connection group, not with the individual packages. If you remove an App-V package from the connection group, the state that existed as part of the connection group will not migrate with the package.
If the same package is a part of two different connection groups, you have to indicate which connection group App-V should use. For example, you might have two packages in a connection group that each define the same registry DWORD value.
The connection group that is used is based on the order in which a package appears inside the **AppConnectionGroup** XML document:
- The first package has the highest precedence.
- The second package has the second highest precedence.
- The first package has the highest precedence.
- The second package has the second highest precedence.
Consider the following example section:
``` syntax
```XML
<appv:Packages><appv:PackagePackageId="A8731008-4523-4713-83A4-CD1363907160"VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"/><appv:PackagePackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"/><appv:PackagePackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"/></appv:Packages>
```
Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package, such as:
Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package.
- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
For this example, the DWORD value definition would be the following:
- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
Since Package 1 appears first, the AppConnectionGroup's virtual environment will have the single DWORD value of 5 (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5). This means that the virtual applications in Package 1, Package 2, and Package 3 will all see the value 5 when they query for HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region.
Other virtual environment resources are resolved similarly, but the usual case is that the collisions occur in the registry.
Other virtual environment resources are resolved in a similar way, but usually collisions occur in the registry.
## <a href="" id="bkmk-merged-root-ve-exp"></a>Merging identical package paths into one virtual directory in connection groups
## Merging identical package paths into one virtual directory in connection groups
If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group's virtual environment. Merging these paths allows an application in one package to access files that are in a different package.
If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group virtual environment. This merging of paths allows an application in one package to access files that are in a different package.
When you remove a package from a connection group, the removed package's applications can no longer access files from packages in the connection group it was removed from.
When you remove a package from a connection group, the applications in that removed package are no longer able to access files in the remaining packages in the connection group.
The order in which App-V looks up a file’s name in the connection group is specified by the order in which the App-V packages are listed in the connection group manifest file.
App-V looks up a file’s name in the connection group in the order App-V packages are listed in the connection group manifest file.
The following example shows the order and relationship of a file name lookup in a connection group for **Package A** and **Package B**.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Package A</th>
<th align="left">Package B</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>C:\Windows\System32</p></td>
<td align="left"><p>C:\Windows\System32</p></td>
</tr>
<tr class="even">
<td align="left"><p>C:\AppTest</p></td>
<td align="left"><p>C:\AppTest</p></td>
</tr>
</tbody>
</table>
|Package A|Package B|
|---|---|
|C:\Windows\System32|C:\Windows\System32|
|C:\AppTest|C:\AppTest|
 
When a virtualized application tries to find a specific file, App-V will first for a matching file path in Package A. If it doesn't find a matching path in Package A, it will then search Package B using the following mapping rules:
In the example above, when a virtualized application tries to find a specific file, Package A is searched first for a matching file path. If a matching path is not found, Package B is searched, using the following mapping rules:
- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, the first matching file is used.
- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, the first matching file is used.
- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, App-V will use the first matching file.
- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, App-V will use the first matching file.
## Have a suggestion for App-V?
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
## Related topics
[Managing Connection Groups](appv-managing-connection-groups.md)
 
 
- [Managing Connection Groups](appv-managing-connection-groups.md)