"HNMatchAppvConnectionGroups” tool on Github, change and match multiple APP-V package settings for use with a Connectiongroup the easy way!

Most of us that work with App-V will eventually need to put some of them inside a Connectiongroup (CG).
That’s a pretty straightforward operation, until you deploy it for test, and it fails to install, giving you errors like:
“The connection group {xxx} version {xxx} could not be published because the
virtual COM settings of the individual packages conflict.
Verify that the virtual COM settings are the same for all member packages and try again.

Finally I had the time to put up our free tool from my previous article up on github.
Our powershell procjectfiles may not contain the latest changes, and some errors since my translation to English was done in a hurry using replace with in notepad++.

But you will most likely get the drift, and the compiled working program is included in the msi.

This tool is free, and based around the excellent work of the Tweakappv tool by Caphyon and 7 zip to extract files form the appv files. They are included in the msi file. So please read the included license files from thoose tools in the install folder after install.
Tweakappv files is included with the permission from Caphyon, the Advanced Installer company.

Hope this will help you, feel free to use it as you want, and please report any bugs!

DISCLAIMER: And as always, use it at your own risk!
For complete documentation on how to use, see the docx file included with the msi file in the program install directory.
This tool only modify the internal AppxManifest.xml file, not external files.
May not work correct with older App-V v 5.0 files, only tested with 5.1 or newer.

If you disable browser plugins, you will sadly not be able to activate them again with the tool, we didn't get that XML transform to work.
But they are only commented out in the Appxmanifest.xml file, so you can use Ace editor on the manifestfile again, and then import it back to the package using AVE or MS sequencer after you removed the comment, and it will be enabled again after you save the package again.