From f782b8aa13a34d2ce1621f1f5ab736c2fb8e1e1b Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 19 Jun 2018 16:56:54 -0700 Subject: [PATCH] Finished first pass through of connection group file revision --- .../app-v/appv-connection-group-file.md | 198 ++++-------------- 1 file changed, 40 insertions(+), 158 deletions(-) diff --git a/windows/application-management/app-v/appv-connection-group-file.md b/windows/application-management/app-v/appv-connection-group-file.md index 5a03163b1b..39d95adfca 100644 --- a/windows/application-management/app-v/appv-connection-group-file.md +++ b/windows/application-management/app-v/appv-connection-group-file.md @@ -18,134 +18,45 @@ ms.date: 04/19/2017 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. -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, then add both packages to a connection group to enable Office to use those plug-ins. +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. ### How a 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. +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. - - ---- - - - - - - - - - - - - - - -

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

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

+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}. ## Structure of the connection group XML file +This section will tell you more about the components of the connection group XML file. + ### 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. |Field|Description| |-----|-----------| -|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:
`xmlns="https://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"`| +|Schema name|Name of the schema.
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:
`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.
You can create a new GUID by entering **[Guid]::NewGuid()**.| |VersionId|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.| |DisplayName|Display name of the connection group.| -|Priority|Optional priority field for the connection group.
A value of **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.| - - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldDescription

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:

-

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.

-

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

VersionId

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.

DisplayName

Display name of the connection group.

Priority

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.

+|Priority|Optional priority field for the connection group.
A value of **0** indicates the highest priority.
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.| ### 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. - ---- - - - - - - - - - - - - - - - - - - - - -
FieldDescription

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.

-

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:

-
    -

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

    • -

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

    • -
-
- -  +|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.
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:
- “**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. +The following example connection group XML file shows examples of the fields listed in the previous tables. -``` +```XML + /> - - - - - Example - Example 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

    • -
- - - + |Example|Example 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. +- **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

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

- - 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? @@ -257,4 +139,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## Related topics -- [Managing Connection Groups](appv-managing-connection-groups.md) +- [Managing connection groups](appv-managing-connection-groups.md)