Also note that if a system is subject to both an uninstall and a required install of the same application, then required install will win.
So, what you probably would do is delete the deployment and then create a new uninstall deployment for the same collection. J From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Craig Sent: Thursday, January 9, 2014 8:12 AM To: [email protected] Subject: RE: [mssms] Help me to understand what happens in this application deployment scenario You cannot target a deployment, install or uninstall, of an application more than once to the same collection(you cannot have an install and uninstall of the same app deployed to the same collection because install/uninstall is the action of the deployment). That said you could target an install to one collection and an uninstall to another collection with the same members, then you would have this problem. Just saying. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Stephen Owen Sent: 09 January 2014 14:57 To: [email protected]<mailto:[email protected]> Subject: [mssms] Help me to understand what happens in this application deployment scenario Hi all, Was asked a question by a colleague that stumped me for a moment. I have much, much more experience in 2007 SCCM than with 2012, so I suspect there is an easy answer to this that I'm missing. Consider this scenario. We have 'Accounting Users Collection' to which we create a Required Installation Deployment of 'Account app 1', and send it off on its way. Later, we discover a problem with this application and need to remove it, so we create a Required Uninstallation Deployment, and target that at the same collection. Does the uninstall run? If so, does the application attempt to reinstall itself? Is there a behavior for controlling how often a Deployment runs on a machine, or is it like an Advertisements 'Run once and never rereun', etc. Thanks guys,
