System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Option to uninstall an application when a user or device falls out of scope of the collection

This is a buggy, Would we like the option to have ' Uninstall Application when Resource falls out of scope of this collection' when an application is deployed to a collection, this would save us having to create 2 collections ( install and uninstall) and to deployments. This would save SO much time and reduce the complicity of application management.

851 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Steven John Cuthill shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Thore commented  ·   ·  Flag as inappropriate

    I love this idea. It would be an big step from an task-based to an status-based deployment solution.

  • Mike Compton commented  ·   ·  Flag as inappropriate

    @Mirko Colemberg - I DO NOT feel that it is the System Center team's role, to NOT write code in case an admin uses it incorrectly. They do not have the role of policing how we administer our estates.

    If they took that approach, we would not have any OSD solution, in case people accidentally deploy a client OS to their server estate.

    If you regularly accidentally delete computer objects A) change the permissions of your role to prevent this and B) be more careful!

  • ConfigMgrRSC commented  ·   ·  Flag as inappropriate

    well Kind of dangerous behavior imho. but you can achieve this by creating a uninstall collection and include "all Systems" that you want to behave like this. as Long as a Client is also in the installcollection, the Software will be deployed to this Client. if you drop him out of the install collection - well the uninstall collection will be do the rest

  • John commented  ·   ·  Flag as inappropriate

    Someone else has a similar suggestion. It's a very good one and shouldn't have the votes for it split.

  • Steve commented  ·   ·  Flag as inappropriate

    Simple enough - you can set applications to deploy to collections but there is no way for those applications to be removed if a user or device is kicked from the collection. This would really help with companies managing their licenses this way.

  • Law YT commented  ·   ·  Flag as inappropriate

    I fully support this as currently have to developed a customized script on the client machine to monitor policy and once detected being removed then only trigger the uninstall of the application. This getting more complex when using application model especial optional deployment.

  • Steven John Cuthill commented  ·   ·  Flag as inappropriate

    Agreed it can be a powerful feature but with some improvements in how the system can remember object ID collection memberships of the object is deleted would make some of this a less of a concern. Good change controls would provent more. It's just to complex to set up an uninstall competed to other vendors and group policy.

  • Anonymous commented  ·   ·  Flag as inappropriate

    that's what SMS 1.2 (or 2.0, don't remember) had, and it was responsible for uninstalling unintentionally applications. Dangerous.

  • Mirko Colemberg commented  ·   ·  Flag as inappropriate

    i thinnk this is not a god idea, in case some admin delete a client object in the konsole this object will loose all direct meberships of all collections and in this case the computernwill uninstall all software. this could be difficult.

2 Next →

Feedback and Knowledge Base