Table of contents
Collapse the table of content
Expand the table of content

About the Connection Group File

Maggie Evans|Last Updated: 8/26/2016
3 Contributors

Applies to

  • Windows 10, version 1607

In this topic:

Connection group file purpose and location

Connection group purpose

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.

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.

How the connection group file works

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.

Example file path


Structure of the connection group XML file

In this section:

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.


Schema name

Name of the schema.

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:



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.

You can create a new GUID by typing: [Guid]::NewGuid().


Version GUID identifier for this version of the connection group.

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.


Display name of the connection group.


Optional priority field for the connection group.

“0” - indicates the highest priority.

If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined.

Parameters that define the packages in the connection group

In the <Packages> 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.



Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.


Unique GUID identifier for the version of the package.

If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted.


Parameter that enables you to make a package optional within the connection group. Valid entries are:

  • “true” – package is optional in the connection group

  • “false” – package is required in the connection group

App-V example connection group XML file

The following example connection group XML file shows examples of the fields in the previous tables.

<?xml version="1.0" encoding="UTF-16"?>
  DisplayName="Sample 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.

Package precedence is the resolution for otherwise inevitable resource collisions during virtual environment initialization. For example, if two packages that are opening in the same virtual environment define the same registry DWORD value, the package with the highest precedence determines the value that is set.

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.

    Priority is required only if the package is 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, 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.


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.

Supported virtual application connection configurations

The following application connection configurations are supported.

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

    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.

    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.

    ExampleExample description

    Virtual application connection group for the financial division

    • Middleware application 1

    • Middleware application 2

    • Middleware application 3

    • Middleware application runtime

    Virtual application connection group for HR division

    • Middleware application 5

    • Middleware application 6

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

    For example, if you are deploying Microsoft Lync 2010, you can use three packages:

    • Microsoft Office 2010
    • Microsoft Communicator 2007
    • Microsoft Lync 2010

    You can manage the deployment using the following connection groups:

    • Microsoft Office 2010 and Microsoft Communicator 2007
    • Microsoft Office 2010 and Microsoft Lync 2010

    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.

Have a suggestion for App-V?

Add or vote on suggestions on the Application Virtualization feedback site.
For App-V issues, use the App-V TechNet Forum.

Managing Connection Groups

© 2017 Microsoft