It will go through the priority list of Deployment Types and stop when the first one is successful. If you want to do this successfully with Application Supersedence you should have an Application for the old application with the uninstall information specified and then create a new Application for your new application, specifying a supersedence relationship with 'uninstall.'
*-----------------------------------------------* *Adam Juelich* Pulaski Community School District <http://www.pulaskischools.org> Client Management Specialist 920-822-6075 On Fri, May 22, 2015 at 2:47 PM, Mark Evers <[email protected]> wrote: > I need help with an Application uninstall deployment, I have an old > application that I need to remove from my environment for an upgrade(will > be using application supersedence). I created a VB.net Visual Basic > program that displays my Removal message, checks to see if the application > is open, prompts user to close, and after a specified time forces it > closed, and then removes the application. I created a single deployment > (set this to priority one) with my custom program for the Uninstall > command, allowing user interaction, which requires the application to be > run only when user is logged in. I wanted to create a second deployment > type so user could schedule the removal after hours, when they are not > logged in. So I copied the 1st to a second deployment, and modify it, this > time just using the msiexe.exe /x {msi code} command to do the uninstall, > since the program will not be opened, and set this to only run when no user > is logged in, deployment type priority 2. However when I test it, the > AppEnforce log says: *Waiting for user logon. App requires a user to be > logged on and there is no user currently logged on.* The deployment type > that is running is the logged on deployment, it is not even going to the > second deployment type. I have tested both deployment types separately and > they run as expected. > > Is this common behavior for uninstall deployments, it will only use the > 1st deployment that matches the detection, and ignore all others, even > if\when the run conditions do not match the current logged in status? I > know uninstalls ignores any requirements I have set. Is there another way > I can have two uninstall deployments base on logged on behavior? > >
