You could disbable the application that is having issues so it doesnt reinstall. And uninstall it or supersede it with the correct application (which you could tell the app to uninstall it). Sent with Good (www.good.com)
-----Original Message----- From: Stephen Owen [[email protected]<mailto:[email protected]>] Sent: Thursday, January 09, 2014 07:57 AM Central Standard Time To: [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,

