Connections groups in AppV5 is a feature that allows different AppV packages to have visibility to each other by overlaying them overtop of each other. Why would you want to do this? In this real world example, we utilize connection groups for 2 AppV packages. One of these packages is updated bi-yearly or yearly and one of the packages is updated quarterly. If we created one monolith package then full revalidation testing needs to be completed each time it’s updated. This process can take several days. By breaking it out into component packages we can ensure that only a subset of the package is changed and testing can be reduced to just that area which can usually be accomplished in a few hours.
To get started, we create our AppV packages:
With our packages complete, we go onto the AppV Management Server and add the packages to the server:
Then we go to the Connection Groups and ‘ADD CONNECTION GROUP’
We publish the connection group to our targetted servers and both AppV packages ‘merged’ when you open either package. Now, we can update the ‘Address Accelerator’ portion on the quarterly basis that is required and simply add the new AppV version to the Address Accelerator package in the management console and the next publishing refresh it will be received on the server and the next user launch of the package will have the updated components. Smooth, easy and now we don’t have to touch the actual program or its guts.