I think that is what happened, but it is not general rule. On another deployments it worked all the time.
Seems as some older ones got stock somewhere and the client or server? needed a push. Deleting the deployment (not nice in prod..) or adding/removing the clients did it. If that happens more often I would raise that of course. Amazing how much time is wasted chasing such things. -R From: [email protected] [mailto:[email protected]] On Behalf Of Kim Oppalfens Sent: Montag, 16. September 2013 14:38 To: [email protected] Subject: RE: [mssms] Weird App Uninstall behavior Haven't tested this, but I am not surprised by your results. I am afraid you've hit a limitation of the app model. Could you have a look at the following: 1. Using the app deployment monitoring tool from the configmgr toolkit check why uninstall isn't occurring. (as stated here before, my guess is, there is still a deployment policy available) 2. Using policy spy check whether you can find the deployment policy. My guess is that the dependencies, do create the deployment policies, but removing the resource from the original installation does not remove the policies for the dependencies. From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: 16 September 2013 09:34 To: [email protected] Subject: RE: [mssms] Weird App Uninstall behavior There ares no user deployments, only machines in this case. Let me put it like that: First there is a deployment for an app with 2 dependencies, installing ok. 1. Install: Client added to collection. App1 installs App2 and App3 2. Uninstall: Client is removed from the install collection and added to uninstall. Three separate deployments for App1, 2 and 3 Only 1 is actually uninstalled, 2 and 3 don't do anything. Can someone try that? -R From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: Montag, 16. September 2013 07:08 To: [email protected] Subject: Re: [mssms] Weird App Uninstall behavior if a deployment tells it to keep it installed by an ad to a user you cannot remove it with an ad to the machine. I really had a hard time understanding your question though. On Sun, Sep 15, 2013 at 5:27 PM, Roland Janus <[email protected]> wrote: I'm trying to make some sense into that: It is know that an application with dependencies installs fine and that an uninstall of that app would just ignore them and keep them installed. Also there is no choice to have an uninstall action in a task sequence. Big gap I'd like to have fixed by MS, but I've tried to work around this by doing: Pre-req: - Collection with a client - A required deployment for that app with dependencies for two other apps. Those 3 apps install fine. Now: - Create an uninstall collection - Create three required deployments o One for the main app (the one having the dependencies). o And two others for the other two applications on the same collection. They are only deployed through the dependency. - Move the client from the install to the uninstall collection. The main app is uninstalled (ignoring the dependencies), but since I have uninstalls for the two others, they should be uninstalled also, there is nothing to keep them enforced I think. They are not. Nothing happens, CM (SP1 CU2) just completely ignores two required uninstall deployments of installed apps. And the detection rules are correct, but it's not doing anything. Can someone try to replicate this please or has an explanation? -Roland
