When a user is removed from a collections that is assigned to a package, the application is not uninstalled automatically. This requires additional labor to create an uninstall collections group for every application and manage the users within it. Having the option for a collections group to uninstall applications from users that are removed from the group would be a huge cost savings in supporting the product.
| Product | Application Workspace |
This is something I would also like to see. When the user is out of scope of the application, the shortcut dissapears but the app remains on the machine. For an user it would still be possible to access it if knowing the runtime path. It would be nice to have an option to trigger uninstallation when assignment is removed for the user or app is not in scope for the user anymore.
During the creation of a manual Uninstall Action Set we would like to have a trigger or possibility to choose somewhat like: if an "entitlement" is removed for a group or user or is not there anymore then the Uninstall Action set is being triggered because of that. The current use of choosing an action for a group or user at the entitlement is not sufficient because it is too much manual intervention and takes a lot of admin time.
Why do we need this? Let's say a user is changing from department from sales to marketing and does not need software which is part of his job / does not have a license anymore to use software, the applications that are part of sales need to be uninstalled automatically during a reboot, refresh or whatever the trigger will be started.