Comparision between Native connection group and SCCM 2012 virtual environment in App-V 5.0

Native & Full Infrastructure	SCCM 2012
Ø       Setting dependency to other virtual applications is done through Connection group.	Connection group is achieved through creating virtual environments  in the SCCM console.
Ø       Connection groups can be published either globally or to user.	Virtual Environments are published globally to the system alone.
Ø       Connection groups can contain a mixture of both user and globally targeted packages.	It cannot contain a mixture of both user and globally targeted packages. SCCM 2012 will only deliver connection groups if all member packages are targeted to either user or machine exclusively. Mixed member targeting is not supported with Virtual Environments in SCCM.
Ø  Connection groups targeted globally cannot contain any user targeted Packages.Connection groups targeted at the user alone can contain both user and computer targeted packages. Mixed scope connection groups always need to be targeted at the user.
Ø       Packages in a connection group set to use any version or set as optional will always use the latest version in cache when initially delivered.	Use any version is not available with SCCM. However we can use the "OR" operator in the console.
Ø      Connection groups can be enabled or disabled to a specific user by an administrator using PowerShell.	Not available as virtual environments are enabled for system only.
Ø      There are two levels of priority with connection groups that can be set in full infrastructure & native.       1. Packages within a connection group can have priority over each other.        2. It can have priority between connection groups.	Virtual Environments can only handle priority between members of a connection group.This is handled by ordering the members in the console.It doesn’t handle priority between connection groups themselves.SCCM currently does not give the ability to set the priority of a virtual environment.So if Package A is a member of two separate connection groups and a user launches Package A, it will fail to launch.
Ø       Packages will fail to unpublish if they are set as mandatory in a published connection group.	Packages that are mandatory can be uninstalled in a virtual environment successfully.SCCM client will create a new connection group which excludes the uninstall package.