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**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > >
