--- title: How to Create a Connection Group with User-Published and Globally Published Packages description: How to Create a Connection Group with User-Published and Globally Published Packages author: dansimp ms.assetid: 851b8742-0283-4aa6-b3a3-f7f6289824c3 ms.reviewer: manager: dansimp ms.author: dansimp ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 ms.date: 11/01/2016 --- # How to Create a Connection Group with User-Published and Globally Published Packages You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods: - [How to use PowerShell cmdlets to create the user-entitled connection groups](#bkmk-posh-userentitled-cg) - [How to use the App-V Server to create the user-entitled connection groups](#bkmk-appvserver-userentitled-cg) **What to know before you start:**
Unsupported scenarios and potential issues | Result |
---|---|
You cannot include user-published packages in globally entitled connection groups. |
The connection group will fail. |
If you publish a package globally and then create a user-published connection group in which you’ve made that package non-optional, you can still run Unpublish-AppvClientPackage <package> -global to unpublish the package, even when that package is being used in another connection group. |
If any other connection groups are using that package, the package will fail in those connection groups. To avoid inadvertently unpublishing a non-optional package that is being used in another connection group, we recommend that you track the connection groups in which you’ve used a non-optional package. |