This is my own personal blog about Windows 365 cloud pc's, Application Packaging, Virtualization, Deployment and managing Windows, macOS and Linux through Intune portal. The opinions and solutions which I provide here are entirely my own thoughts and does not necessarily reflect the opinion or view of my employer or its employees.
| Full infrastructure | SCCM |
| Connection Groups have to be explicitly published to a target. | Only the App-V application sequences have to be distributed to a target. Connection groups are automatically created if a Virtual Environment (VE) is applicable. |
| All App-V sequences in a connection group are available on the target that the connection group has been published to regardless of whether or not the separate sequences have been published to the target. | The ability to create ‘AND’ and ‘OR’ VE’s. In the case of an ‘AND’ VE the connection group will be created only when all sequences in the connection group have been distributed to the target. In the case of an ‘OR’ VE the connection group will be created with only the sequences that have been distributed to the target. |
| Connection group priority can be set at the server console.(Although this does not work with App-V 5 Sp1 due to a bug. This bug has been fixed in Hotfix 1 for App-V 5.0 SP1 Management Server) | There is no method to manage connection group priority. You will have to prevent conflicts from occurring by making sure that one sequence will not be a member of more than one connection group on the same client, through managing your distributions. |
| Connection groups can be disabled (unpublished) from the console. | Connection groups cannot be disabled only removed by removing the VE in SCCM. |
| Connection Group GroupID and VersionID are generated at the server and passed down to every client. | Connection Group GroupID and VersionID are generated at the client (unique at every client). |