Hey,
I have attempted to develop a standard application workflow for Config Manager 2012 Sp1. Based on our 2007 workflow where we targeted workstations...
Install collections were populated where workstation was a member of an AD group but did NOT have the install available.
Uninstall collections were then populated where workstation was not a member of the AD group but had the application installed.
This process was fairly simple and meant the collections had limited numbers of members.
NOW
I am looking at reproducing a similar workflow in 2012 however user targeted deployments seem to be causing an issue.
The only option I have come up with is if user is in an AD group they get added to the collection and the install collection is excluded from the uninstall collection.
By default all users are a member of the uninstall collection so if the application is detected it gets uninstalled.
In practice the above approach does work...however I have a feeling that since we have 200+ applications the fact that a client is assessing 190 odd uninstall deployments this can take some time on the clients and other tasks get delayed during the processing.
Does anyone have a tried and true approach to this? Am I doing it right or have a gone down the completely wrong path?