Export (0) Print
Expand All

About the Connection Group File

Use the Microsoft Application Virtualization (App-V) 5.0 Connection Group file to configure existing Application Virtualization 5.0 connection groups. The following information provides more information about creating or editing a Connection Group file. For more information about managing connection groups using the Application Virtualization 5.0 Management Console see Managing Connection Groups.

Advanced: Connection Group file

When you apply an Application Virtualization 5.0 Connection Group file the packages that are enumerated in the file will be combined at runtime into a single Virtual Environment.

You can use the Connection Group file to configure each connection group using the following methods:

  1. Specify runtime priorities for Connection Groups.

    noteNote
    Priority is only required if the package is associated with more than one connection group.

  2. 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 Application Virtualization 5.0 client uses the priority to determine of which Connection Group Virtual Environment the application should run in. This would only occur 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 will not be utilized in this case.

For example, the Virtual Application Microsoft Outlook is running in Virtual Environment XYZ. When you open an attached Microsoft Word document, a virtualized version Microsoft Word will open in the Virtual Environment XYZ regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.

Configuring Package Precedence

Package precedence is configured using the package list order. The first package in the document has the highest precedence and subsequent packages listed have descending priority. Package precedence is the resolution for otherwise inevitable resource collisions during Virtual Environment Initialization. An example would be if two packages opening in the same Virtual Environment define the same registry DWORD value, the package with the highest precedence will determine the value that is set.

File System location of Connection Group file

The following is an example of a file path:

%APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}.

Connection Group file structure

The following is an example of a file path:

The AppConnectionGroupID is a constant versioned (GUID)

The Connection Group’s VersionID is associated with the member Application Virtualization 5.0 Package versions.

The group's priority is optional:

  • Priority= “0” is highest priority

  • If priorities are not available when required, the package will fail because there is no method to determine correct Virtual Application Connection Group that should be used.

The group's DisplayName is required

Header- the header of the Connection Group file is as follows:

<?xml version="1.0"?>

<AppConnectionGroup

     AppConnectionGroupId="6CCC7575-162E-4152-9407-ED411DA138F4"

     VersionId="4D1E16E1-8EF8-41ED-92D5-8910A8527F96"

     Priority="0"

     DisplayName="Automation Tools"

     xmlns="http://schemas.microsoft.com/appv/2010/virtualapplicationconnectiongroup">

Body- The body of the Connection Group file includes a list of packages that will be associated with the Connection Group. As explained above the first package will have highest precedence for any resource conflicts at Virtual Environment Initialization.

<Packages>

<Package

     PackageId="139FD3C0-A6F6-4A1D-9B94-762DC120EA49"

     VersionId="C7DF4F63-5288-439C-ACEF-EF06BF401EC5">

   </Package>

   <Package

     PackageId="15C59546-D495-4C61-8E8A-E2F5A523EE46"

     VersionId="383F8BD9-A822-459A-ACFA-75B3681F35E0">

   </Package>

   <Package

     PackageId="0652B617-7646-4EDC-808E-9BF8FACAF15A"

     VersionId="AF901B80-3E12-4347-BE19-ABFDCAEA1604">

   </Package>

   <Package

     PackageId="B4E0289A-1E44-46EA-B02B-1AA757D75155"

     VersionId="3359EC3F-DE69-4456-944D-7E86F96E0467">

   </Package>

   <Package

     PackageId="1FF1644F-9AE8-4E16-9D8D-D80669591CDF"

     VersionId="7D8DE309-63E5-4E19-9DDF-338CD6CED016">

   </Package>

  </Packages>

</AppConnectionGroup>

Supported Virtual Application Connection Configurations

 

Configuration Explanation

An.exe file and Plugin (.dll)

The scenario represents Microsoft Excel plugin that is available through by a third party and distributed internally to a subset of users running Microsoft Office. The plugin requires Microsoft Excel to function, but do you not want to make it available to all computers. Instead you should use two packages, one for Microsoft Office, and a second for the Microsoft Excel Plugin. All employees will receive the Microsoft Office package, and only some users will receive the Microsoft Excel plugin. The employees that require the Microsoft Excel plugin receive the packages using a Virtual Application Connection Group with both packages. You should update each package individually as required.

An.exe file and a middleware application

This scenario represents an Application that requires a middleware application. There may several applications that all depend on the same middleware runtime version. All computers who require one or more of the Application receive the Virtual Application Connection Groups with the application and middleware application runtime. You can optionally combine multiple middleware applications into a single Virtual Application Connection Group for example 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 runtime}.

An.exe file and an .exe file

This scenario represents an application that relies on another application. You wish 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:

  1. Microsoft Office 2010

  2. Microsoft Communicator 2007

  3. Microsoft Lync 2010

You can manage the deployment using Virtual Application Connection Groups: Microsoft Office 2010 and Microsoft Communicator 2007, and Microsoft Office 2010 and Microsoft Lync 2010. When the deployment has completed, you can choose to either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package, or keep and maintain them as separate packages and deployed using a Connection Group.

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
Show:
© 2014 Microsoft