Uninstall deployment for an AppV5 application with Connection group fails if using a User Collection but works on Machine Collections.

Question

Hi,
I'm having troubles to understand why my application in AppV5 that was sequenced with "MS. AppV Sequencer SP1" is somehow failing to be uninstalled properly only if this on is deployed with a
User collection but on the other hand the same application installs & uninstalls perfectly if its deployed using a
Machine collection? 
Here is an extract of the Appenforce.log:
Remove-AppvClientPackage : Operation failed because package belongs to a
connection group on the machine. Please ensure that package does not belong to
any connection groups.
Operation attempted: Remove AppV Package.
AppV Error Code: 020000050C.
Please consult AppV Client Event Log for more details.
Au caractŠre Ligne:1 : 106
+ import-module 'C:\Program Files\Microsoft Application
Virtualization\Client\Appv ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidResult : (:) [Remove-AppvClientPackage], 
   ClientException
    + FullyQualifiedErrorId : RemovePackageError,Microsoft.AppV.AppvClientPowe
   rShell.RemoveAppvPackage
I know that SCCM 2012 does not uninstalls application prerequisites unless they are targeted by their individual uninstall collection or script an uninstall procedure on the main application. But if I try using the Machine collection the error is not appearing
and the main application is removed and the Prereq will be left behind without causing any trouble at all !! 
So my question is: Why an APPV5 application with a connection group should be pushed in a Machine context ?
Notice that I already tried to do the troubleshooting to remove the application manually with PowerShell.
- set-executionpolicy unrestricted
- Import-Module AppvClient
- Get-AppvClientPackage -Name PackageName*
- Unpublish-AppvClientPackage $PackageName
- Remove-AppvClientPackage $PackageName
And actually it was removed but the problem started again if I tried to re-install /remove the application.
Will really appreciate your comments.
Kind Regards.
Joel E.G.

Answer 1

Hi Paul,
To be honest we already experienced many troubles after the SCCM console was migrated from R1 to R2, SCCM client was updated too in consequence, but our AppV5 client still remains on SP1.
I'm afraid that any application that uses Connections Groups will have to be pushed on a Machine context and I just wanted to really understand more about this subject of why it was working that way and not by User is there something I missed with (Run Virtual)
that for any reason is not perfectly implemented to run on a user context?
Any way, we will be testing AppV5 Client SP2 really soon because we have no choice.
Regards,
Joel EG