SCCM 2012 R2: automatic uninstall App-V 5 packages

Question

Hi,
We are using App-V 5.0 SP3 for computers (in test phase) as well as Terminal Servers (in production, App-V 4.6 and 5.0 on the same W2K8R2 servers). We were thinking about using a App-V management server since SCCM integrated App-V has downsides, most important
one is no automatic uninstall. Then there is this comparison which shows that integrating in SCCM has much more options:
http://virtualvibes.co.uk/app-v-management-server-or-configuration-manager-2012-a-feature-comparison
So we're back at going for "SCCM App-V integrated" and the issue that uninstall doesn't happen automatically. Also there is this post which tells us "With App-V 5.0 SP2, App-V packages that are being used cannot be uninstalled."
http://henkhoogendoorn.blogspot.be/2013/07/configmgr-2012-sp1-with-app-v-50.html
So I'm still looking for the best approach to:
*deploy App-V 5.0 packages to terminal servers via SCCM 2012 (user targetted): an uninstall won't happen for one user if another user has it in use? Then how can we enforce an uninstall/remove an application nicely?
*deploy App-V 5.0 packages to W7 computers via SCCM 2012 (first phase, later we will deploy to users on the computers): deploy an App-V package to  certain collection with computers, deploy an uninstall to "all computers" so that if
computerobject isn't member of the collection, it will uninstall? Won't every user then receive loads of uninstalls triggered (even not visible in the console)?
Sound all quite messy for me.
Please advise.
J.
Jan Hoedt

Answer 1

>So the answer to your first question, yes, the installation will happen even though there's another user
My question was "an UNinstall won't happen for one user if another user has it in use? Then how can we enforce an uninstall/remove an application nicely?"
What I meant: an uninstall should remove the App-v package for all users (uninstalling for 1 user is not the goal) but it won't as long it 's in use. That means we need to force a removal somehow.
>For the second one, I'd skip the first phase
That's no option, so my question stays
"deploy an App-V package to  certain collection with computers, deploy an uninstall to "all computers" so that if computerobject isn't member of the collection, it will uninstall? Won't every user/computer then receive loads of uninstalls
triggered (even not visible in the console)?"
Jan Hoedt
If you want to remove the application from all users, just add all users to the collection and deploy the application as uninstall, it will be removed from every single user when the policies are applied.
For the second question, create a collection that has all the computers that you want to have the application installed and deploy the installation of the application to that collection. Then create another collection that has all the computers as member,
BUT exclude the collection you created for installation. Now all the computers that don't belong to the install collection, will have uninstall deployed against them.