Export (0) Print
Expand All

About the Connection Group Virtual Environment

Updated: December 8, 2014

Applies To: Application Virtualization 5.0, Application Virtualization 5.0 SP1, Application Virtualization 5.0 SP2, Application Virtualization 5.0 SP3

How package priority is determined

The virtual environment belongs to the AppConnectionGroup. It is not contained in the individual App-V 5.0 packages. Consequently, all the state that is accumulated belongs to the AppConnectionGroup. If an App-V 5.0 package is subsequently removed from the Connection Group, the state that existed during use as part of the connection group will not migrate with it.

During the initialization of the virtual environment, resources can collide. For example, if two packages that each define the same registry DWORD value are combined into a single AppConnectionGroup, a rule must be applied to determine which of the values will exist inside the AppConnectionGroup's virtual environment.

The rule that is used is based on the order in which they appear inside the AppConnectionGroup XML document. For example:

  1. The first App-V 5.0 package in the list has the highest precedence.

  2. The second App-V 5.0 package in the list has the second highest precedence.

For the following section:















Assume that same DWORD value ABC (HKEY_LOCAL_MACHINE\software\contoso\finapp\region) is defined in the 1st and 3rd package, such as:

  1. Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY_LOCAL_MACHINE\software\contoso\finapp\region=5

  2. 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.

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 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 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.

The following example shows the order and relationship of a file name lookup in a connection group for Package A and Package B.


Package A Package B





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.

Got a suggestion for App-V?

Add or vote on suggestions here. For App-V issues, use the App-V TechNet Forum.

See Also

Other Resources

Managing Connection Groups

You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft