New-AppvConnectionGroupFile -DisplayName вЂњInternet Explorer PluginsвЂќ -Priority 0 -FilePath InternetExplorerPlugins.xml -Packages $PackagesД¬reates a Connection Group file named вЂInternetExplorerPlugins.xmlвЂ™ with a display name of вЂInternet Explorer PluginsвЂ™ from packages contained within the array $Packages. # Group description (XML) files for use with stand alone clients or # Desc: Function that uses the App-V 5.0 client to create Connection The function will output the definition file to a specified path and then return that file as an object that you can do further processing with. New-AppvConnectionGroupFile will create the definition file from a list of App-V packages passed to it. To simplify the process of creating the definition file for a Connection Group, IвЂ™ve written a PowerShell function that will handle the heavy lifting for you. To create the file, we need to generate GUIDs for the group and version IDs, supply a Connection Group display name and priority, and then add the package and version IDs for each member package. Each Connection Group has itвЂ™s own group and version ID (GUIDs).ДЄ typical definition file will look something like this: WhatвЂ™s in a Definition File?ДЄ Connection Group definition file contains the details about the Connection Group and the member packages. Crafting XML files from scratch using Notepad isnвЂ™t my idea of fun. Without the App-V Management Server or ConfigMgr (where the resulting file ends up on the client), youвЂ™ll need to do that manually. Connection Groups are easy enough to deploy with the App-V Management Server or Configuration Manager 2012 however that isnвЂ™t the case for stand-alone scenarios or 3rd party ESDs.ДЄdding a Connection Group to the client, first requires creating a definition file in XML. Connection Groups (or Dynamic Suite Composition v2) in App-V 5.0 are great for enabling separate App-V packages to talk to each other.

Powershell create odbc connection