About the Connection Group Virtual Environment
Updated: November 1, 2012
Applies To: Application Virtualization 5.0
About Connection Group virtual environment
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:
The first App-V 5.0 package in the list has the highest precedence.
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:
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 ResourcesManaging 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.